-
State changed as build TOD-239 (4.4.0) is successful
-
OneDev
changed state to 'Closed' 3 weeks ago
Previous Value Current Value Open
Closed
| Type |
Enhancement
|
| Priority |
Minor
|
| Assignee | |
| Labels |
No labels
|
Issue Votes (0)
Current behavior (tod 4.3.4). When
issue create,issue editorissue change-stategets--field Type=Taks, the error says “Invalid choice value” and nothing else. The agent has to calltod issue get-valid-fields, find the field and retry.Proposal. Include the valid choices of the offending field in the error message, for example
Invalid choice value "Taks" for field "Type"; valid values: Bug, Task, Improvement.Why. Anthropic’s guidance for agent tools recommends exactly this: “prompt-engineer your error responses to clearly communicate specific and actionable improvements, rather than opaque error codes” (“Writing effective tools for agents”, anthropic.com/engineering/writing-tools-for-agents). It turns one failed call plus two recovery calls into a single retry.