Describe the bug
When write_to_file tool is called, the user is shown accept/deny buttons to approve the change + message box can be used for feedback.
Providing a /slash command within the message box for feedback does not lead to the slash command being expanded with the command body, it is instead included literally as the /command name.
Example: Background - bad analysis of an issue be local model, trying to get better feedback from a cloud model instead of the proposed diff.
API log:
"role": "assistant", "content": [ { "type": "text", "text": "\n\nLet me apply the fix REDACTED:\n\n" }, { "type": "tool_use", "id": "chatcmpl-tool-976841c597d3a9ea", "name": "write_to_file", "input": { "path": "REDACTED.file", "content": "REDACTED" } }
"role": "user", "content": [ { "type": "tool_result", "tool_use_id": "chatcmpl-tool-976841c597d3a9ea", "content": "{\"status\":\"denied\",\"feedback\":\"/handoff \\nPerform handoff to cloud model\"}" }, { "type": "text", "text": "REDACTED" } ],
Note the /handoff slash command has not been replaced, it is the /slash command name instead.
Within the message box UI the / is detected and slash commands listed, and the /handoff slash command is detected in the message box and highlighted to show it's a command that exists.
Correct feedback API call would be:
"role": "user", "content": [ { "type": "tool_result", "tool_use_id": "chatcmpl-tool-976841c597d3a9ea", "content": "{\"status\":\"denied\",\"feedback\":\"Please stop the current local editing task and hand off the problem to the cloud model with relevant context.............. etc, \\nPerform handoff to cloud model\"}" }, { "type": "text", "text": "REDACTED" } ],
To Reproduce
- Have any slash commands
- Initiate a file write tool call review
- Deny review and include slash command as feedback
Expected behavior
/slash command body expanded in tool call feedback as it is for standard messages.
What version of zoo are you running
3.73.100303 (d27153a)
Describe the bug
When write_to_file tool is called, the user is shown accept/deny buttons to approve the change + message box can be used for feedback.
Providing a /slash command within the message box for feedback does not lead to the slash command being expanded with the command body, it is instead included literally as the /command name.
Example: Background - bad analysis of an issue be local model, trying to get better feedback from a cloud model instead of the proposed diff.
API log:
"role": "assistant", "content": [ { "type": "text", "text": "\n\nLet me apply the fix REDACTED:\n\n" }, { "type": "tool_use", "id": "chatcmpl-tool-976841c597d3a9ea", "name": "write_to_file", "input": { "path": "REDACTED.file", "content": "REDACTED" } }"role": "user", "content": [ { "type": "tool_result", "tool_use_id": "chatcmpl-tool-976841c597d3a9ea", "content": "{\"status\":\"denied\",\"feedback\":\"/handoff \\nPerform handoff to cloud model\"}" }, { "type": "text", "text": "REDACTED" } ],Note the /handoff slash command has not been replaced, it is the /slash command name instead.
Within the message box UI the / is detected and slash commands listed, and the /handoff slash command is detected in the message box and highlighted to show it's a command that exists.
Correct feedback API call would be:
"role": "user", "content": [ { "type": "tool_result", "tool_use_id": "chatcmpl-tool-976841c597d3a9ea", "content": "{\"status\":\"denied\",\"feedback\":\"Please stop the current local editing task and hand off the problem to the cloud model with relevant context.............. etc, \\nPerform handoff to cloud model\"}" }, { "type": "text", "text": "REDACTED" } ],To Reproduce
Expected behavior
/slash command body expanded in tool call feedback as it is for standard messages.
What version of zoo are you running
3.73.100303 (d27153a)