Terminal and CLI

#One Installed Application

The daita command is bundled with daita-agents:

pipx install daita-agents
daita

With no subcommand, daita opens the full-screen Textual application. It handles onboarding, chat, source and MCP management, permissions, jobs, routines, inbox outcomes, approvals, and external-editor handoff without falling back to a second line-oriented interface.

Select an agent and workspace explicitly when needed:

daita --workspace /absolute/path/project --agent atlas

Global --root, --workspace, and --workspace-sensitivity options appear before the subcommand:

daita --root /absolute/path/daita-state \
  --workspace /absolute/path/project \
  sources atlas

#Terminal Controls

Inside the terminal:

• /help shows the shipped commands.
• Typing / opens a filterable command palette.
• Typing @ selects a registered source for one question without changing the persistent default.
• /files <question> runs with workspace tools only.
• /workspace shows the admitted local workspace.
• Ctrl-J inserts a newline and Enter submits.
• Ctrl-C cancels an active run when no application-owned selection exists.
• Ctrl-O shows or hides the most recent run's recorded tool calls and results.
• Ctrl-D exits from an empty prompt.

Memory and skill editing commands use $EDITOR; Textual temporarily restores the ordinary terminal and then reacquires the application UI.

#Agents and Sources

daita --workspace /absolute/path/project create atlas
 
daita --workspace /absolute/path/project \
  attach atlas sqlite /absolute/path/warehouse.db \
  --source-name Warehouse
 
daita --workspace /absolute/path/project \
  attach atlas postgresql \
  --host db.example.com \
  --database analytics \
  --username daita_agent \
  --password-env POSTGRES_PASSWORD \
  --schema public \
  --ssl-mode require \
  --source-name Analytics
 
daita sources atlas
daita detach atlas <source-id> --yes

Only sqlite and postgresql are attach kinds. Local CSV, TSV, JSON/NDJSON, and Parquet files remain in the admitted workspace and are queried through Files tools.

Use /source edit for an atomic redacted connection handoff and /source permissions for exact read and PostgreSQL update scopes.

#Run and Terminal Alias

Run one request and write one JSON result:

daita --workspace /absolute/path/project \
  run atlas "Summarize revenue by region" \
  --model openai:gpt-5.6-terra

Continue a conversation, restrict the run to workspace files, or emit lifecycle events:

daita run atlas "Compare it with last quarter" \
  --model openai:gpt-5.6-terra \
  --conversation-id <conversation-id> \
  --events-jsonl
 
daita run atlas "Summarize the release notes" \
  --model openai:gpt-5.6-terra \
  --files-only

daita chat atlas is a retained alias for the same full-screen application as daita --agent atlas. Model setup happens inside the app; chat is not a second chat implementation.

#Knowledge

daita memory read atlas --target memory
daita memory edit atlas --target user
daita memory inspect atlas
daita memory review atlas --model openai:gpt-5.6-terra --cost-limit 0.05
daita memory list-candidates atlas --status awaiting_review
 
daita skills list atlas
daita skills show atlas monthly-revenue-review
daita skills save atlas monthly-revenue-review \
  --description "Compare monthly revenue." \
  --instructions-file /absolute/path/monthly-review.md

#MCP, Artifacts, Jobs, and Automation

/mcp
/jobs
/routines
/inbox

Headless lifecycle groups include:

daita mcp --help
daita artifacts --help
daita export-location --help
daita routines --help
daita inbox --help

Save a known artifact or keep scheduled work progressing:

daita artifacts save atlas <artifact-id> \
  --destination /absolute/path/exports
 
daita --root /absolute/path/daita-state \
  --workspace /absolute/path/project \
  host --agent atlas

The resident host owns the ordinary agent-home writer lock. Stop it before opening the same agent in another TUI or CLI process.

#Destructive Commands

Headless destructive operations require explicit confirmation:

daita detach atlas <source-id> --yes
daita conversations clear atlas --yes
daita mcp revoke atlas <binding-id> --yes
daita delete atlas --yes

Detaching never changes source data. Clearing conversations preserves approved memory, user profile, semantics, and skills, plus durable state still rooted by jobs, routines, or deliveries. Agent deletion removes the inactive agent home and Daita-owned credentials but never deletes attached data or user-owned artifact copies.