Config file

The CLI persists a single JSON config file. Schema:


{
  "endpoint": "https://api.prxy.monster",
  "token":    "prxy_xxx",
  "user": {
    "id":    "u_xxx",
    "email": "you@example.com"
  }
}

Only endpoint is required at read time. token and user are populated by prxy login.

Location

Platform	Default path
macOS / Linux	`~/.prxy/config.json`
Windows	`%APPDATA%\prxy\config.json`

Override with PRXY_CONFIG_DIR=/path/to/dir.

Permissions

On Unix, the file is written with mode 0600 (owner read/write only) and the directory with 0700. Writes are atomic — the CLI writes to a .tmp sibling and renames into place, so a crash mid-write can’t leave you with a half-written config.

On Windows, the default ACL on %APPDATA%\<app>\ is already user-only, so no explicit chmod is needed.

Hand-editing

Editing the file by hand is supported — prxy doctor will tell you if anything’s wrong. Common cases:


# Switch to staging
$EDITOR ~/.prxy/config.json
# Change "endpoint" to "https://api.staging.prxy.monster"
 
# Or use the env var override (no edit needed):
PRXY_CONFIG_DIR=~/.prxy/staging prxy doctor

Wipe


prxy logout       # removes the file entirely
rm -rf ~/.prxy    # nuke everything if logout misbehaves

Environment variable overrides

Variable	Purpose
`PRXY_CONFIG_DIR`	Override config directory.
`PRXY_REGISTRY_URL`	Override the registry index URL for `prxy modules`.
`NO_COLOR`	Disable colored output (https://no-color.org ).

The endpoint can also be overridden per-command with --endpoint=... on prxy login. Once saved, the endpoint sticks until the next login.