Overview
Type: Coding ToolPrimary Path: OpenAI ResponsesSupport Confidence: Supported with model/channel limits
/v1/responses. That path works well, but some Responses-native features still depend on whether the selected model and routed channel support native passthrough.
System Requirements
- OS: macOS, Linux (official support), Windows via WSL
- Node.js: Version 18+
- npm: Version 10.x.x or higher
Installation
Configuration
Step 1: Set API Key
Temporary (current session):~/.bashrc, ~/.zshrc, or ~/.bash_profile:
Step 2: Configure config.toml
Edit~/.codex/config.toml:
If the config file doesn’t exist, run
codex once to generate it, then edit the file. Restart Codex completely after changing config.toml so the new provider settings are reloaded.If a request uses Responses-native-only fields that your chosen model or routed channel does not support, LemonData returns an explicit error instead of silently downgrading the request.
Basic Usage
Start interactive mode:Recommended Models
| Model | Best For |
|---|---|
gpt-5.4 | Best default choice for coding and reasoning |
gpt-5-mini | Faster, cheaper fallback for coding workflows |
claude-sonnet-4-6 | Code review, documentation |
deepseek-r1 | Algorithm design, reasoning |
Interactive Commands
| Command | Description |
|---|---|
/help | Display help |
/exit or Ctrl+C | Exit |
/clear | Clear conversation |
/config | View configuration |
/model <name> | Switch model |
/tokens | View token usage |
Verify Configuration
Common Use Cases
Code review:Troubleshooting
Connection Error
Connection Error
- Verify
base_urlin config.toml is exactlyhttps://api.lemondata.cc/v1 - Check network connectivity
- Ensure no proxy interference
Authentication Failed
Authentication Failed
- Verify
env_key = "OPENAI_API_KEY"is present in~/.codex/config.toml - Verify
OPENAI_API_KEYenvironment variable is set - Check that the key starts with
sk- - Ensure the key is active in LemonData dashboard
Model Not Found
Model Not Found
- Check model name matches exactly
- Verify model availability at lemondata.cc/en/models
Responses-native field rejected
Responses-native field rejected
- Some fields are only available when the selected model and routed channel support native
/v1/responsespassthrough - If you see an error mentioning
unsupported_request_fieldor native passthrough, remove the field or switch to a compatible model/channel