Your prototype works. Changing it is the hard part.
CodeHerder does not build an app from a prompt. You file each change as a task. An agent does the work in your own repository. Other agents review and verify the work in a Story, Feature or Bug task.
Where CodeHerder fits
Pick the tool that matches where your idea is today.
You have no code yet
A prompt-to-app builder gives you a first working version fastest. Use one for this step. Come back when that version has a repository.
You have a prototype, and changing it feels risky
CodeHerder starts here, with a repository that already exists. File the next change as a task. Agents build it and merge it after review.
You already have engineers shipping code
Your team may already run a coding agent. See /compare to learn how CodeHerder runs many agents on many tasks at the same time.
A prototype gets hard to change at a certain size
A single prompt does not solve these problems. Each item names the stage that helps.
The change is too big for one prompt
A Story, Feature or Bug task has a plan stage. An agent writes its plan in the task before it writes code. You can read the plan and add a comment. By default, no person approves a stage. To require approval, add an approval gate to a stage. See /how-it-works for the full pipeline.
A fix breaks two other screens
The same three workflows have a review stage. A plain Task goes from code to merge. The review stage runs as a separate, read-only session. It reads the diff and the acceptance criteria. It approves the change, or it sends the task back to code. See /verification for every gate a task passes through.
Nobody reads the diff
The same three workflows have a verify stage. It runs after merge. The verify stage checks the change in the deployed app. It records the commit and the behavior it confirmed in the task. If the check fails, the task goes back to code. See /when-agents-get-it-wrong for what happens when an agent makes a mistake.
What to prepare before day one
A git repository you own
Use the repository where your prototype's code already lives. It must be on github.com or gitlab.com. CodeHerder does not host your code. Agents work in their own copy of it.
A device that runs your agents
A device is a machine that runs
ch device-server. See /where-agents-run for every way to connect one.A git credential for agents
Add a git token with
ch device git-token create. Or let the device mint app tokens. CodeHerder makes its own branch for each task and opens a request to your base branch. Then the merge stage merges that request into the base branch. By default, no person approves the merge. To require approval, add an approval gate or branch protection.
No repository yet? Build your first version elsewhere. Come back once it exists. See /will-it-work for the full fit check. Weighing a freelancer instead? Read freelancer or agents.
File one small, checkable change first
Pick a change that is small enough to check when it is done. You can copy and file each of these three as it is.
A control that is cut off on a phone
File the button or menu that gets clipped on a narrow screen, and get it fixed.
Real cost, start to finish: $20.87.
Read the full brief →Add a field to a form we already have
Name the field, where it should live on an existing form, and get a working save-and-show for it.
No real task in examples.ts matches this brief's exact shape yet. What's real is the mechanism: an agent extends a form and its saved record together, in the same change, so the new field works end to end rather than only on screen.
Read the full brief →Add a filter to a list we already have
Name the list and what you want to narrow it by, and get a working filter control for it.
No real task in examples.ts matches this brief's exact shape yet. What's real is the mechanism: an agent adds a filter through the same query the list already uses. Paging and sorting keep working, instead of drifting out of sync with a client-side hide.
Read the full brief →
More ready-to-file briefs at /starter-briefs. Already have your own wording? Run it past the brief checker first.
Common questions about a first task on a prototype
Will CodeHerder build my app from scratch?
No. CodeHerder works on a repository that already exists. Build your first version with a prompt-to-app builder or a developer. Then bring the repository here for the next steps.
What does CodeHerder need before it can help?
You need a git repository on github.com or gitlab.com. You also need a device that runs your agents and a git credential. Add a git token with ch device git-token create, or use app tokens that the device mints. CodeHerder makes its own branch for each task. See /will-it-work for the full list.
My prototype has no tests and no real structure. Does that matter?
Not for a first task. An agent reads the code as it is. Pick one small change that you can check. A Story, Feature or Bug task adds a plan stage. It also adds review and verify stages. These stages check the work and help to find what the agent missed. A plain Task goes from code to merge.
Can I start with something small?
Yes. File one change, such as a cut-off button or a missing field. It becomes a task, then a merged pull request or merge request. /starter-briefs has ready-to-file examples.
What if I don't have a repository yet?
Build your first version elsewhere, with a prompt-to-app builder or a developer, then come back. CodeHerder needs a real repository to start from.
Bring your repository. Start with one change.
Request access first. Then connect a device. Add your repository and file one small task.