CLI setup
Connect Claude CLI and Codex CLI to Conflux while keeping workspace governance active.
Claude CLI
Set the Anthropic-compatible base URL and use a Conflux workspace API key.
Windows PowerShell:
$env:ANTHROPIC_BASE_URL="https://api.yoiyoi.xyz"
$env:ANTHROPIC_API_KEY="<CONFLUX_API_KEY>"
Remove-Item Env:ANTHROPIC_AUTH_TOKEN -ErrorAction SilentlyContinue
claude --dangerously-skip-permissionsmacOS/Linux:
export ANTHROPIC_BASE_URL="https://api.yoiyoi.xyz"
export ANTHROPIC_API_KEY="<CONFLUX_API_KEY>"
unset ANTHROPIC_AUTH_TOKEN
claude --dangerously-skip-permissionsCodex CLI
Configure Codex to point at Conflux, then set the Conflux API key before running.
Add this provider configuration to your Codex `config.toml`.
model_provider = "yoiyoi"
model_reasoning_effort = "high"
[model_providers.yoiyoi]
name = "yoiyoi"
base_url = "https://api.yoiyoi.xyz/v1"
env_key = "CONFLUX_API_KEY"Windows PowerShell:
$env:CONFLUX_API_KEY="<CONFLUX_API_KEY>"
codexmacOS/Linux:
export CONFLUX_API_KEY="<CONFLUX_API_KEY>"
codexLong-running work
Long-running CLI work can exceed browser or proxy expectations when routed through the wrong hostname. For production CLI/API traffic, use the direct API hostname rather than the web hostname.
CLI-native memory
Claude CLI and Codex CLI may already include their own working context. Conflux preserves that client payload on the first attempt and uses workspace memory as a governed layer around the request, not as a replacement for the CLI's own task context.