Synopsis
Description
config manages two layers of configuration:
- CLI config - stored locally in
~/.profclaw/config.json. Controls how the CLI connects to the server (API URL and token, default agent, output format). - Server settings - stored in
config/settings.ymland the database. Controls runtime behavior of the running server (use--serverflag).
Subcommands
| Subcommand | Description |
|---|---|
get [key] | Print one or all configuration values |
set <key> <value> | Set a configuration value |
reset | Reset configuration to defaults |
path | Print the path to the CLI config file |
login | Configure API authentication (URL and token) |
config get
Optional key to retrieve. Omit to print all values. For server settings, use dotted format:
system.telemetry.Output as JSON.
Fetch server-side settings from the running API instead of the local CLI config.
config set
Configuration key to set. CLI keys:
apiUrl, apiToken, defaultAgent, outputFormat. Server keys use category.key format (e.g., system.telemetry).Value to set. For server settings, JSON values are parsed automatically (
true, false, numbers, objects).Apply change to server-side settings via API.
config login
API bearer token. Saved to the CLI config file and used for all subsequent API calls.
API base URL (e.g.,
https://my-server.example.com).CLI Config Keys
| Key | Default | Description |
|---|---|---|
apiUrl | http://localhost:3000 | Base URL of the profClaw API |
apiToken | - | Bearer token for authentication |
defaultAgent | - | Default agent type for task creation |
outputFormat | table | Output format (table or json) |
Examples
Related
profclaw auth- User and invite managementprofclaw onboard- First-run configuration wizard- Configuration Reference - Full settings documentation