Pimp My IDE / Garage Dispatch
Back to garage
September 25, 2026 | continuity / Codex / local routes

Your login is not your workshop.

A Codex outage briefly left API-key login as the documented bypass. The useful lesson is bigger than one incident. Keep identity, code, handoff state, and inference on separate switches.

The take. An alternate credential is one bypass, not a continuity plan. Keep the repository local, prepare a separately billed API-key route, save a plain-text handoff, and test one hardware-fit local model before the next login gate sticks.
Wire the Identity Bypass Switch

The outage named the boundary.

OpenAI marked a Codex outage at 22:58 UTC on September 25. Twenty minutes later, its status page said API-key login would unblock access. OpenAI marked all affected services recovered at 23:54 UTC.[1] The incident lasted 55 minutes and 53 seconds. It was an identity-route failure with a documented alternate path, not proof that every Codex surface or every model provider failed.

The Hacker News item preserved the incident URL and discussion ID while the event was active.[2] That trail matters because status headlines age fast. The final incident record now says resolved.

An API key changes the bill and the rules.

OpenAI's Codex authentication docs describe two local sign-in methods: ChatGPT and API key. The docs say API-key use follows the API organization's data settings and standard API pricing. Some workspace and cloud-dependent capabilities are limited or unavailable.[3]

A bypass that changes billing, policy, and available capabilities needs its own test card.

Do not discover that difference during an outage. Confirm the account, spend cap, allowed models, credential storage, and minimum task while the main route still works. Never paste the key into a repository, issue, or handoff note.

Local compatibility is a limp-home lane.

Ollama documents a local server that accepts a subset of the OpenAI API at http://localhost:11434/v1/. Its page includes chat-completions and Responses examples, and it lists unsupported cloud features.[4] A compatible endpoint can reduce adapter work. It does not make a small local model equivalent to a hosted coding agent.

Choose one bounded fallback job. Good candidates include summarizing a local diff, drafting a commit message, explaining a test failure, or extracting a checklist. Record the model, memory fit, latency, missing tools, and output limits. That is a continuity route. Pretending feature parity is not.

Run the drill while everything is green.

  1. Freeze or stash the work so the repository remains the durable state.
  2. Write a handoff with the goal, changed files, last command, result, and next safe action.
  3. Test API-key login on a low-risk task and record the separate billing route.
  4. Test one local model on the same bounded task, then record where it falls short.

The drill is complete only after somebody runs both alternate routes and records the result. The switch below prepares that drill card. It does not test credentials, models, or recovery.

Interactive makeover / physical continuity bus

Identity Bypass Switch

Traditional purpose replaced: watch a status page and wait. Better version: isolate four dependency switches, see which routes reach the ignition bus, and copy a drill card that names the evidence still missing.

Close the bypass circuits

Each switch records a requirement selected for the drill. It does not record a passing test.

Continuity drill requirements

Trace the continuity bus

Requirements selected0 / 4
Four requirements remain open.

Select the repository, authentication, handoff, and local-model requirements before printing the drill card.

Print the outage drill

The card names what to test and keeps evidence fields blank. Fill those fields only after running each route.

Sources read, not vibes

Open the source log
  1. OpenAI status incident 01M3DCNWMW57HYK8FJ5FBFPA39. Incident start, API-key bypass notice, mitigation, and resolved timestamp.
  2. Hacker News item 49851169. Discovery trail and the exact incident URL. Comments are reaction, not incident evidence.
  3. OpenAI Codex authentication docs. ChatGPT and API-key sign-in paths, billing and policy differences, local-client scope, and feature limits.
  4. Ollama OpenAI compatibility docs. Local endpoint, compatible request examples, and unsupported-feature boundaries.

Source boundary. OpenAI's status record supports the incident timeline and temporary API-key advice. OpenAI documents its own authentication behavior. Ollama documents its own compatibility layer. The four-switch drill and continuity advice are Pimp My IDE's operating method.