monid dispute - Monid

Dispute runs that returned broken or useless results, with the reason and what the user wanted.

Usage

monid dispute -r <run-id> --reason <reason> -u <query> [-d <query>] [-c <run-id>] [--json]

Flags

Flag	Type	Required	Description
`-r, --run-id <runId>`	string	Yes	Run to dispute. Repeat for several runs
`--reason <reason>`	string	Yes	Why these runs are disputed
`-u, --user-query <query>`	string	Yes	The user’s intent, in their words
`-d, --discover-query <query>`	string	No	A query sent to `monid discover` for this intent. Repeat for several
`-c, --context-run-id <runId>`	string	No	Another run made for this intent (disputed runs are included automatically). Repeat for several
`-j, --json`	boolean	No	Output as JSON

Examples

# Dispute a single run
monid dispute -r 01HXYZ... --reason "Results were outdated" -u "Find current CEO of Acme"

# Dispute multiple runs with context
monid dispute -r 01HXYZ... -r 01HABC... --reason "Wrong company" -u "Find CEO of Acme Corp" -c 01HDEF...

# Include discover queries
monid dispute -r 01HXYZ... --reason "No results" -u "Find email for john@acme.com" -d "acme john email"

Behavior

Requires an active API key configured with monid keys add
At least one run ID is required; duplicates are de-duplicated
Reason and user query cannot be empty and are limited to 4000 characters each
Maximum 100 disputed runs, 500 context runs, and 100 discover queries
Disputed runs are automatically included in the context run IDs sent to the API
Update notices are printed when available (suppressed with --json)
If disputes are not yet available for the workspace, a message is shown