← ClaudeAtlas

add-codexlisted

Add OpenAI/Codex as a backend. Guides through API key setup, service backend configuration, optional CLI setup, and verification. Can run alongside Claude (default) or replace it.
sliamh11/Deus · ★ 38 · AI & Automation · score 80
Install: claude install-skill sliamh11/Deus
# Add OpenAI/Codex Backend This skill configures OpenAI/Codex as a backend for Deus. Two independent modes: - **Service backend** (`DEUS_AGENT_BACKEND=openai`) — container agents use the OpenAI Responses API for background message handling - **CLI sessions** (`deus codex`) — foreground interactive sessions using the `codex` CLI binary You can enable one or both. The Claude backend remains the default until explicitly switched. **IMPORTANT:** This skill writes environment variables to `.env` and syncs them to `data/env/env` at runtime. It does not modify source code or require a rebuild. ## Phase 1: Pre-flight ### Check if already configured Check if OpenAI/Codex is already set up: ```bash grep -q 'OPENAI_API_KEY=.' .env 2>/dev/null && echo "API key found" || echo "No API key" deus backend ``` If both show valid config, skip to Phase 5 (Verify). ### Ask scope AskUserQuestion: How do you want to use OpenAI/Codex? 1. **Service backend** — container agents use OpenAI for message handling (replaces Claude as default backend) 2. **CLI only** — use `deus codex` for interactive sessions (Claude stays as service backend) 3. **Both** — service backend + CLI sessions > **Recovery:** If you're unsure, start with CLI only (option 2). You can switch the service backend later with `deus backend set codex`. ## Phase 2: API Key ### Check for existing key ```bash grep 'OPENAI_API_KEY' .env 2>/dev/null ``` If a key is already set and valid, skip to Phase 3. ### Collect the API