How dragoncraftgg/claude-code-vpn-launcher works
This Windows launcher intercepts the global claude command, collects VPN settings when needed, and offers direct or local-proxy launch modes. The main runtime path runs through the launcher and its VPN manager; the wrappers then hand off to native Claude Code, with proxy variables applied only in proxy mode. The README also documents importing Claude API settings and restoring wrappers on uninstall. The wrapper implementations and install/uninstall scripts were not sampled, so those relationships are based on README statements.
Main entry points: claude.ps1 PowerShell Wrapper · launcher.js Interactive Launcher · claude.cmd claude Command · vpn-manager.js VPN Manager
Components 9
Command and Menu
- claude Command
files/claude.cmd - PowerShell Wrapper
files/claude.ps1 - Interactive Launcher
files/launcher.js
VPN Proxy
- VPN Settings
files/vpn-manager.js - VPN Manager
files/vpn-manager.js - sing-box Proxy
Claude Handoff
- Native Claude Code
- Claude API Settings
Other components
- User
Connections 9
- User → claude Command: runs
README.md - claude Command → PowerShell Wrapper: dispatches
README.md - PowerShell Wrapper → Interactive Launcher: starts
README.md - Interactive Launcher → VPN Settings: reads / writes
files/launcher.js - Interactive Launcher → VPN Manager: starts / stops
files/launcher.js - VPN Manager → sing-box Proxy: starts / stops
files/vpn-manager.js - PowerShell Wrapper → Claude API Settings: imports env
README.md - PowerShell Wrapper → Native Claude Code: launches
README.md - sing-box Proxy → Native Claude Code: proxies traffic
README.md