Skip to main content
Connect Gecko to Codex using an API key. Create the key first under Settings > API Keys.
1

Export your API key

2

Add the server

For Codex Cloud, set GECKO_API_KEY in the environment’s secrets. The server is stateless, so ephemeral sandboxes reconnect with no session state.
Ask Codex to list your Gecko repositories to confirm the connection.
See the overview for available tools and how access is scoped.

​
Troubleshooting

Confirm GECKO_API_KEY is set in the environment Codex actually runs in (shell profiles don’t reach Codex Cloud; use the environment’s secrets), and that the key still exists under Settings > API Keys. Keys are revoked the moment they’re deleted.
An API key can do exactly what its owner’s role allows, no more. If the key owner’s role lacks triage or ticket permissions, those tools return permission errors while reads keep working. See Teams & permissions.