Manual
Depaza Code CLI manual
Everything the CLI can do — install, login, every command, the interactive session, the team, configuration and troubleshooting.
Covers depaza v0.27.0 · run depaza --help for the same reference offline.
Install & update
Depaza Code CLI is a Python package (depaza-cli, the depaza command) and needs Python 3.10 or newer. Install it once, globally:
The CLI checks for a new version in the background on launch (at most once a day, non-blocking). Update manually any time:
depaza updateVerify with depaza --version. Enable shell tab-completion with depaza --install-completion, then restart your shell.
Login & access
Connect the terminal to your Depaza account once. depaza auth opens your browser, you approve the device, and the key is written to ~/.config/depaza/config.toml (file mode 0600).
depaza authdepaza whoamidepaza usageAll paid plans (Pro and above) have instant Code CLI access. Free accounts can be granted access via a redeem code from an admin.
depaza redeemAdvanced: paste a key non-interactively with depaza auth --key dpz_live_…, or set DEPAZA_API_KEY in the environment (handy for CI).
Commands
Run depaza with no arguments to open the interactive session, or use a one-shot command. Coding commands accept --model / -m <lite|core|max> and --auto / -y (approve edits and commands automatically).
Coding
depaza chatdepaza codedepaza fixdepaza reviewdepaza newdepaza initdepaza prdepaza screenshotTeam & Council
depaza teamdepaza huddledepaza solvedepaza evaldepaza solve writes to solution.py by default (-o), authors a pytest oracle if you omit -t, and runs 2–5 Council members (-n, default 4).
Account & system
depaza modelsdepaza permissionsdepaza hostsdepaza configdepaza mcp listdepaza syncInteractive session & slash commands
Run depaza (or depaza chat) to open the session. Type naturally to give the team work; it reads and searches files, makes precise edits and runs commands, then verifies its own changes. Press Shift+Tab to cycle the approval mode shown in the toolbar.
Address a teammate by name for a direct request — Emma, plan the billing flow, Bob, implement it, Anna, review this, Max, check the architecture — or say Team, … to run the full pipeline (Emma plans → Bob builds → Anna reviews).
Slash commands — type / for completion:
/helpShow all commands./teamMeet the team / run the full pipeline./emma📋 Plan it (PM — never codes)./bob🐥 Fast first-pass implementation./max🦾 Senior: architecture & hard calls./anna🔎 QA: tests, edge cases, GDPR./huddleWhole team analyzes in parallel, then synthesizes./pasteRead a screenshot from the clipboard./modelSwitch model (lite | core | max)./planPlan mode — approve before coding./normalApprove each action./yoloNo approvals./modeCycle plan → normal → yolo./diffShow uncommitted git changes./undoRevert the last file changes./rewindUndo the last n turns (files + chat)./compactShrink the conversation context./memoryShow the team's saved lessons./rememberSave a lesson for future runs./resumeResume a past session./usagePlan limits + usage./costSession size + plan usage./exportWrite a markdown transcript of this session./configOpen the configuration UI./clearStart a fresh conversation./exitQuit.The team
Depaza is not one model — it is a small team, each running the EU-hosted tier that suits their job. Call them by name in a session, or with the matching slash command.
| Teammate | Role | Best for |
|---|---|---|
| 📋 Emma | Product Manager | Clarifies the goal and writes the numbered plan — never codes. |
| 🐥 Bob | Junior Developer | Eager, fast first-pass implementation. |
| 🦾 Max | Senior Engineer | Architecture, refactors and the hard calls. |
| 🔎 Anna | QA & Testing | Adversarial tests, edge cases, GDPR — read-only guardian. |
Run depaza team to see which model each teammate is on. depaza models shows the orchestrator / coder / verifier strategy and how to override any role.
Approval modes & permissions
Every file edit and command asks for approval — with a diff or command preview — unless you opt out. Three modes, switched live with Shift+Tab or the slash commands:
| Mode | Behaviour |
|---|---|
| plan | Propose a numbered plan and wait for approval before making changes. |
| normal | Approve each action (edit / command) individually. The default. |
| yolo | Auto-approve everything for the rest of the session. |
Start a run unattended with --yolo (or per-command --auto / -y), or pre-plan with --plan. At any approval prompt you can type yolo to switch for the rest of the session.
Permission rules give fine-grained control. A rule is a tool name with an optional glob — edit_file, run_bash(git *), write_file(/etc/*), mcp__*. Deny always wins.
depaza --allowdepaza --denydepaza permissionsAdd --sandbox to confine run_bash (no network; writes limited to the project) where the OS supports it. The agent's tools span read-only (read_file, list_dir, glob, grep, web_search), mutating (write_file, edit_file, run_bash) and remote ops (ssh_run, scp_upload / scp_download, rsync_sync) via your ~/.ssh/config host aliases.
Configuration
Settings live in ~/.config/depaza/config.toml (mode 0600). Edit it with the interactive UI — depaza config — or by hand. Environment variables override the file, which is useful in CI.
config.toml sections
| Section | Keys |
|---|---|
| [auth] | api_key, base_url (default https://depaza.com/v1) |
| [preferences] | default_model (lite | core | max, default core) |
| [permissions] | auto_approve, sandbox |
| [roles] | orchestrator_model, coder_model, verifier_model |
| [local] | mini_enabled, model_path, model_url (opt-in on-device model) |
| [sync] | enabled (upload sessions to the EU dashboard) |
Environment variables
| Variable | Purpose |
|---|---|
| DEPAZA_API_KEY | Your dpz_live_… key. |
| DEPAZA_BASE_URL | Override the API endpoint (self-hosting). |
| DEPAZA_AUTO_APPROVE | Set to 1 to auto-approve edits and commands. |
| DEPAZA_SANDBOX | Set to 1 to confine run_bash. |
| DEPAZA_DEBUG | Set to 1 to log raw API traffic to ~/.config/depaza/debug.log. |
| DEPAZA_LOCAL_MINI | Set to 1 to enable the on-device mini model. |
| DEPAZA_ORCHESTRATOR_MODEL / _CODER_MODEL / _VERIFIER_MODEL | Override the model tier for a role. |
Depaza uses open-source LLMs. You can run the CLI with your own local open models (Ollama, vLLM, or Depaza's local-optimized ones) or our EU-hosted versions. The agent team and orchestration are the same. See active tiers with depaza models. Pass --no-orchestrator to use a single model.
Custom commands & MCP
Custom slash commands. Drop a markdown file in ~/.config/depaza/commands/<name>.md (user-level) or ./.depaza/commands/<name>.md (project-level, wins on conflict) to add your own /<name>. Optional YAML front-matter sets a description:; the body is the prompt, with $ARGUMENTS replaced by whatever you type after the command.
MCP servers. Connect external tools over the Model Context Protocol. Configure servers in ~/.config/depaza/mcp.json or ./.depaza/mcp.json, then list them with depaza mcp list. MCP tools appear to the agent as mcp__<server>__<tool> and obey the same permission rules.
Project conventions. A DEPAZA.md (it also reads AGENTS.md / CLAUDE.md) in your repo root is loaded into every session. Generate one with depaza init.
Sessions, undo & headless
Sessions are saved automatically. Resume the most recent one in this directory, or pick from the last ten:
depaza --continuedepaza --resumedepaza resumedepaza sessionsdepaza undoInside a session, /rewind undoes the last few turns (files and chat together) and /undo reverts the most recent edits.
Isolated & headless. Use --worktree to run in a throwaway git worktree and review/merge on exit. For scripts and CI, run headless:
depaza --printHeadless output formats are text (default), json and stream-json. Mutating tools stay denied headless unless you pass an --allow rule or --yolo. Add --transcript <path> to write a full markdown reasoning/tool trace.
Troubleshooting & getting help
Something off? Run with --debug (or set DEPAZA_DEBUG=1) to log raw API requests and responses to ~/.config/depaza/debug.log.
depaza whoamidepaza updatedepaza welcomeTab-completion not working? Run depaza --install-completion and restart your shell. Local config lives under ~/.config/depaza/ — remove config.toml to start clean, then run depaza auth again.
Operators have a server-gated depaza admin command group (stats, users, plans, costs and search administration). It is restricted to the super-admin allowlist and is out of scope for this manual.
Need a hand? Run depaza help for branded examples, or reach us via the CLI overview and your dashboard.
Get started
Put the whole team to work today
Emma, Bob, Max and Anna are ready in your terminal — EU First, EU-hosted and GDPR-ready. Pick a plan and connect in under a minute.
Paid plans (Pro+) get instant Code CLI access — just run depaza auth. Free accounts may receive a redeem code.
This manual mirrors depaza --help. The CLI and all of its models run inside the EU.