Skip to content

Manual CLI Walkthrough

The exact command sequence for a normal bug fix, small feature, or planned task, once you already know the shape from Tutorial 1 or the Onboarding Guide. This page assumes you know why each command exists; it’s the terse reference, not the walkthrough.

Terminal window
# Once per repository
codev init --target . --agent-platform all
# One normal task
git rev-parse HEAD
codev task start --id <id> --base <base-sha> --summary "<outcome>" --link <url>
codev git branch --id <id> --base <base-sha>
# During build and review
codev task status
codev task record --id <id> --round <n> --role builder --head <sha> --evidence <file>
codev task record --id <id> --round <n> --role reviewer --head <sha> \
--findings <file> --coverage <file> --decision READY_FOR_OUTER_LOOP
codev task check --id <id> --head "$(git rev-parse HEAD)"
# When ready for a pull request
codev git commit --id <id> --message "<message>"
codev git push --id <id>
codev git open-pr --id <id> --title "<title>"
codev git mark-ready --id <id>
# After the human decision
codev task close --id <id> --outcome approved
codev status --target .

--link points to the issue, brief, design, or plan that authorizes the work. For work already represented by a GitHub issue, use --github-issue <number> instead. --outcome also accepts abandoned (intentionally stopped) or escalated (needs an unresolved human decision).

If you started coding before involving CoDev, pick one entry mode deliberately instead of a cold codev task start:

Terminal window
# Unfinished work: let the build loop continue the existing diff.
codev task start --id <id> --base <base-sha> --entry takeover --summary "<outcome>"
# Finished work: skip the build loop and send it straight to review.
codev task start --id <id> --base <base-sha> --entry direct-review --summary "<outcome>"

Preview first, and resolve any reported local changes rather than overwriting them:

Terminal window
codev diff --target .
codev update --target .

Never run init, update, or remove while product code is mid-build.

  • Talking to Your Agent — how this sequence actually gets triggered in normal use: you talk, your agent runs it.
  • Tutorial 1: your first fix — the narrated version of the checklist above, with real output at every step.
  • CLI reference — every command, not just the ones in a normal task.
  • Starting Prompts — copy-paste prompts for the two moments above that are easy to under-specify.