Skip to content

chore: add changeset for empty input guards #14

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Suprhimp merged 1 commit into from
May 25, 2026
Merged

chore: add changeset for empty input guards #14

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .changeset/empty-input-guards.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
'@planningo/duul': patch
---

Guard against empty MCP tool input. Sonnet subagents occasionally emit `request_plan_review` / `request_code_review` / `request_execution_partition` with an empty `{}` input, hitting MCP `-32602` in a retry loop they can't recover from. Now each tool traps empty/short input at handler entry and returns a tool-level error with a concrete retry example, instead of letting zod throw the opaque MCP `-32602`. Also strengthens zod `.describe()` strings and MCP tool descriptions to make the required-vs-optional distinction explicit, and adds a "Tool input rules" section to the `duul-planner` agent prompt.
Loading