You file an issue. An agent picks it up, creates a branch, writes the code, and opens a draft PR. You review.

That's the loop now. This is the biggest update to Agent Boards since launch — and the biggest area of investment this cycle.

The self-driving issues flow, step by step

1. File an issue. Write it the way you'd write a ticket for a teammate: "Fix the broken pagination on /users." "Add a /health endpoint." "Write tests for the auth module."

2. The agent picks it up. No assignment step, no kickoff command. The board sees the issue and an agent starts working it.

3. It creates a branch and writes the code. The agent works in a real branch against your real repo, following your board instructions.

4. It opens a draft PR. When the work is done, a draft PR lands in your review drawer with the changes laid out.

5. You review and merge. You stay in the review seat. The agent does the work; you make the call.

Issue → branch → code → PR → human review. That's the whole loop.

Create PRs from the review drawer

PRs are now created directly from the review drawer, with a custom title and custom description. Review the diff, name the PR what it should be named, ship it — without leaving the board.

Board settings: instructions, models, cost caps

Three new per-board controls:

• Per-board instructions. Tell the agent how you want things done for this repo — style guide, testing framework, file structure. Better instructions, better PRs.
• Model selection. Pick the right model for the job, per board. A docs board and a refactoring board don't need the same brain.
• Cost caps. The default cap is higher now, and it's configurable. Bounded autonomy, your bounds.

The reliability stack

A shipping workflow is only as good as its plumbing. Also in this update:

• Board-scoped reordering — card order stays correct per board
• Accurate PR-merge detection — merged means merged
• Rate-limit-aware GitHub sweeps — no more sync stalls under API pressure
• Corrected run-history ordering — the history reads in the order things happened

What this means

Agent Boards are a code shipping workflow now: file issues, review PRs, watch costs, stay in control.

The gap between "AI can code" and "AI ships code through your actual workflow" is the whole game. This update closes a lot of it.

Try it — no API key needed: agents.pinata.cloud