01Run it
Replace the <placeholders> with your own values, or use the builder below.
p202 click-filter list update <entry-id>02What you get
Pick the shape you need. People get a table. Add
--json, --csv or --ndjson for scripts, or -q for ids only. An AI agent gets compact JSON without asking. All output formats03Build your command
Pick values and the command line writes itself, quoted and ready to paste.
p202 click-filter list updateSet flags below; the command updates as you type.
04Flags
4 flags, plus the global flags every command takes.
| Flag | What it does |
|---|---|
| --actionstring | count or filter: count, filtercountfilter |
| --addressstring | New address or CIDR block |
| --notestring | New note ("" clears it) |
| --user-idstring | Account whose click filter this is (default: the API key's own user) |
05For agents
Running this from an agent
- Read the same facts as JSON:
p202 commands click-filter list update --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, 6 no Pro licence on the install.
- This command writes. Add
--stagedto record it as a proposal a person applies withp202 change apply.
{
"path": "p202 click-filter list update",
"use": "update <entry-id>",
"short": "Change an entry's address, action or note",
"runnable": true,
"flags": [
{
"name": "action",
"type": "string",
"default": "",
"usage": "count or filter: count, filter",
"allowed_values": [
"count",
"filter"
],
"required": false
},
{
"name": "address",
"type": "string",
"default": "",
"usage": "New address or CIDR block",
"required": false
},
{
"name": "note",
"type": "string",
"default": "",
"usage": "New note (\"\" clears it)",
"required": false
},
{
"name": "user-id",
"type": "string",
"default": "",
"usage": "Account whose click filter this is (default: the API key's own user)",
"required": false
}
]
}