Using OpenCode or Pi?

Define done before
the code.

Carthagent writes the checks before the code, and only calls a task done when they pass on the current code.

Free with your own model provider.

How it works

  1. Checks first.

    Every requirement gets a check before any code is written.

  2. Stale after a change.

    When the code changes, earlier passes stop counting until they run again.

  3. A clear finish.

    If a check fails, it tries a limited number of fixes. In Ship mode, a task is verified only when every check is current and the change is reviewed. Otherwise it stops as blocked.

Checks can still miss bugs or requirements, so review the result yourself.

Read the workflow on GitHub

One run against Pi.

Same voxel-world task, same model (DeepSeek V4.1 Flash).

Carthagent coding run
8m 58s
Pi coding run
12m 00s
Playable acceptance
Neither passed

One attempt per tool, so it shows neither a general speed nor quality advantage. We haven’t tested OpenCode.

Read the full experiment

Try it on your next issue.

Pick a small change in a project you know. Check the diff and run the result yourself, then compare it with your usual tool.

Keep your own model provider, or use Carthagent Cloud from $10/month.

Official site: carthagent.xyz. CLI: ctg. Source: B-icy/Carthagent on GitHub. Not affiliated with carthagent.com.