Architecture described

  • CLI Proxy API signs into Claude and Codex accounts, maintains their authentication, and exposes an endpoint used by the coding clients. This centralizes access instead of repeatedly switching local credentials. 12:41 13:05 15:11
  • Theo places the proxy on a home machine and connects remote machines through Tailscale. His example routes five Claude accounts and four Codex accounts through one residential connection. 22:12 24:22
  • He attributes authentication trouble to cloud IPs, VPNs, and simultaneous access from different locations. He also explicitly warns this arrangement might violate terms or lead to bans; residential routing is not established as a guarantee. 13:32 14:07 14:41
  • His proxy endpoint has no API key because access is restricted to his tailnet. The network restriction is essential context for that choice. 22:12 22:38
  • The demonstrated dashboard is his heavily modified fork, originally derived from Vibe Proxy. A fresh upstream installation will not look like his screen. 17:40 18:04

Reusable machine setup

  • A fleet-management repository records machines, proxy and Tailscale setup, and desired tools including rg, fd, jq, tmux, btop, Node, Python, build tools, Claude Code, and Codex. 23:05 23:37
  • His provisioning loop is to enable SSH, give an agent the machine details and repository instructions, then approve Tailscale enrollment when it appears. 23:59 24:22
  • He says client configuration requires changing endpoint settings, but does not supply exact variables or a complete installation procedure. Separate client home directories can preserve both normal authentication and proxy-configured instances. 24:50 25:09 25:39
  • He specifically warns against using a Claude subscription through clients other than Claude Code. Cross-client model access through the proxy does not, in his account, remove that restriction. 25:39 25:53