Deploy Codex CLI with Bedrock Through agentgateway A walkthrough published on GitHub by sebbycorp shows how to run OpenAI's Codex CLI against an OpenAI model on Amazon Bedrock with no API key on the laptop, using open source agentgateway v1.7.0 in a local kind cluster. The gateway accepts Codex's OpenAI Responses API calls on localhost, rewrites the model name gpt-oss-120b to Bedrock's openai.gpt-oss-120b-1:0, returns 404 for any other model name, and logs each request's token count and cost to a Postgres database for the agentgateway UI. The setup installs Gateway API v1.6.3 CRDs plus agentgateway-crds and agentgateway Helm charts at v1.7.0, and also exposes an MCP endpoint at /mcp backed by search.solo.io/mcp. Codex CLI wants an OpenAI-shaped endpoint and an API key. I wanted neither on my laptop. The goal for this build: Codex talks to a gateway on localhost with no key at all , the gateway sends the request to an OpenAI model running on Amazon Bedrock , and every call shows up in a log with its token count and cost. All of it runs on open source agentgateway https://agentgateway.dev v1.7.0 in a local kind cluster. The manifests and the full step list are in sebbycorp/agentgateway-oss-k8s https://github.com/sebbycorp/agentgateway-oss-k8s . What you end up with: gpt-oss-120b . The gateway rewrites that to Bedrock’s openai.gpt-oss-120b-1:0 . Any other model name gets a 404. /mcp . php flowchart LR C Codex CLI