delos-cli

A terminal REPL for Delos — the Claude-Code-style CLI for the Delos agent.

Talk to your Delos AI from any shell. Streaming Markdown answers, slash commands, and tools that read and edit your local files (with your approval), all in a TUI that lives in your terminal.

Install

uv tool install delos-cli

Or with pipx:

pipx install delos-cli

Sign in

delos login --region eu       # or "us" / "ae"

The browser opens, you sign in to your Delos workspace, and the CLI saves your tokens to ~/.config/delos/.

Run

delos

Conversations are scoped to the directory you launch from — running delos in ~/projects/foo shows only chats started in ~/projects/foo. Pick an existing one to resume, or start a fresh one.

In the REPL

Slash commands

/help                 list commands
/clear                wipe the screen and start a fresh conversation
/rename <new name>    rename the current chat
/mode [name]          show or set the mode: ask, plan, auto, build (default: build; shift-tab cycles)
/delete               delete the current chat and go back to the picker
/resume               back to the picker without deleting
/stop                 interrupt the agent
/usage                show plan usage limits and remaining credits
/context              show what fills the agent's context window
/quit                 exit

Local MCP servers

The CLI runs the stdio MCP servers declared in a .mcp.json (the Claude Code format) and gives their tools to the agent as mcp__<server>__<tool>. They execute on your machine, after the same permission prompt as shell commands, so keys stay local.

• global: ~/.config/delos/mcp.json
• project: the nearest .mcp.json up to the repo root (wins on a name clash)

{
  "mcpServers": {
    "my-server": {
      "command": "uvx",
      "args": ["my-mcp"],
      "env": { "TOKEN": "${MY_TOKEN}" },
      "timeout": 600
    }
  }
}

timeout is per call, in seconds. A project server only starts once you approve it in /mcp, and again whenever its command, args or env change. Server logs: ~/.config/delos/logs/mcp-<name>.log.

Remote MCP servers

A remote entry ("type": "http" with a url) is not run by the CLI: checking it in /mcp imports it into Delos as your own connector (nobody else in the org sees it), opens its OAuth consent in your browser, then enables it for the coding agent. Its tools then run server-side, through Delos, like any other connector. Not supported yet: entries with headers, and URLs only your machine can reach (localhost, private addresses, .local).

d in /mcp (or "Remove from Delos" in VS Code) removes your own import and your credential for it; the entry stays in .mcp.json, and checking it again imports it afresh — the way out of an import that went wrong.

Headless mode (VSCode extension engine)

delos serve --app vscode --workspace /path/to/project

Runs the agent as an NDJSON server over stdio — no TUI. This is what the Delos Code VSCode extension spawns under the hood: user messages and RPC requests come in on stdin, agent events / permission requests / RPC responses go out on stdout (one JSON object per line), logs go to stderr. See apps/vscode/DEVELOPING.md in the monorepo for the protocol reference.

Requirements

• Python 3.14
• A Delos account

Uninstall

uv tool uninstall delos-cli

Made by Delos Intelligence.