0xkaka/homeport
Networking & CommunicationRoute Claude, Google and Stripe through one fixed residential IP on every device while other traffic keeps using your usual proxy node.
What it does
homeport is a set of proxy routing rules and configuration snippets, not a standalone app. It makes selected "sensitive" sites — Claude/Anthropic, Google, Stripe, hCaptcha, and a few risk-control and analytics domains — exit through one static residential proxy with a fixed IP, while all other traffic keeps using the user's existing airport (proxy subscription) node. The point is IP consistency: rotating datacenter nodes often trigger verification, payment failures, or account blocks.
The mechanism is a relay chain: traffic for the listed domains goes through the currently selected airport node (the "jump board") and then to the residential proxy, which websites see as the final IP. Switching airport nodes does not change that final IP, and the same residential credentials on every device keep the IP identical across devices. The rules also block Anthropic's IPv6 ranges so clients fall back to IPv4.
Quick start
- Prepare a working airport subscription and a static residential HTTP or SOCKS5 proxy with username/password. Note the proxy host (Proxy Address, not the assigned exit IP), port, username and password.
- Open the one-click config page, choose your device and client, fill in the four proxy values, and copy the generated config. The page says credentials are processed only in the browser.
- Paste into the matching client: Clash Party or Clash Verge Rev use an override/extension script, FlClash imports the script by URL and then edits the
HOMEblock, and Shadowrocket installs the module and adds a node named exactly🏠住宅出口-勿选. - Select the override on the airport subscription, restart the core, set mode to Rule (Clash) or Config (Shadowrocket), and enable system proxy; enable TUN if desktop apps such as Claude Code should also be covered.
- Verify by opening
https://ipv4.webshare.io/; the IP should equal the residential proxy exit IP on every device. On desktop,curl -x http://127.0.0.1:7890 https://ipv4.webshare.io/(Clash Verge Rev defaults to port 7897) confirms the same.
Client support and links are documented per platform in the client preparation section.
Constraints
- The rules only make sense with an existing airport node as relay plus a purchased static residential proxy; the project does not supply either.
- v2rayN cannot express this split routing; the README recommends switching to Clash Verge Rev.
- FlClash must be version 0.8.85 or newer; Shadowrocket is a paid app from the US App Store, with the Mac version limited to Apple Silicon.
- Terminal programs and Claude Code do not automatically use the system proxy; you need TUN mode or explicit
http_proxy/https_proxyenvironment variables. Chrome needs QUIC disabled to avoid bypassing the proxy. - Ports differ by client (Clash Party 7890, Clash Verge Rev 7897), and Shadowrocket module updates do not carry credentials, which live in the node.
- The repository declares no license.
Maintaining the rules
Domain lists live in two places that must stay in sync: the SUFFIX array in flclash/homeport.js and the [Rule] section of shadowrocket/homeport.module, plus the GROUPS rules in the one-click page's index.html. A self-check script python3 scripts/check.py validates relay selection and rule consistency, and GitHub Actions runs it on push.
HotRepo's take
homeport appeared on HotRepo's new-project list on 2026-11-19 with 254 stars and 133 net new stars over the roughly 24-hour window ending that day, alongside 19 new forks. The hourly star samples show a small, steady climb through 2026-11-18 and a sharp jump in the final hours (from 146 to 254 between 11:46 and 15:46 UTC), which is a burst pattern rather than a long record. No GitHub daily rank or HN discussion was recorded, so there is no basis to comment on broader traction. What stands out technically is the narrow scope: it solves one specific IP-consistency problem for a handful of services and openly depends on the user already having both a subscription and a residential proxy.
Written by AI from the project's README, updated . The project's own docs are the source of truth.