| name | af |
| description | Agent Farm CLI quick reference. Use when running af commands to check correct syntax, subcommands, and flags. Prevents guessing at command names. |
| disable-model-invocation | false |
Agent Farm Quick Reference
Tower (Dashboard Server)
af tower start
af tower stop
af tower log
af tower status
There is NO af tower restart — use af tower stop && af tower start.
Dashboard
af dash start
af dash stop
af dash open
Builder Management
af spawn -p 0003
af spawn --soft -p 0003
af spawn --issue 42
af spawn -p 0003 --resume
af status
af cleanup --project 0003
af cleanup --project 0003 -f
Resuming Builders
When a builder's Claude process dies but the worktree and porch state survive,
use --resume to restart it without recreating the worktree:
af spawn -p 0003 --resume
This reuses the existing .builders/0003 worktree, creates a fresh terminal
session registered with the Tower (so it appears in the dashboard), and lets
porch pick up from whatever phase the builder was in. Works with all spawn
modes: -p, --issue, --task, --protocol, --worktree.
Utility
af util
af open file.ts
af ports list
af send <builder> "msg"
Configuration
Edit af-config.json at project root to customize shell commands.
{
"shell": {
"architect": "claude",
"builder": "claude",
"shell": "bash"
}
}
Pre-Spawn Checklist
Before af spawn, commit all local changes. Builders work in git worktrees
branched from HEAD — uncommitted files (specs, plans, codev updates) are invisible
to the builder. The spawn command will refuse if the worktree is dirty (override
with --force).
Common Mistakes
- Spawning with uncommitted changes — builder won't see specs, plans, or codev updates
- There is NO
codev tower command — Tower is managed via af tower
- There is NO
restart subcommand — stop then start
- There is NO
af start for Tower — use af tower start or af dash start