Workflows
How a run actually works.
Six phases, grounded in what the agent can really do — not a marketing loop diagram.
01 · Plan
Read the repo before it acts
Agent V plans against your actual working tree — it can search the codebase, query the language server, read code index state, and run git status before writing a plan, not against pasted snippets.
02 · Edit
Change real files, not a simulation
The agent edits, creates, and moves files in your checkout with precise string-level edits, applies unified diffs, and keeps unrelated user changes untouched.
03 · Fan out
Delegate to child instances
Split work into independent workstreams and spawn child agent instances. Each child gets its own git worktree branch; finished branches merge back into the parent without disturbing in-flight work.
04 · Verify
Run the real gates
Typecheck, lint, and test runners are first-class tools in the catalog. Agent V runs the narrowest relevant checks, expands verification when changes cross boundaries, and reports what it verified separately from what it assumes.
05 · Ship
Commit, PR, and release
Git status, diffs, commits, and patch application are wired in, plus GitHub pull requests and issues. Releases publish installers to the releases repository, and the site picks them up automatically.
06 · Extend
Shape the tool catalog to you
Pin MCP server tools, load marketplace skills and plugin rules into a run, or let the agent build a tool that doesn't exist yet — available instantly, no restart.