For product people & non-technical builders
You have the idea. You don't have an engineer.
Write the task as you would to a teammate: what is wrong, or what you want. Pick Story as the type. An agent plans the work. Then it builds the change and opens a pull request.
- 7
- Real tasks filed in plain English
- $3.05–$29.54
- Cost range, start to finish
- $21.75
- Median cost
Total cost of the seven plain-English tasks in /examples#nocode, over each task's whole life.
What people wrote
Three real tasks, filed exactly like this
The form has no ticket template. Only the title is required. These are the exact sentences three people typed into the web app, and what came back.
"Missing skills link in Set Up section on Group"
Added the missing nav link, so a Skills workspace a group inherits is reachable from that group's own Set up section.
"Drop down arrow cut off on mobile. There is now also no way to get to your profile on mobile."
Fixed the mobile topbar overflow, which also restored the only path to Profile, Theme, and Sign out on a phone.
"We recently changed it so that devices didn't keep the names of the ec2 servers they were created from - probably an ok change... but what it has been replaced with is useless... some hash that means nothing..."
Added an operator-set device name that now wins everywhere a device is shown, with the old hostname kept as a fallback.
Four more like these, all filed by people who do not use the CLI or git, at /examples#nocode. If a word like task or orchestration is new to you, the glossary defines it in plain English. Do you have engineers who are booked? See for product teams. Do you need a specific job done? See ship a small feature and clear the bug backlog. Do you want a ready-made starting point? Copy one from starter briefs.
After you save
What happens after you save a task
In the New task form, the Workflow field preselects Task. A Task goes straight to code and merge. Pick Story to add a plan, then a review, then a final check. Agents run each stage.
An agent writes the plan
Before any code exists, an agent writes what it will do and why. You can read the plan. To change it, send the task back to plan with a note. The agent does not wait for your approval.
A second agent reviews the code
The review runs in a new session on a different model tier. If review rejects the work, the task goes back to code.
A third agent checks the result
After merge, the verify agent records proof that the change does what the task asked. If something is still wrong, reopen the task with a note.
By default, no person approves the plan, the code or the result. To require a person, ask your developer to turn on required approval on GitHub or GitLab. Then no change merges until a person signs off.
Before day one
What you need before the first task
A repository
Your code stays where it lives now. CodeHerder never hosts it.
One connected machine
A laptop or a small server works. Each agent session gets its own copy of your repo (a git worktree) and its own branch.
About an hour of a technical person's time, once
A developer or your IT team must connect that first machine. Borrow one for an hour. Or see where agents run for a one-click option that needs no CLI. It needs your own AWS account. After that, you work in the browser. You can file a task there. You can also read it and reopen it.
See the exact setup steps →. Do you already have a prototype? See /prototype-to-production for the next step.
How the work gets checked
How a Story gets checked
Plan
An agent writes the plan and an acceptance checklist before it writes code.
Review
A separate agent checks the code. The agent that wrote it does not review it.
Merge
The merge agent merges after review. Your git host's branch protection decides if a person must approve first.
Verify
An agent checks the merged change against the task and records the proof.
A plain Task has none of these checks. See how each check works at /verification, and where your code and keys stay at /security.
What it costs
What seven real tasks cost, start to finish
Each figure is the total cost of one task over its whole life. It covers the seven plain-English tasks in /examples#nocode. CodeHerder prices recorded token use at published API rates.
Estimate your own workload at /calculator, or see the plans at /pricing. Do you want to compare a freelancer? Read freelancer or agents.
FAQ
Questions before you file your first task
Do I need to know how to code?
No. Write the task as you would write a message to a teammate. Say what is wrong, or what you want, in plain words. You do the daily work in the web app. You do not need the CLI or git to file a task or to reopen it. A developer connects the first machine.
Who fixes it if the agent gets something wrong?
Pick Story as the task type. A second agent reviews the code, and a review reject sends the work back to code. You can read the plan and reopen a finished task with a note. By default, no person approves the work. A required approval on your git host adds one.
Do I need my own repository?
Yes: one repo and one connected machine, set up once by a developer or your IT team. See /where-agents-run for the setup options, including one with no CLI install. After that, every task you file runs against your own code, in its own git worktree and branch.
Can I try one small thing first?
Yes. File a task for a broken layout or a missing link. Watch it go from one sentence to a merged fix. /examples has real ones, filed by people who do not use the CLI, with cost included.
What happens to my source code?
Your repository stays on your own machine, and CodeHerder never hosts it. An agent works on a copy on your connected machine and opens a pull request when it is done. CodeHerder does see terminal output and commit messages. It also sees changed file paths and branch names.
What if I disagree with the plan?
Leave a comment, or send the task back to plan with a reason. The agent does not wait at the plan stage. A comment reaches a live session on the task, or the next session. A send-back makes the agent write a new plan.
Write the first sentence.
Tell us what you want built. We will connect your workspace and your first repo.