Desktop: task sources (GitHub issues, Linear) as a board that starts worktrees

Ouverte
#52 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
16/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Calme
Stack technique
github, rust, tauri
Domaine
desktop, devtools

Piste de recherche

This is a design-first feature: before any code, read how worktrees and agents are created today in the Rust/Tauri backend and where a new project-scoped view would plug into the desktop UI. The provider boundary is the key design decision — sketch the trait (list tasks, fetch body, link back with Closes #N) and how a task-shaped worktree name plus initial agent prompt are produced, then write that interface up as the third acceptance criterion asks. Done means a GitHub-backed task list via the gh CLI, a Start action that creates the worktree and agent, and documentation showing a second provider fits in one module.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

area: desktop status: needs-triage type: feature

Problem

Today a GitHub issue URL can name a worktree, but you cannot browse issues/tasks in Atlas. Picking the next task means leaving the app.

Evidence

From research on parallel-agent desktops and worktree tools, this is a recurring user request:

A recurring request across agent-workspace and parallel-agent tools, with high upvote counts in their public trackers. Public examples: https://github.com/BloopAI/vibe-kanban/issues/1697 (GitLab, 26 👍), https://github.com/BloopAI/vibe-kanban/issues/2509 (keep the kanban board).

Proposed behavior

  • A Tasks view per project: GitHub issues (via gh) first; Linear through its API token; a small provider trait so GitLab/Gitea/Forgejo can follow.
  • Filters (assignee, label, state). Start on a task creates a worktree named after it with the task body as the agent's first prompt.
  • Worktrees show the linked task; PR creation references it (Closes #N).

Acceptance criteria

  • GitHub issues list loads via gh with no extra login.
  • Start creates a worktree + agent with the issue text as prompt.
  • The provider interface is documented so a new source is one module.
Langage dominant
Rust
Étoiles
3
Forks
1
Merge moyen
9 h 51 min
PR mergées (30 j)
310

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de codeatlasdev/atlas

Toutes les issues de codeatlasdev/atlas

Issues similaires

Plus d'issues Rust

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.