DeepChat CLI

Use the bundled deepchat command to ask the running DeepChat main process to perform supported operations. The main process remains the sole owner of providers, credentials, Skills, MCP servers, artifacts, Agent runs, and approvals.

Command rules

• Every command must begin exactly with deepchat <domain> <verb>. Put --json, --jsonl, --timeout, and all domain options after the domain and verb.
• Execute one standalone command per exec call. Do not use pipes, redirection, command separators, command substitution, environment assignments, or shell wrappers around deepchat.
• Quote every user-controlled argument for the current shell. Never interpolate untrusted text into an unquoted command.
• Prefer --json for one result and --jsonl for streaming or benchmark collection. Use text mode only when its output will be returned directly to the user.
• Do not inspect authentication environment variables or DeepChat's local descriptor. Authorization is injected only after the command has passed the normal shell permission check.
• A shell approval authorizes command execution. Sensitive mutations can additionally pause for a renderer approval; wait for that decision and never attempt to manufacture confirmation data.
• Use deepchat help or deepchat <domain> <verb> --help only when the options below are insufficient. Do not probe undocumented routes.

Agent file and recursion boundaries