TOML
Codex configuration
~/.codex/config.tomlRead one continuous config, with model, access, permissions and tools marked inside the code. Select a setting to see its explanation beside it.
CONFIG FILES & API SETUP
Codex, Claude Code & Hermes Setup: Config & API Keys
Find the right config file, connect your API provider and choose a model. Follow settings examples for Codex, Claude Code, Hermes, OpenClaw, Pi and DeepSeek Harness, with each parameter explained beside the code.
Choose your agent.
Open its config guide or go straight to third-party setup.
JSON
Claude Code configuration
.claude/settings.local.jsonRead one continuous config, with model, access, permissions and tools marked inside the code. Select a setting to see its explanation beside it.
JSON
OpenClaw configuration
~/.openclaw/openclaw.jsonRead one OpenClaw config with model access, third-party gateways, reasoning, tools, heartbeat, MCP and channel settings explained beside the selected line.
YAML
Hermes configuration
~/.hermes/config.yamlRead Hermes' YAML settings for providers, reasoning, terminal tools, compression, memory and MCP. Explanations stay beside the selected setting.
JSON
Pi configuration
~/.pi/agent/settings.jsonRead Pi settings, third-party models, sampling controls and MCP in one continuous window. Select a setting for its explanation.
YAML
DeepSeek Harness (DSH) configuration
$DSH_HOME/profiles/web/cordis.patch.ymlRead DSH's real YAML provider patches, reasoning and output limits, third-party models, compaction, permissions and MCP. Select a setting to see its explanation.
FROM EXAMPLE TO YOUR SETUP
How to use a config guide
- Find the right file. Check the agent, installed version and file path. Personal defaults, project settings and provider catalogs can have different locations.
- Select a setting. Read what it does, when to change it and how to check the result. Explanations follow the line you select.
- Copy and merge. Copy a single setting, the active config or a complete third-party example. Replace placeholders and keep credentials in the location your agent supports.
COMMON CONFIG QUESTIONS
Before you change a parameter
Can I use the same config for every agent?
Each agent has its own schema and file locations. A gateway URL, model ID or API key reference may use different field names. Follow the example for your agent, including any separate-file or plugin scope.
Where do I set temperature?
Support depends on the agent, provider and model. Each handbook includes a temperature note and shows its configuration location when supported. Reasoning effort and response limits are separate controls.
Does copying an example connect my provider?
You still need the provider's endpoint, exact model ID and credentials. The examples explain the setup; they do not create an account or establish a live connection.