You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Strata 0.2.6 · Engine 0.1.50 Messed up toolcalls #4299
Thanks for the issue. To keep the tracker readable, every item needs an area prefix in the title and the parts of the issue form filled in. This one is missing:
Start the title with its area: [Engine], [GUI], [TUI], [Benchmark], [Docs] or [Other], then a short description. Example: "[Engine] decode stops after 2 minutes".
Add your graphics card with its VRAM, your RAM and your operating system.
Edit the issue (title and description) and this note goes away on its own. If it is still missing parts in 5 days it will be closed, which is not a rejection: fix it and comment /reopen.
I encountered this issue too: when the model calls a tool that was not declared in the request, frontend.py treats the call as plain text. The client therefore cannot return an “unknown tool” error, preventing the model from correcting the tool name.
My fix is to forward native tool calls with undeclared names as structured tool calls when the request provides tools. The client can then report the unknown tool and let the model retry. Requests without tool definitions retain the existing declared_only behavior.
Closing this issue because it still did not follow the format after 5 days. That is housekeeping, not a rejection.
To bring it back: fix the title (area prefix) and the missing parts, then comment /reopen. A check runs and reopens it, or tells you what is still missing. See CONTRIBUTING.md.
Activity
github-actions commentedon Oct 27, 2026
Thanks for the issue. To keep the tracker readable, every item needs an area prefix in the title and the parts of the issue form filled in. This one is missing:
Edit the issue (title and description) and this note goes away on its own. If it is still missing parts in 5 days it will be closed, which is not a rejection: fix it and comment
/reopen.Details: CONTRIBUTING.md
Chenj168 commentedon Oct 28, 2026
I encountered this issue too: when the model calls a tool that was not declared in the request, frontend.py treats the call as plain text. The client therefore cannot return an “unknown tool” error, preventing the model from correcting the tool name.
My fix is to forward native tool calls with undeclared names as structured tool calls when the request provides tools. The client can then report the unknown tool and let the model retry. Requests without tool definitions retain the existing declared_only behavior.
github-actions commentedon Nov 2, 2026
Closing this issue because it still did not follow the format after 5 days. That is housekeeping, not a rejection.
To bring it back: fix the title (area prefix) and the missing parts, then comment
/reopen. A check runs and reopens it, or tells you what is still missing. See CONTRIBUTING.md.