Beads Git Graph

A local project workspace for coordinating tasks across AI providers in VS Code. Create tasks, follow dependencies, and review results without installing Beads or another task CLI. Git history and existing Beads workspaces are supported too.

Graph view with sample tasks. Now marks recorded work in progress; Next marks ready work.

Find your way around

Manage view with sample tasks. Lanes reflect recorded task and Git/PR metadata, not live agent monitoring.

Get started

1. Install from VS Marketplace or Open VSX.
2. Open a folder, then open Tasks from the Beads Git Graph Activity Bar entry.
3. Create a task, update its status, and add dependencies. Use Graph, Table, and Manage to follow work, or Plan to draft and import a larger plan.

Folders without .beads use built-in local tasks. Tasks are saved to .taskgraph/tasks.json on the first write; opening the folder does not create a task file. Basic task management needs no account, AI provider, or Git repository. Writes require a trusted workspace.

An existing .beads folder keeps using Beads. Its task actions still require the bd CLI; if it is unavailable, the extension reports the problem rather than switching task stores. Set beads-git-graph.bdPath in machine settings if needed. The extension does not initialize or migrate your Beads database, or copy its tasks into the local store.

For a Git repository, run Beads Git Graph: View Git Graph (git log) from the Command Palette.

Graph controls: wheel to zoom at the pointer, drag to pan, Option/Alt-drag to box-zoom, and double-click to fit all. Your selection and viewport stay in place during normal refreshes.

Choose how work runs

Start AI asks for a provider and model. It becomes available when the active task store confirms the task is ready and the workspace supports the required writes. Provider setup and explicit AI approval still apply; local task management itself does not make AI requests.

Direct-provider output is verified and shown for your approval before a file is written. A generated response or applied edit does not automatically close a task. See the provider setup and execution guide for credentials, model choices, parallel runs, and limits.

Copilot sessions require Git for an isolated worktree. The optional Beads Agent Project Manager plugin supports Beads workflows and still requires bd; it is not needed for the extension's built-in local tasks.

Privacy and safety

Privacy-first, security-first: the extension emits no telemetry. AI execution requires a trusted workspace and approval. Cloud providers have their own data policies. Task records and AI audit files may contain plain text. Local task files and Beads files may be Git-tracked—keep secrets out of them and review changes before committing. Read the security boundaries before running agents.

More

User guide · Testing · Contributing · Security policy · Changelog