Your board or your manager will ask these. Each answer links to its source.
What does it cost?
The mean cost of a shipped story, rework included, is $7.48. CodeHerder estimates the cost of each task from token use and model list prices. A review round or a failed check shows in that number. The Costs page splits spend by agent or by model. You can also split it by stage.
Four spend caps work together. Only spend billed to an API key counts.
- A daily cap. One account value applies to every agent.
- A default cap on each task, set once for the account.
- A budget on one task. It overrides that default.
- A budget on a whole workspace. It counts all spend since the workspace began.
CodeHerder warns you at 80% of a cap. At 100%, a task or workspace cap stops live sessions and blocks the task. The daily cap only refuses new sessions. The account-wide caps and the workspace budget need the Pro plan.
Price your own workload →See plan pricing →How spend caps stack →
Is the work any good?
CodeHerder has six server-enforced gates. Each workflow turns on its own set:
- Required fields
- Required verifications
- Checklist gates
- Approvals with separation of duties
- Dependency and close gates
- Change-size limit
The default story workflow uses required fields and a checklist. It also needs a passing verify check. Approvals and size limits are opt-in on a custom workflow.
CodeHerder runs on its own gates. This codebase carries 45,032 go test functions in the suite, built the way your work would be.
Read every gate →See what CodeHerder has shipped →
Who is accountable?
Agents review and merge the work by default. No person approves it. To require one, use a git-host approval. The merge stage tells the agent to block the task when that approval is missing. This holds only if your host denies the merge identity approve and bypass rights.
You can also add an approval gate to the entry stage of a custom workflow (Starter plan and up). A member you choose then approves each task before an agent starts. A checklist gate blocks a move past the proof stage of any unticked acceptance item. It applies to workflows with a checklist. The story workflow has one. The activity feed records each status change and each comment. It records each blocker too.
Approvals and staying in control →How work flows →Activity feeds →
What is the risk?
Each task gets its own git worktree and branch. Overlapping edits raise an alert, and the merge agent resolves conflicts. Agents run on devices you own, or in your own AWS account. We do not run them. Billing goes to your own AI account, through an API key or a subscription login. A self-hosted deployment keeps coordination inside your own perimeter.
Isolating agent runs on a device →Security →Answers for your security review →Self-hosting →What happens when it gets it wrong →
Does everyone deliver work the same way?
Without a shared process, each engineer runs agents their own way. Checks and hand-offs depend on who runs the agent, and progress is spread across chats and terminals.
In CodeHerder the team defines its workflows once. Each stage's prompt lives in the shared stage library and is versioned. Skills and the workspace wiki reach every session. The server enforces each workflow's gates, whoever filed the task. Set these in a group and every workspace under it inherits them. Custom workflows and stage prompts need the Starter plan.
One process for the whole team →Customising workflows →The stage library →Skills →