← ClaudeAtlas

add-connectorlisted

Onboard a `deus connect` connector — a way to route Claude Code sessions to non-Claude models (e.g. GPT via CLIProxyAPI) alongside normal Claude access. Generic orchestrator over whichever connector is selected.
sliamh11/Deus · ★ 51 · AI & Automation · score 79
Install: claude install-skill sliamh11/Deus
# Add a `deus connect` Connector `deus connect` launches the real, unmodified `claude` binary with which upstream model answers its requests redirected via `ANTHROPIC_BASE_URL` — identity, vault/memory context, preferences, and portable skills stay intact, exactly like a normal `deus`/`deus home` session. This is separate from Deus's own container-agent backend adapters (`deus codex`, `DEUS_AGENT_BACKEND`) — see `docs/decisions/backend-neutral-agent-runtime.md`'s note near the Parity Matrix. This skill is generic over any registered connector (ships with `cliproxy-oauth` and `ollama`) — adding another connector in the future changes `connectors/providers/`, not this skill. **Four distinct "ollama" surfaces exist in this repo — do not conflate them when guiding a user:** 1. **`deus connect ollama`** (this skill, this section) — routes a Claude Code session directly to a local Ollama instance via its native Anthropic-API mode. No proxy, no daemon management. 2. **`deus provider ollama` / `deus fcc`** (`deus-cmd.sh`'s `fcc` proxy system) — a *different* mechanism: routes through `fcc-server`'s OpenAI-compat translation proxy. Also reaches a local Ollama install, but via proxy translation, not a direct native-mode redirect. 3. **`deus backend set ollama`** — a persisted `DEUS_AGENT_BACKEND` value. Not yet wired to a working CLI agent; its stub error message points here (`deus connect ollama`) and to `deus provider ollama`/`fcc`. 4. **`.claude/skills/add-ol