01Run it
Replace the <placeholders> with your own values, or use the builder below.
p202 config list-profiles02What you get
Captured from the real binary, run against a demo store with 30 days of traffic. Switch tabs to see the same run as JSON, the shape scripts and agents parse.
$ p202 config list-profiles name active api_key tags url ------- ------ ----------- ---- --------------------- default true 4f1c...9d0e https://track.example.com
$ p202 config list-profiles --json { "active_profile": "default", "data": [ { "active": true, "api_key": "4f1c...9d0e", "name": "default", "tags": "", "url": "https://track.example.com" } ] }
03Build your command
Pick values and the command line writes itself, quoted and ready to paste.
p202 config list-profilesSet flags below; the command updates as you type.
04Flags
1 flag, plus the global flags every command takes.
| Flag | What it does |
|---|---|
| --tagstring | Filter profiles by tag |
05For agents
Running this from an agent
- Read the same facts as JSON:
p202 commands config list-profiles --json. - With
AI_AGENT,CLAUDECODEor another agent variable set, output is compact JSON and errors arrive on stderr as a JSON envelope with ahint. - Exit codes: 0 ok, 1 bad input, 2 auth, 3 network, 4 server error, 5 partial failure.
{
"path": "p202 config list-profiles",
"use": "list-profiles",
"short": "List all configured profiles",
"runnable": true,
"flags": [
{
"name": "tag",
"type": "string",
"default": "",
"usage": "Filter profiles by tag",
"required": false
}
]
}