To connect Kimi, open Settings → Connections → Connect via API → Kimi / Moonshot. Use Get Kimi key, paste the key, and select Test and save API; URL and format are prefilled. Choose a catalog model and Enable runner for this connection or Prepare execution, depending on status. Add a mission agent with that provider, model, and DSH runner. If K3 is missing, check your Kimi account access. Listing models does not test generation or tools. Kimi, OpenAI, Grok/xAI, OpenRouter, OpenCode Go, FreeLLMAPI, and custom APIs can coexist with separate credentials. The legacy gateway remains for compatibility.
For Grok as a CLI, open Settings → Connections → Use or install CLI → Grok CLI · community. Install on the server using the button (Linux x64 or macOS arm64), or follow the project link. The adapter supports superagent-ai/grok-cli. Use existing authentication in ~/.grok/user-settings.json or GROK_API_KEY, or save an encrypted key in the CLI screen. No API connection registration is needed. Select Check CLI on server, then add Grok CLI with the CLI runner and model. The test checks executable and credential presence; actual tasks confirm access and credit balance. MCP uses separate per-panel configuration, preserving your file.
The CLI reads its process environment. It does not automatically load .env. Export variables before starting or use a process manager. Never commit secrets.
| Variable | Purpose / default |
|---|---|
COCKPIT_HOST | Direct CLI: 127.0.0.1; npm start: 0.0.0.0 if absent/empty. |
COCKPIT_PORT | Port; 4000. |
COCKPIT_TOKEN | Master API/WS token; explicit token authentication is disabled if absent. Network access still requires authorization. |
COCKPIT_LOG_LEVEL | Logging; info. |
COCKPIT_STATIC_DIR | Alternative SPA folder with index.html and assets. |
COCKPIT_HOME | Global project, catalog, skill, and DSH roots; does not change engine state under <cwd>/.cockpit. |
COCKPIT_PROJECTS_FILE | Alternative recent-projects file. |
COCKPIT_CATALOG_PATH | Folder containing an external cockpit.json. Optional; otherwise the bundled catalog is used without searching neighboring folders. |
COCKPIT_CATALOG_CONFIG | Direct cockpit.json path, overriding COCKPIT_CATALOG_PATH. |
DSH_REPO_PATH | DSH checkout; historical default /DATA/Projetos/deepseek-harness. |
DSH_BIN | Entrypoint; default <DSH_REPO_PATH>/apps/cli/lib/bin.js. |
DSH_HOME | Isolated data; default ~/.cockpit/dsh-home or <COCKPIT_HOME>/dsh-home. |
CODEX_HOME | Model cache used by Codex discovery. |
OPENAI_API_KEY, ANTHROPIC_API_KEY | Agent configuration depending on CLI authentication mode. |
GEMINI_API_KEY, ELEVENLABS_API_KEY, REPLICATE_API_TOKEN | Media providers; GPT Image also uses OPENAI_API_KEY. |
Bash example:
export COCKPIT_PORT=4100
export COCKPIT_HOST=127.0.0.1
npm start
COCKPIT_CONNECTION_FILE, COCKPIT_URL, COCKPIT_MISSION_ID, and COCKPIT_PANE_ID are normally injected bridge context. Do not invent IDs or reuse another instance's connection.
#Catalog v1
Without v1, Cockpit uses a bundled catalog. An external cockpit.json may provide profiles, recipes, runners, models, media, environments, and account pools. Use trusted configuration: it can define server commands. Legacy vault data is also read when available; v1 remains optional.