01Run it
Replace the <placeholders> with your own values, or use the builder below.
p202 config show02What 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 show Config file: /home/you/.p202/config.json Active: default Profile: default URL: https://track.example.com API key: 4f1c...9d0e Profiles: default Output: table (flag)
$ p202 config show --json { "active_profile": "default", "api_key": "4f1c...9d0e", "available_names": [ "default" ], "config_path": "/home/you/.p202/config.json", "output_format": "json", "output_source": "flag", "profile": "default", "url": "https://track.example.com" }
03Build your command
Pick values and the command line writes itself, quoted and ready to paste.
p202 config showSet flags below; the command updates as you type.
04For agents
Running this from an agent
- Read the same facts as JSON:
p202 commands config show --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 show",
"use": "show",
"short": "Show current configuration",
"runnable": true
}