Choose your OS
- macOS: Use Terminal or iTerm and store tool configs under
~/.tool-name/ - Linux: Use your normal shell and the same
~/.tool-name/config layout - Windows: Use PowerShell and store tool configs under
%USERPROFILE%\.tool-name\ - WSL: Follow the Linux examples inside your WSL environment
Reuse these values everywhere
macOS and Linux
Windows PowerShell
Basic flow
- Create or copy an
appleai.codesAPI key. - Pick a routed model path such as
anthropic/claude-sonnet-4oropenai/gpt-5. - Open the guide for your tool and paste the shared values into its config.
- Run one simple request to confirm the endpoint and key work together.
Verify the connection first
macOS and Linux
Windows PowerShell
Recommended order
- Start with Claude Code, Codex CLI, or OpenCode. They expose direct config files.
- Move to Cursor, Cline, Continue, or Roo when you want editor integration.
- Use the MITM-only tools flow only when the product does not let you enter a custom base URL.
Pick a guide
Claude Code
Configure Anthropic-compatible environment variables.
Codex CLI
Add an OpenAI-compatible provider block and API key.
OpenCode
Register a provider that points to
appleai.codes.Shared configuration
Review the values and route format each guide expects.