Home / Blog / Run any LLM in t3's Codex and Claude tabs through a local…
Tech News

Run any LLM in t3's Codex and Claude tabs through a local gateway

Points: 1 # Comments: 0 Run any LLM in t3's Codex and Claude tabs through a local gateway Coverage based on HN Claude/Codex/Fable reporting.

By Dillip Chowdary • Sep 03, 2026 • Source: HN Claude/Codex/Fable

Run any LLM in t3's Codex and Claude tabs through a local gateway

What happened

Section 3 Para 2: 81 words Section 4 Para 1: 81 words Section 4 Para 2: 81 words Section 5 Para 1: 81 words Section 5 Para 2: 81 words * Total words: 90 + 810

A GPT model in the Claude tab, GLM or Kimi K3 in the Codex tab, plugged and unplugged on demand. One local gateway (CLIProxyAPI) on 127.0.0.1:8317 speaks the OpenAI, Responses, and Anthropic formats at once and routes each request by model id.

How it works

Run any LLM in t3's Codex and Claude tabs through a local gateway
Illustration · Pexels

Nothing touches t3's database, so unplugging leaves your setup as it was. Setup git clone https://github.com/0xhsn/proxy-llms ~/proxy-llms && ~/proxy-llms/setup.sh It downloads the gateway, turns your existing Codex and Claude logins into gateway credentials, starts it, and routes the Codex tab through it.

Advertisement

Tech Pulse Daily

Get tomorrow's pulse first

Join engineers who read Tech Pulse before stand-up. Free, weekday mornings.

Why it matters

The Claude tab shows only claude- slugs, so give an external model a claude- alias (second line above) to run it there. See the full write-up from HN Claude/Codex/Fable via the source link for quotes and complete context.

Who is affected

Read the original coverage at HN Claude/Codex/Fable via the source link above for the complete details and primary quotes.

What to watch next

Cross-check release notes and official docs before changing production systems based on early reporting.

Developer Action Items

  • ☐ Diff the official changelog for OpenAI / Anthropic / Claude 127.0.0.1 before you bump — APIs, defaults, and removed flags only.
  • ☐ Install through the vendor's documented channel in staging; keep a one-command rollback and time-box the canary.
  • ☐ Grep your repo for old flag names, lockfile pins, and plugin versions that the notes mark as breaking.
  • ☐ Prefer the first patch cut over the day-zero tag unless you have a reason to be on the leading edge.
  • ☐ If HN Claude/Codex/Fable did not name a region, plan, or SKU, screenshot the official availability line before you promise it to users.
Dillip Chowdary

Author

Dillip Chowdary

Writes Tech Bytes coverage of AI, engineering, and the tools that actually ship. Editor of Tech Pulse Daily.

Related on Tech Bytes

Advertisement

5-min tech signal

Weekday briefing for engineers who skip the noise.

No spam · Unsubscribe anytime

Advertisement

✈️ CareerPilot

Your AI job-search copilot

Match your resume against live Ashby, Greenhouse & Lever openings — fit scores, job-specific resume optimization and email alerts.

Find matching jobs →

Free Tools

Browse all tools →