Configuration
Configuration
Clash Verge CLI has zero config files. Everything is hardcoded in two constants:
constants.js
const CLASH_VERGE_PATH = '/Applications/Clash Verge.app';
const ADMIN_HELPER_PATH = '/Library/PrivilegedHelperTools/org.clashverge.helper';| Constant | Default | When to change |
|---|---|---|
CLASH_VERGE_PATH |
/Applications/Clash Verge.app |
If you installed Clash Verge elsewhere (homebrew, ~/Applications, custom directory) |
ADMIN_HELPER_PATH |
/Library/PrivilegedHelperTools/... |
If the helper daemon is at a non-standard path (rare — only if you manually moved it) |
Custom path example
// If your Clash Verge is in ~/Applications:
const CLASH_VERGE_PATH = '/Users/yourname/Applications/Clash Verge.app';Edit constants.js, save, and run node index.js. No rebuild needed.
Environment variables (passed to Clash Verge)
The CLI sets these env vars before spawning:
CLASH_VERGE_TUN=1— enables TUN modeHOME— inherited from your shellPATH— inherited from your shell
Proxy config
This tool does NOT manage your proxy rules, subscription links, or routing — those are configured inside Clash Verge's GUI once it launches. The CLI only handles the "start with TUN permissions" part.