Skip to content

Strata 0.2.6 · Engine 0.1.50 Messed up toolcalls #4299

Closed as not planned
Closed as not planned

Description

@XeonG

Strata 0.2.6 · Engine 0.1.50
Swift 1.5 IQ3_XXS · swift-iq3_xxs · 128K

Seems to have alot now, with the last complete message just being a messed up tool call....

Research is complete and verified. Delegating implementation with the exact approved scope.

<tool_use> <parameter=name> run_in_terminal </parameter> <parameter=parameters> {"command": "cd /Users/test/ && git --no-pager diff -- [SitePage.php](http://_vscodecontentref_/10) [Chrome.php](http://_vscodecontentref_/11) [AdminModule.php](http://_vscodecontentref_/12) [Admin.html](http://_vscodecontentref_/13) misc/static/admin/_page-title.scss", "explanation": "Review the implementation diff.", "goal": "Verify implementation", "mode": "sync"} </parameter> </function> </tool_call>

Activity

  1. github-actions commented on Oct 27, 2026

    @github-actions

    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.

    Details: CONTRIBUTING.md

  2. Chenj168 commented on Oct 28, 2026

    @Chenj168

    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.

  3. github-actions commented on Nov 2, 2026

    @github-actions

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs-formatTitle or template does not follow CONTRIBUTING.md yet

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions