Guides for connecting the desktop forge to your trackers and git providers.
- Initiation
Getting started
What a workflow needs before it runs: a coding agent, a repository, and a ticket source with a filter.
- Initiation
The UI
The parts of the dashboard: the header, the stage machines, the run controls, the Execution Console and the token meter.
- Initiation
The kanban board
Every ticket a workflow knows about, one card each, from Backlog to Done — and how to queue, order, clear and recover them.
- Covenants
Connect a ticket source
Connect any tracker as a ticket source over MCP — one browser sign-in, no tokens.
- Covenants
Connect GitLab
Register a GitLab OAuth application so the Publish stage can open merge requests on your behalf.
- Covenants
Connect Bitbucket
Create a scoped Atlassian API token so the Publish stage can push commits and open pull requests.
- Covenants
Connect Asana
Register an Asana MCP app so the Scan stage can pull your tasks.
- Workflows
Built-in workflows
Greenfield for a project you're starting, Brownfield for one already in use — and how to choose.
- Workflows
Custom workflows
Build a workflow of your own, share it, and install ones other people made.
- Workflows
The workflow editor
Lay out a custom workflow's machines, set up each stage, draw each one as you like, and pass what one produces to the next.
- Workflows
24/7 development
Let a workflow keep scanning your tracker and running new tickets on its own, on a schedule you set.
New here? Start with Connect a ticket source to seal your first covenant.