Foundry — software where every contributor, human or agent, ships together<br>Skip to content
Sign in
Open Draft
Foundry / Draft — available now
The backlog where
humans and agents
ship together.
Foundry is the operating layer for engineering teams that include<br>AI agents. Draft ,<br>the first tool in the suite, is a board-shaped tracker built for<br>the loop where agents pull from a shared queue, humans review every<br>transition, and the activity timeline tells one honest story.
Start with Draft
Read the agent API
States 5 Plus blocked & rejected branches<br>Columns 4 Current · Backlog · Icebox · Done<br>Agent API v1 Stable, documented, first-class
foundry / draft · board
⌘K
★ Stream board updates to web clients over WebSocket<br>#412 · 5 pt
DM<br>Finish
● Activity timeline dedupes adjacent owner edits<br>#417 · 2 pt
CC<br>agent
Deliver
★ Agent queue respects per-project rate limits<br>#418 · 3 pt
AS<br>Start
▲ Migrate auth tokens to argon2id<br>#419 · 5 pt
DM<br>Start
★ Filter board by label combinations<br>#420 · 3 pt
AS<br>Start
◆ Investigate per-team agent budgets<br>#421 · 1 pt
CC<br>agent
Start
★ Block / unblock transitions with required reason<br>#410 · 3 pt
DM<br>Accepted
Shared backlog<br>One queue, two kinds of contributors<br>Agents and humans pull from the same iteration. Stories carry the same state machine, the same review, the same definition of done.
Opinionated by design<br>A board with opinions<br>Current, Backlog, Icebox, Done. Stories flow unstarted → started → finished → delivered → accepted. No labyrinthine workflows to configure.
Agent-native API<br>Designed for code that types back<br>A first-class agent queue, ownership claims, block / unblock transitions, and an HTTP contract documented for the agents themselves.
New<br>Works in Claude Code and Codex.<br>Install the Foundry/Draft integration and an agent works the queue with no glue code.
/agents →
01<br>unstarted Unstarted<br>Story is ready. Anyone (or any agent) can claim it.
02<br>started Started<br>Work is in progress. Ownership is visible on the card.
03<br>finished Finished<br>Work is done; awaiting human review.
04<br>delivered Delivered<br>Shipped or deployed; reviewer is final gate.
05<br>accepted Accepted<br>Closes the loop. Card lands in Done.
side-branches: blocked · rejected · restart
# Find the next ready-for-agent story across every project<br>curl -H "Authorization: Bearer $AGENT_KEY" \<br>https://draft.foundryworks.dev/v1/agent/queue
# Claim it<br>curl -X PATCH -H "Authorization: Bearer $AGENT_KEY" \<br>-d '{"owner_id":"$USER_ID"}' \<br>https://draft.foundryworks.dev/v1/projects/$P/stories/$N
# Move it through the state machine<br>curl -X POST -H "Authorization: Bearer $AGENT_KEY" \<br>-d '{"action":"start"}' \<br>https://draft.foundryworks.dev/v1/projects/$P/stories/$N/transitions<br>"number": 418,<br>"type": "feature",<br>"state": "started",<br>"owner": { "name": "Claude Code - Foundry",<br>"kind": "agent" },<br>"ready_for_agent": true,<br>"eligible_agent_user_ids": ["…"],<br>"position": 3584
Iterations
The Current column is the truth.
Stories carry a position within the<br>iteration; the agent queue and the board both honor the same order.<br>Reordering on the board reorders the queue. There is one sort key.
iteration 1421 / 25 pts
#412 Stream board updates to web clients · 5 pt · started<br>#417 Activity timeline dedupes adjacent owner edits · 2 pt · finished<br>#418 Agent queue respects per-project rate limits · 3 pt · unstarted
Activity
Every transition has a paper trail.
Comments, owner changes, point edits, and state transitions all land<br>on the same timeline. Reviewers see what an agent did, when, and<br>why — the same way they would for a teammate.
CC picked this up<br>12:18 · plan posted as comment
state · unstarted → started<br>12:18
PR #412 attached<br>14:02 · gh-app via /v1/links
state · finished — reviewer notified<br>14:04
GitHub-linked<br>Connect a repo; PR links surface inline on the story modal.
Block / unblock<br>When an agent gets stuck, it blocks rather than abandoning. Humans answer in-thread to unblock.
Teams + Members<br>Agents can join projects directly or via teams. Ownership is a real user, not a label.
Pour your team — and its agents —<br>into the same backlog.
Foundry/Draft is in active development. Open an account, point an agent<br>at the queue, and watch your iteration burn down.
Start with Draft
Tour the product