CLI reference
The zdev terminal command manages development records in .zdev and their
relationship to Git. Use it to inspect work, create areas, update tasks, and
commit completed changes. The Agent commands tell a
coding agent to plan, implement, or verify that work.
Examples
Section titled “Examples”zdev status greetingzdev next greeting --format jsonExamples use an area named greeting and, where needed, a task named
greeting-001. Create the area and import its tasks before running commands
that refer to them. The tutorial walks through setup.
Ask the agent to run a command
Section titled “Ask the agent to run a command”You can ask an agent with terminal access to run any CLI example in this
reference. It needs zdev installed and access to the repository, just as you
would. For example, instead of running zdev status greeting, ask:
Use zdev to show the status of greeting and explain what is ready next.The agent runs the relevant commands and summarizes their output. It might report: “One task is done and one is ready. The area’s branch is safe for task work.” That reports state; it does not start implementation. You can also paste an exact command and ask the agent to run it. The same approval and completion requirements apply when an agent changes records on your behalf.
zdev goal greeting still only renders continuation context when run by an
agent. To start execution, ask it to implement a task or loop through the area.
Find a command
Section titled “Find a command”| Command | Use it to |
|---|---|
| instructions | Print the short workflow instructions for an agent. |
| init | Initialize a repository and choose how to store its records. |
| cleanup | Remove pull-request records before a squash merge. |
| config | Read or change project settings and worker profiles. |
| area | Create an objective and manage its branch and lifecycle. |
| research | Run measured experiments and track research limits. |
| slice | Add a brief for a bounded increment within an area. |
| tasks | Review, import, list, and index task files. |
| task | Read, complete, reopen, or record evidence for one task. |
| next | Select ready work. |
| goal | Render the current continuation goal for an area. |
| work-context | Capture task and Git context for a worker. |
| status | Read task counts and branch health. |
| check | Validate records and relationships. |
| skill | Install or check a coding-harness integration. |
| commit | Commit staged changes with a stable change ID. |
| change-id | Generate a stable change ID. |
| change | Inspect or find commits by their stable ID. |
Global options
Section titled “Global options”--root PATH selects the repository explicitly. Otherwise, zdev discovers it
from the current directory. --format text is the default; --format json
returns structured output for scripts and agents. Both options work on
subcommands as well as on zdev itself.
zdev --root . --format json status greetingzdev task done --helpUse --help at any command level for its full argument list, or --version
to identify the installed binary. In syntax examples, uppercase names are
values to supply, brackets mark optional arguments, and ... means a value
can repeat.