Your chosen agent connected to a local model in one command
Use Ollama on your hardware platform to run a local coding model and connect a CLI coding agent. This playbook supports three options: Claude Code, OpenCode, and Codex CLI. Each agent is wired up with Ollama's built-in launch method (ollama launch <agent>), so you can work without environment variables, provider config files, or external cloud APIs.
Pick the tab that matches the CLI agent you want to use:
You'll run a local coding model (Qwen3.6) on your hardware platform with Ollama, launch your chosen CLI agent against it with a single command, and complete a small coding task end-to-end.
Required:
Optional:
Use the matrix below to confirm your hardware platform, recommended default local settings, and whether multi-node applies.
| Hardware platform | OS | Memory | Recommended default local settings | Multi-node capable hardware |
|---|---|---|---|---|
| DGX Spark | DGX OS (Linux) | 128 GB Unified Memory | Ollama + qwen3.6:35b-a3b-mtp-q4_K_M (~23 GB); Claude Code / OpenCode / Codex via ollama launch | — |
Hardware requirements
q8_0; about 71 GB for bf16)Software requirements
ollama launch and the default MTP Q4_K_M model): ollama --version@openai/codexvenv support for the optional coding-task verificationBrowse models you can pull and run with Ollama in the Ollama library. Use the tags and sizes that fit your hardware platform’s memory and storage.
| Hardware platform | More recipes |
|---|---|
| DGX Spark | Ollama library · Qwen3.6 |
Use the Claude Code, OpenCode, or Codex CLI tab for the base workflow.
ollama launch and the default MTP Q4_K_M model tag — verify with ollama --version and install from ollama.com/download if needed~/.ollama/models (see Cleanup in each agent tab). Cleanup is optional and removes downloaded model files.ollama launch on supported hardware platforms