CodeHerderSearch⌘KRequest access →

Ship a product idea without an engineer

Many product ideas sit in a backlog for months. Nobody thinks they are bad. Engineering time just never frees up. You know what “done” looks like: a new page, or a report that nobody builds by hand. But someone who can write code has to build it, and their calendar is full.

CodeHerder gives that work to AI agents. You describe the result in plain words. Agents plan the work, write the code, review it, merge it and check it. You use the web app. This post follows one real task through that path.

A real brief, start to finish

Someone on our team filed this task. They wrote it the way they would tell a colleague:

Drop down arrow cut off on mobile. There is now also no way to get to your profile on mobile.

That is the whole brief. The agents found the cause: the top bar ran out of room on a phone. The same fault hid the entire account menu. They fixed it, added a build-time check that catches the fault if it comes back, and merged the change the same day. The task cost $20.87. Read the full record on the example page.

The brief was short because it was a small bug. For a bigger idea, add a checklist of what “done” means. The playbook shows how.

The five stages

Each task moves through a workflow. The default one has five stages:

  1. Plan. An agent checks that the task is clear.
  2. Code. An agent writes the change and opens a merge request.
  3. Review. A second agent checks the work against your checklist.
  4. Merge. The change joins the main code.
  5. Verify. An agent confirms that the change works.

The task page shows the current stage. You do not need to ask anyone for a status update. You can also open any agent’s live session in your browser and watch the work.

Answer questions when agents ask

Sometimes an agent needs a decision that only you can make. It asks a question and waits. The question shows in the Needs attention section of the Dashboard. Pick an option or type your own answer. The agent then continues. A short answer is fine. “I do not know” is also a valid answer.

Decide where a person must approve

By default, agents move work through every stage without waiting for a person. Review is done by another agent. If you want a human to sign off, you must ask for it.

An approval gate holds a task when it leaves a stage. An admin sets it in the workflow: open the stage and turn on Approval required to leave. Editing a workflow needs the Starter plan or higher. Two gates are common:

  • Gate the plan stage to approve the plan before any code exists.
  • Gate the review stage to approve the result before it merges.

A held task shows under Awaiting your approval on the My work page. Select Approve to move it on. Select Reject to keep it where it is.

What a developer sets up once

One technical step remains. A developer connects your repository and one device. A device is the machine that runs the agents. This takes an afternoon at most, and you do it once. After that, you only use the web app.

Start with one small thing

Pick one bug or small feature that has waited too long. Write the brief. File it, then check the task page later. Our example above took 293 minutes from filed to merged. For a way to write better briefs, read the playbook or try the brief checker.

← Back to Insights

Have an idea but no engineer?

Write what you want in one sentence. An agent builds it, and a person reads the result.

Try "pricing", "connect a device", or "who reviews the code"

↑↓ move · ↵ open · esc close