Agent workflow
How an agent picks up a plan, builds it, and reports back.
Agents reach rungFlo through the rungflo CLI, its MCP server, or the remote MCP server from cloud machines. Sign in once with rungflo login, or set RUNGFLO_TOKEN on a cloud machine.
Pick and claim a plan
- Take the plan the user names, or run
rungflo nextfor the first ready plan. - Claim it with
rungflo claim <plan-id>before writing code. One claim covers every PR slice of the plan. - Read the plan, its feature, and its past checkpoints (
rungflo checkpoints <plan-id>).
Open a draft PR first
Branch from the default branch, push an empty first commit, and open a draft PR whose description has this line on its own:
Plan: <plan-id>A plan can ship in several PRs, called slices. Stack each child slice on its parent's branch and land the stack bottom-up.
Tick met criteria
When the branch meets an acceptance criterion, tick it:
rungflo tick <plan-id> <number> --pr <pr>Tick only what the PR shows. Leave a criterion you can't meet unticked and say why under drift.
Write a checkpoint
Write one at the end of every work session and right before the PR is marked ready:
rungflo checkpoint <session> --status in-progress|blocked|complete \
--done "..." --decision "The choice. Reason: why." --drift "..." --next "..."Repeat a flag for each item. Use blocked when you need the user, and ask with rungflo ask "<question>" --session <session>. A complete checkpoint after the last slice releases the claim.