Skip to content
PricingReleases

CLI Reference

Every Recursive install ships the recursive command — a terminal client for the same Product API the dashboard uses. Use it interactively, in scripts, or hand it to an AI agent: every resource supports --json output.

The CLI is bundled with the desktop app. After installation, recursive is on your PATH (the app’s installer links the binary). Verify:

Terminal window
recursive --version
Terminal window
recursive <resource> <verb> [flags]
ResourceVerbs
serverstart, stop, status
configget/set operations for app configuration
sessionlist, status, start, delegate, merge, archive
tasklist, create, get, update
MCP-backed resourcesproject, memory, settings, plugin, automation, inbox, metric, adapter, favorite, macro, schema, preview, terminal

MCP-backed resources are auto-discovered at runtime from the connected server’s tool schemas, so a plugin that adds tools extends the CLI automatically.

FlagPurpose
--jsonOutput raw JSON (for agents and scripts)
--serverServer URL (default: http://localhost:12321)
--tokenAuth token for remote servers
--helpShow help for a command
--versionShow version

Run recursive with no arguments in a terminal to open the interactive TUI dashboard. Run recursive <resource> to list that resource’s verbs, and recursive <resource> <verb> --help for flag details.

List sessions as JSON:

Terminal window
recursive session list --json

Delegate a task to an autonomous agent:

Terminal window
recursive task create \
--title "Add /health endpoint" \
--description "Return { status: 'ok' } with dependency checks" \
--json

Point at a remote instance over remote access:

Terminal window
recursive --server https://your-box.example.com \
--token "$RECURSIVE_TOKEN" \
session status s_abc123

Each CLI verb maps one-to-one onto a Product API operation documented in the OpenAPI specification. If you can call it with the CLI you can call it with curl, an SDK generator, or an MCP client.