Before filing
Closest existing issue
none found
What's broken
The berd-help skill bundled with the app instructs agents to file feedback using berdctl feedback open / berdctl feedback submit. Neither subcommand exists in 0.6.2, so an agent following Berd's own bundled instructions hits a dead end — specifically in the bug-reporting instructions.
Steps to reproduce
- Launch Berd
- Read the bundled skill reference at
~/Library/Application Support/xyz.block.berd/skills/berd-help/references/reporting-problems.md (the same file ships inside the app bundle at Contents/Resources/distro/skills/berd-help/references/reporting-problems.md)
- Note it instructs: "Prefer
berdctl feedback open --title <title> --description <description>" and describes berdctl feedback submit
- Run
berdctl feedback --help
What you expected to happen
The command exists — or the skill describes the route that does exist (the in-app feedback dialog).
What actually happened
error: unrecognized subcommand 'feedback'
berdctl --help lists only session, folder, project, agent, skill, and info. Internal asset names suggest the feedback dialog itself exists in the app UI, so it appears to be specifically the CLI entry point named by the bundled docs that's missing. (If feedback is a gated/newer noun, the bundled skill still shouldn't recommend it unconditionally on builds where it's absent.)
How often does it happen?
Every time — reliably reproducible
Berd version
0.6.2
Operating system
macOS (Apple Silicon)
Model and provider
n/a — CLI only
Relevant log output
no relevant log output — berdctl rejects the subcommand client-side before it reaches the app, so nothing is written to the log.
Filed via gh (an agent helped investigate and draft; I reviewed before posting). Laid out with the bug-report form's fields since the API path doesn't render the form.
Before filing
Closest existing issue
none found
What's broken
The
berd-helpskill bundled with the app instructs agents to file feedback usingberdctl feedback open/berdctl feedback submit. Neither subcommand exists in 0.6.2, so an agent following Berd's own bundled instructions hits a dead end — specifically in the bug-reporting instructions.Steps to reproduce
~/Library/Application Support/xyz.block.berd/skills/berd-help/references/reporting-problems.md(the same file ships inside the app bundle atContents/Resources/distro/skills/berd-help/references/reporting-problems.md)berdctl feedback open --title <title> --description <description>" and describesberdctl feedback submitberdctl feedback --helpWhat you expected to happen
The command exists — or the skill describes the route that does exist (the in-app feedback dialog).
What actually happened
berdctl --helplists only session, folder, project, agent, skill, and info. Internal asset names suggest the feedback dialog itself exists in the app UI, so it appears to be specifically the CLI entry point named by the bundled docs that's missing. (Iffeedbackis a gated/newer noun, the bundled skill still shouldn't recommend it unconditionally on builds where it's absent.)How often does it happen?
Every time — reliably reproducible
Berd version
0.6.2
Operating system
macOS (Apple Silicon)
Model and provider
n/a — CLI only
Relevant log output
no relevant log output —
berdctlrejects the subcommand client-side before it reaches the app, so nothing is written to the log.Filed via
gh(an agent helped investigate and draft; I reviewed before posting). Laid out with the bug-report form's fields since the API path doesn't render the form.