Command reference

The qargi command reference: every command, verb, argument and option, the help topics, files and environment variables, from the release it names.

Updated 2026-11-05

qargi dispatches one-off, task-scoped development tasks to sandboxed agents and takes the work back as reviewable patches. An agent is a member on this machine (local, the default) or a cloud agent (only when you ask for it in that request). Agents work in their own clone and never push. A team adds a lead that coordinates members for build, write and review on one task. Everything qargi stores about you and your projects lives outside every repository. Inside a project's repository you can leave out its name.

A gathering place for agent work: dispatch, review, remember. This reference is generated from the command description of qargi 0.2.1, so it matches that release.

Set up #

Command	What it does
`project`	Store the answers about a project, once, outside the repository
`methodology`	List and inspect the development and release methodologies
`cloud`	Which ant profile and workspace each project uses
`agent`	Name the members: the local agents that do the work
`role`	List and check the roles: what a member or cloud agent is for
`provider`	List and check the model providers: tiers, models and what each can do
`provision`	Create the cloud agent, deployment and environment of an instance
`env`	What a repository declares about its development environment
`instances`	Register, inspect and manage agent instances
`skill`	Create or import skills and attach them by scope
`tool`	Create or import tools (MCP servers with an allowlist) and attach them by scope
`packs`	Render, load or apply the skills and tools a role gets
`discover`	Find, recommend and install tools for the roles of a project

Run a task #

Command	What it does
`feature`	Develop on a feature branch; merge it into develop once, when complete
`marshal`	Who leads which open feature: lease, status, goal, plan, handoff
`release`	Releases and hotfixes by the git-flow rules
`branch`	Branch housekeeping: delete the merged agent and feature branches and their worktrees
`changelog`	Numbered changelog items: find duplicate numbers and renumber them
`upstream`	Follow an upstream repository: how far behind, what is new, sync its branch
`ref`	Record in the lead's ref journal a branch move that no flow verb made
`start`	Start a standby cloud session for an instance
`send`	Send a task to an idle cloud session
`status`	Show tracked cloud sessions, or one session
`report`	Cost per applied change, what waits for review, what looks stuck
`noticed`	What members noticed and did not act on, and what became of it
`watch`	Wait for a cloud session to stop; prints one line when it does
`collect`	Download a session's output files into a fresh directory
`stop`	Interrupt a running cloud session
`close`	Archive a finished cloud session
`mark`	Record what happened to a session's work
`track`	Track a session that was started elsewhere (for example in the console)
`local`	Prepare, verify, list and clean a local run that has no way to push
`supervise`	Find stalled agent runs: notify, prepare a nudge, never act alone

Review and apply #

Command	What it does
`review`	Check what an agent returned and put it on a task branch
`team`	Run a task with a lead and role agents (opt-in)

Memory #

Command	What it does
`memory`	Check a memory store, list its tiers, read a note, split, merge or copy stores
`canon`	Bring a project's two memory stores to the standard layout and keep them there

Lead and credentials #

Command	What it does
`lead`	The lead session: its context, and the cloud lead's right to push
`credential`	Check or set up the tokens qargi uses
`hook`	Claude Code hooks

Export and import #

Command	What it does
`export`	Save a project's setup, definitions and memories to one file
`import`	Restore from an export, choosing what and how

Other #

Command	What it does
`upgrade`	Move the installed tool to a newer branch or tag of its origin
`help`	Show help
`version`	Print the version

Topics, files and environment #

Help topics: the ideas behind the commands.
Files: what qargi stores and where.
Environment: the variables it reads.

Typical use #

Once per project

qargi project template acme > acme.json   # edit it
qargi project init acme --answers acme.json
qargi provision plan acme-build    # then apply it with --plan and --approved

One task, cloud

qargi send acme-build "$BRIEF" --label rename-verb --asked "use the cloud builder"
qargi watch SID    # in the background
qargi collect SID ./out
qargi review check ./out

A team

qargi team brief acme code-docs --task "rename the verb" --done "make test" --base develop
qargi lead status acme
qargi team check ./run