Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.codezero.io/llms.txt

Use this file to discover all available pages before exploring further.

Manage integrations independently of the base setup. Enable wires an integration to use cordon (running base setup if needed); disable removes only integration-specific settings.

cordon integration enable

Enable an integration. Runs the base setup if needed, then configures that integration’s proxy settings.
cordon integration enable <claude-code|codex|hermes> [OPTIONS]
Flags go after the integration name, for example cordon integration enable codex --scope user.
Argument / OptionDescription
<integration>claude-code, codex, or hermes
--scopeConfiguration scope (see defaults below; Hermes supports user scope only)
--config, -cPath to cordon.toml (default: ./cordon.toml)
--yesSkip confirmation prompts
--trustAdd CA to system trust store
--no-trustSkip trust store prompt
--regenerate-caRegenerate the CA certificate
--serviceInstall cordon as a background service
--no-serviceSkip the service install prompt

Default scopes

Each integration has a default scope that matches its typical usage pattern:
IntegrationDefault scope
claude-codeproject
codexproject
hermesuser
Override with --scope:
# Use user scope for claude-code instead of the default project scope
cordon integration enable claude-code --scope user
Hermes operates across projects and only supports user scope. cordon integration enable hermes --scope project is rejected.

Examples

# Enable Claude Code integration (project scope)
cordon integration enable claude-code

# Enable Codex integration with trust and service install
cordon integration enable codex --trust --service

# Enable Hermes integration (defaults to user scope)
cordon integration enable hermes

cordon integration disable

Disable an integration. Removes only the settings that the integration wrote — keeps the CA files and cordon.toml so you can re-enable without rotating certificates.
cordon integration disable <claude-code|codex|hermes> [OPTIONS]
Flags go after the integration name, for example cordon integration disable claude-code --yes.
Argument / OptionDescription
<integration>claude-code, codex, or hermes
--scopeConfiguration scope (same defaults as enable; Hermes supports user scope only)
--config, -cPath to cordon.toml
--yesSkip confirmation prompts
--trustAlso remove the CA from the system trust store

Examples

# Disable Claude Code integration
cordon integration disable claude-code

# Disable and remove CA from trust store
cordon integration disable codex --trust

# Disable Hermes integration (defaults to user scope)
cordon integration disable hermes

# Skip confirmation
cordon integration disable claude-code --yes
Disabling an integration is safe — it only removes integration-specific wiring. The CA certificate, key, and cordon.toml are retained so you can re-enable with cordon integration enable without regenerating anything.

What each command touches

CommandCreates / modifiesRemoves
cordon setupCA cert + key, cordon.toml
cordon setup claude-codeCA cert + key, cordon.toml, Claude Code settings.json env vars
cordon integration enable claude-codeSame as cordon setup claude-code
cordon integration disable claude-codeClaude Code settings.json env vars
cordon integration disable claude-code --trustClaude Code settings.json env vars + CA from system trust store
cordon setup codexCA cert + key, cordon.toml, Codex .env and config.toml (project .codex/ by default, $CODEX_HOME/~/.codex for user scope)
cordon integration enable codexSame as cordon setup codex
cordon integration disable codexCodex .env env vars
cordon setup hermesCA cert + key, cordon.toml, combined CA bundle, Hermes ~/.hermes/.env env vars
cordon integration enable hermesSame as cordon setup hermes
cordon integration disable hermesHermes .env env vars + combined CA bundle
cordon trustAdds CA to system trust store
cordon untrustCA from system trust store
cordon service uninstall NAMElaunchd plist / systemd unit
cordon setup --regenerate-caReplaces existing CA cert + keyOld cert + key
If you run --regenerate-ca and the old CA was already trusted, rerun cordon trust after setup. Regeneration replaces the certificate files, but it does not automatically update the system trust store to trust the new CA.