# Try it on your own repo before you ask anyone

Install the ch CLI and run a real agent task in your own git repository. You need no account. The session bills your own model provider.

Source: https://codeherder.com/for-developers/

Install one binary. Describe a task in your own repo. An agent builds it on a local branch. You need no account.

[Try it on your repo](https://codeherder.com/for-developers/#try-it) [Request access →](https://codeherder.com/get-started/#request-access)

Cost and lead time measured across 280 shipped stories, the week of 9–15 November 2026. Task count from /examples#dev.

## Try it on your own repo, with no account

Start with `ch example`. It gives one small job to an agent in a temporary repository, shows you the result and deletes the repository. After that, point `ch task start` at your own checkout.

--follow ch task result

" data-astro-cid-kenkipkp>

ch · no account needed

```
# 1. Install ch. It needs no sign-in.❯ curl -fsSL https://app.codeherder.com/cli/install.sh | sh# 2. Run the whole loop on a disposable repository.❯ ch example# 3. From your own git checkout, start a real task.❯ ch task start "fix the flaky login test"# Not sure yet? Preview it. This creates nothing.❯ ch task start --check# 4. Watch it, then take the result.❯ ch task show <taskId> --follow❯ ch task result <taskId>
```

`ch example` asks you to confirm before it creates anything. Read every flag in [run a task on your own machine](https://codeherder.com/docs/local-tasks/).

## What you need, and what it costs

- A coding-agent CLI. It must be installed and signed in on your machine. See [the supported agents](https://codeherder.com/works-with/).
- A git repository. If the folder has none, `ch` offers to create one.
- macOS or Linux.
- Your own model provider account. The agent session calls your provider for real, so it bills you.

## What it does to your repo

- The task works on its own local branch and commits there. It needs no hosted pull request.
- `ch task start --check` only previews. It creates nothing.
- `ch task result <taskId> --accept` keeps the branch. `--discard` deletes it.
- You decide how to merge the branch into your own work.
- You can make a check required. Then the task cannot advance until the check passes. See [every gate](https://codeherder.com/verification).

## Tasks developers filed

The CodeHerder team filed these briefs against its own code. Each page shows the cost and the lead time, and links the diff.

- "Nine of the SPA's realtime event subjects route to zero cache invalidations, so the Members, Repos, Secrets, Integrations and Plan screens never live-refresh — a second viewer sees stale data until they navigate away and back."Wired live-refresh for the missing subjects, and rewrote the guard's admission table so what's left out has a durable reason instead of "out of scope for this refactor."$11.93 · 48m [Read the full story →](https://codeherder.com/examples/realtime-cache-invalidation-gap/)
- "internal/loccensus's Ingest re-inserts every per-area breakdown row one at a time inside the same transaction as the snapshot upsert, up to 64 single-row INSERTs per ingest instead of one multi-row INSERT."Replaced the per-area insert loop with one multi-row INSERT, built the same way an existing webhook batching helper already does it. $12.79 · 3h 26m [Read the full story →](https://codeherder.com/examples/loccensus-batch-insert/)
- "A blur-triggered validation probe found five form routes with no observable validation-error element, and no route had been tested for a submit-click or a server-error state at all."Drove all five routes with a real submit click, added a server-error test arm, and extended the browser check so this whole state family has real coverage, not just the blur case. $15.47 · 3h 56m [Read the full story →](https://codeherder.com/examples/form-validation-coverage-gap/)

## When your team joins

Run `ch auth login` to move a local repo into a cloud workspace. Read [move a local repo to the cloud](https://codeherder.com/docs/connect-a-local-repo/). Hosted access is invite-only today. The hosted service adds more:

- A cloud workspace where your team can see every task.
- Tasks that span several repositories. See [multi-repo tasks](https://codeherder.com/docs/multi-repo-tasks/).
- Agents on a device you choose. See [where agents run](https://codeherder.com/where-agents-run).

Setting up a team? Follow [get started](https://codeherder.com/get-started).

## Questions developers ask

Do I need an account to try CodeHerder?

No. Install ch with one command, then run ch example or ch task start. The local path needs no CodeHerder account and no workspace. Hosted access is invite-only.

What does the local path cost?

The agent session calls your own model provider, so it bills your account. ch example tells you this and asks you to confirm before it creates anything.

Which agent CLIs does it use?

It uses a coding-agent CLI that is installed and signed in on your machine. If several are ready, pass --harness `<key>` to pick one. See /works-with for the list.

Does it push code or open a pull request?

No. The task works on a local branch and commits there. You review it with ch task result, then accept or discard it. You decide how to merge the branch.

How do I make a test required?

Edit the code stage with ch stage edit and mark a verification as required. A required check can block the task until it passes. ch project init --checks saves the commands it detects, but it never makes a check required.

How do I move to a team workspace?

Sign in with ch auth login. Then move the local repo's tasks into a cloud workspace. See /docs/connect-a-local-repo for the steps.
