tokens.toml.
Tokens authenticate clients to the local proxy for configured route-host traffic. Full route matches still decide whether credentials are injected. Token values are never printed by cordon token; use cordon env for generic clients.
The default token is the general-purpose proxy credential for a Cordon instance. Client tokens are named proxy credentials managed for configured clients such as Claude Code, Codex, Hermes, and OpenClaw. In the current token model, all valid tokens grant the same proxy access; client tokens exist for independent rotation, revocation, setup/remove cleanup, and logging. Workload identity is verified separately.
When enforcement is active, unmatched forwarding still works without a token. If a request does include Proxy-Authorization, Cordon rejects malformed, duplicate, or invalid values before forwarding.
Usage
For Hermes and OpenClaw client tokens, omit
--scope to use the integration’s default config path (or a legacy user-scope config during migration), or pass --config explicitly. --scope project is rejected for these global app integrations because it would otherwise target the caller’s current directory.
Commands
cordon token list
List configured token names and creation times without printing token values.
cordon token rotate
Rotate one token or every configured token. Omitting the token name rotates the default token.
claude-code, codex, hermes, or openclaw), rotation updates that client’s tokenized proxy URL before writing the new token file. Restart any running client process that already inherited the old URL.
cordon token revoke
Revoke a client token.
tokens.toml.
Token storage
On Unix, Cordon writes
tokens.toml with 0600 permissions and refuses symlinked, wrong-owner, or group/world-readable token files.