Getting Started
Prerequisites
- A real terminal (macOS Terminal, iTerm2, Windows Terminal, etc.) is recommended for the best TUI experience.
- A recent Node.js is recommended if you install via npm/pnpm/yarn.
Install
bash
npm install -g dimcodeOther package managers:
bash
# pnpm
pnpm add -g dimcode
# yarn
yarn global add dimcode
# bun
bun add -g dimcodeRun
bash
dim
# or: npx dimcodeVerify
bash
dim --version
dimFirst-time setup (recommended)
DimCode can be configured entirely inside the TUI:
- Open the command palette:
Ctrl+P - Choose Connect Provider (or type
/connect) - Set API key / base URL
- Choose a model:
/models - Set tool approvals:
/approvals(autoorall)
Tip: For local providers like Ollama or LM Studio, you usually don't need an API key, but you do need to add model IDs (or fetch them) in the Connect Provider flow.
Then run:
bash
dimFor where settings are stored and how paths are resolved, see: /config.
Useful in-app commands
Command palette
Press Ctrl+P for quick access to:
- Sessions (switch/list/create)
- Settings / Connect Provider
- Models
- Tool Approvals
- Tool Settings (web search)
- MCP Settings
Slash commands
Type these directly in the input box:
/connect- connect a provider (API key / base URL)/models- pick a model/approvals- approvals mode (autoorall)/sessions- list sessions/new- new session/rename <title>- rename current session/timeline(or/tl) - jump to a user message/tool-settings- configure tools like WebSearch/mcp-settings- configure MCP servers/language- switch UI language/theme- toggle light/dark theme
Troubleshooting
No API key / unauthorized
- Use
/connect(recommended), or setOPENAI_API_KEYin your environment.
Terminal rendering issues
Try:
bash
dim --no-alt-screen --no-mouseDebug logs
bash
dim --debug
# writes: ./dimcode-debug.log (override via DIMCODE_DEBUG_LOG=/path/to/file)