Self-host a VPS with Hysteria2 and smart routing for a stable AI workflow

sujingshen · x · 2026-08-19

An AI-heavy product person shares a full tutorial on building a personal network exit. The motivation: repeated Claude/Codex failures weren't the model's fault but a dirty shared exit, while global proxying makes local sites (Taobao, WeChat, home NAS) slow.

Core idea: AI-first, not Proxy-first — rent a VPS, run Hysteria2, and use Surge/Clash with routing rules so AI and dev services (Claude, Codex, GitHub) tunnel on demand while domestic traffic stays direct.

Three wins from self-hosting: controlled exit (you know who uses it), controlled policy (per-service rules), and controlled infrastructure (configs, certs, backups in your hands) — though it's not guaranteed faster. The guide walks through buying a VPS, installing Hysteria2, and writing routing rules with a ready-to-edit template.

Original post →

More from coding & agent

coding & agent channel →