This will be available in the next version. The tools accepted values they could not honour and reported some failures as successes: an unknown status, skillsMode, provider, reasoning effort or ticket type, a branch name git refuses (HEAD), or an agent or team that does not exist are now refused with an error and nothing is written; any answer with ok:false (missing note, prompt, skill, team, agent, command, setting, invalid team graph) now also sets isError:true; an unknown folderId in memory_list, prompts_list or skills_list is refused instead of looking like an empty folder, and memory_list returns totalInScope and totalAll; agents_get now includes every field of agents_list. Note that "in_review" is a real status (the review lane), so it stays accepted. If something still behaves this way after the update, please reopen the ticket with as many details as possible.
MCP tools: validate inputs and report failures as errors
From RogerJagerDone 6 days ago
Backlog accepts invalid status in list and update Runtime accepts a status outside the documented enum, persists it, and can query it back.
Runnable reproduction / implementation sketch backlog_list({"status":"in_review","limit":5}) backlog_update({"taskId":"<disposable-task-id>","status":"bogus"}) backlog_get({"taskId":"<disposable-task-id>"}) backlog_list({"status":"bogus","limit":5}) Steps Run the invalid list filter. Write bogus status to a disposable task. Fetch and filter by bogus. Restore or delete the task. Safety Use a disposable task. Restore it immediately if it matters.
Observed Invalid filter returns success; invalid write returns ok:true and persists; bogus filter returns the task.
Expected / proposed Enforce todo, in_progress, pending, or done at runtime.
Why it matters Tasks can disappear into unsupported states and simple agents may trust invalid writes.
Replies
Thanks: the bug is fixed and the fix ships in the next release. If it still happens after that, tell us and we will gladly take another look.