Skip to content

docs: correct two CLI facts in AGENTS.md - #5573

Open
jimparkins wants to merge 1 commit into
block:mainfrom
jimparkins:docs/cli-corrections
Open

docs: correct two CLI facts in AGENTS.md#5573
jimparkins wants to merge 1 commit into
block:mainfrom
jimparkins:docs/cli-corrections

Conversation

@jimparkins

Copy link
Copy Markdown

Two factual corrections to the agent guide, both verified against crates/buzz-cli/src/commands/messages.rs at be48ce9.

1. messages search has no --kinds flag

Gotcha 3 currently says an open-ended search hits the relay p-gate and to pass --kinds to scope it. Neither half holds:

  • search hardcodes an explicit kind filter — "kinds": [9, 40002, 45001, 45003] at messages.rs:451 — so the documented failure cannot occur.
  • There is no --kinds argument on the subcommand, so the documented fix is an unrecognized-argument error.

messages get is the subcommand that accepts --kinds (messages.rs:359, default [9, 40002, 40008, 45001, 45003] at :366), which is the likely origin of the confusion. The replacement text says so, since that is the question a reader arrives with.

2. The deep-link example contradicts the rule 14 lines below it

The example trails --format compact after the subcommand:

buzz messages thread --channel <uuid> --event <hex> --format compact

while the guide states correctly a few lines later that --format compact is a global flag that goes before the subcommand. Reordered to match.


Found while building an out-of-tree buzz-backend-* provider that runs Buzz agents in Orca worktrees — the search line sent me looking for a flag that does not exist.

Note the edit is to AGENTS.md; CLAUDE.md is a symlink to it.

Both verified against crates/buzz-cli/src/commands/messages.rs at be48ce9.

`messages search` has no --kinds flag. It hardcodes an explicit kind filter
(messages.rs:451), so the documented failure — an open-ended search hitting
the relay p-gate — cannot occur, and the documented fix is an
unrecognized-argument error. `messages get` is the subcommand that accepts
--kinds (messages.rs:359, default at :366), which is the likely origin of the
confusion.

The deep-link example trailed `--format compact` after the subcommand,
contradicting the correct statement 14 lines below it that --format is global.

Found while building an out-of-tree buzz-backend-* provider; the search line
sent me looking for a flag that does not exist.

Signed-off-by: Jim Parkins <jimparkins@gmail.com>
@jimparkins
jimparkins requested a review from a team as a code owner August 11, 2026 14:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant