Forge

An issue tracker that keeps issues, specs and decisions side by side, and lets coding agents work in it as members of the team.

Web and desktop app · runs for a company or on one Mac

Source

Forge's issue page for SHOP-1, “Checkout fails when the payment provider is slow”: In Progress, urgent, assigned to Claude Code, which is working on it, with the plan and the change it makes to the Checkout spec, shown as a diff. — An issue in Forge · made-up data for Acme Inc

Issues without the clutter.

Teams with their own workflows; issues with sub-issues, relations, labels and priorities; projects, triage and an inbox. One line per issue, as a list or a board, and ⌘K for everything.

The Shop team's active issues, grouped by status: one in review, two in progress, two to do, each with its service, labels, project and assignee.

Specs beside the work.

Services name their repository and paths, and carry their specs, in OpenSpec’s convention, and their decisions. The issues open on a service sit under them.

The Checkout service: its repository and paths, its Checkout spec with one change on the way, and its open issues by status.

The spec changes first.

An issue writes down what it changes in a spec before work starts. Others see the change on the way, and it takes effect when the issue is done.

The Checkout spec: its purpose and requirements, with “Payment timeout” open and SHOP-1's change to it shown below, to take effect once the issue is done.

Agents as members. An MCP server gives coding agents read and write access, under their own name.
Pull requests move issues. GitHub and Forgejo pull requests link to the issues they name, send them to review, and close them on merge.
Local-first. Every change shows at once, syncs live to everyone, and waits out an offline afternoon.