#Integration Troubleshooting

#The tool still uses the old provider

• Restart the tool.
• Check whether it reads a different profile or configuration file.
• Confirm environment variables are available to GUI apps and background services, not only your interactive shell.
• In CC Switch, confirm the provider is active for the correct target app.

#Model list is empty

Many tools can still use a manually entered model ID. Copy one from Models. An empty list does not prove that Chat Completions or Responses is unavailable.

#Chat works but Codex fails

Chat clients usually use /v1/chat/completions; Codex uses /v1/responses. Choose a Responses-capable model and set wire_api = "responses" in the Codex provider.

#Chat works but tool calling fails

Verify all three layers:

1. the model supports tool calling;
2. GetRouter exposes that capability through the selected protocol;
3. the tool understands the returned tool-call events.

#URL/path is duplicated

Examples of incorrect requests:

/v1/v1/chat/completions
/v1/responses/responses
/v1/chat/completions/chat/completions

Use the integration guide for that tool and remove the duplicated segment.

#Configuration changes do not take effect

• Validate JSON or TOML syntax.
• Preserve the tool's required nesting.
• Restart the process.
• Check for project-local settings that override user settings.
• Confirm CC Switch or another manager did not rewrite the file.

#Safe escalation

Include versions, protocol, model ID, Request ID, timestamp, and redacted configuration. Replace keys with YOUR_API_KEY before sharing.