One gateway for Codex and your editor
Understand the connection settings for Codex CLI, OpenCode, Cursor, Cline, and Kilo Code.
Codex uses a custom provider
The Codex setup guide generates a user-level TOML configuration with ModelMesh as the provider, the selected model ID, the gateway base URL, and Responses as the wire API. Put the top-level model settings above the first table. The environment holds your key; the configuration references its variable name.
OpenCode has its own provider configuration
Connect a credential under the modelmesh provider ID, then merge the generated provider into the configuration. Select the same exact catalog model. The guide currently shows the OpenCode v1 schema; use the official documentation for your installed release if its configuration schema differs.
Editor integrations use provider settings
Cline and Kilo Code offer an OpenAI Compatible provider with fields for the base URL, key, and model. Cursor's custom endpoint settings depend on its version and organization policies. Custom keys apply to supported chat features; they do not replace the editor's built-in tab completion.
Check capabilities as well as connectivity
A text response is a useful first check, but a coding assistant also relies on structured tool calls. Test a small task before giving a tool a large project. Unsupported model capabilities, key restrictions, and account limits can all cause failures even when the URL is correct.