Coding tools setup for OpenAI-compatible clients and agent workflows.
Use the shortest path: test the API first, then choose either the OpenAI-compatible route or the Anthropic-style route depending on the tool.
Standard values
OpenAI-compatible
Anthropic-style
/v1 manually.Codex
Recommended: use the one-click script. It writes the local config after asking for your API key.
Manual values
Claude Code
Recommended: use the one-click script, then restart the CLI after the environment snippet is generated.
Manual values
Gemini CLI
Recommended: use the one-click script. If your build supports custom providers, use the OpenAI-compatible route.
Manual values
OpenClaw
Use MonkeyAI with OpenClaw. The easiest path is the one-click script: choose Anthropic (Claude) or OpenAI (Codex) when prompted, then paste your API key.
Anthropic (Claude)
/v1 for Claude / Anthropic-native access. Example model: claude-sonnet-4-20250514-20250514.OpenAI (Codex)
/v1. Example model: gpt-4o.Recommended: interactive one-click script
Hermes
Use MonkeyAI with Hermes. The recommended path is the one-click script, which lets you choose the provider route and writes ~/.hermes/config.yaml.
Recommended: interactive one-click script
OpenAI-compatible
Anthropic-style
Cursor / Cline / Continue
Cursor / Cline
Continue
Common pitfalls
- OpenAI-compatible tools usually need
/v1; Anthropic-native tools usually do not. - Use one API key per tool if possible.
- Test one short request before long coding sessions.
- Keep your API key out of public repositories.