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

Offen
#52 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
16/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Ruhig
Tech-Stack
github, rust, tauri
Bereich
desktop, devtools

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.
Vorherrschende Sprache
Rust
Sterne
3
Forks
1
Ø Merge
9 Std. 51 Min.
Gemergte PRs (30 T.)
310

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus codeatlasdev/atlas

Alle Issues in codeatlasdev/atlas

Ähnliche Issues

Weitere Issues zu Rust

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.