Droid fails to make tool call and stops working on plan #793
Description
I have been using droid for a few weeks with good success. This week it started malfunctioning and is pretty much unusable at the moment.
The issue is when I ask it to do something, it will start working on it, but then it will stop when it tries to make a tool call. Instead of making the tool call and proceeding, it instead seems to print out the xml for the tool call and stops as if it is done with the task, even though it isn't.
For reference I am using stepfun/step-3.5-flash:free via open router.
Here is a sample text of the latest session:
v0.74.0
You are standing in an open terminal. An AI awaits your commands.
ENTER to send • \ + ENTER for a new line • @ to mention files
Current folder: C:\Users\samue\workspace\defense_mud
> In game/core.py:1297, there is a to do. Please complete it, including writing tests in tests/game.feature
using the existing step definitions,
⛬ I'll help you complete the TODO in game/core.py at line 1297 and add tests in tests/game.feature. Let me
first explore the codebase to understand the context.
READ (\game\core.py, offset: 1290, limit: 30)
↳ Read 32 lines.
READ (\tests\game.feature)
↳ Read 1312 lines.
GLOB (**/*.py)
↳ Found 18 files.
⛬ Let me read more of the handle_put function to see what the TODO is about:
READ (\game\core.py, offset: 1290, limit: 40)
↳ Read 42 lines.
GREP ("FoodStorage", content mode)
↳ Read 9 lines.
READ (\game\core.py, offset: 1320, limit: 50)
↳ Read 52 lines.
⛬ Let me check how the command parsing works and see examples of handling missing arguments in other
commands:<tool_call>
<function=Grep>
<parameter=-A>
2
</parameter>
<parameter=-B>
2
</parameter>
<parameter=output_mode>
content
</parameter>
<parameter=path>
C:\Users\samue\workspace\defense_mud\game\core.py
</parameter>
<parameter=pattern>
Take what\?
</parameter>
</function>
</tool_call>
READ (\game\core.py, offset: 1100, limit: 50)
↳ Read 52 lines.
⛬ <tool_call>
<function=Grep>
<parameter=-A>
30
</parameter>
<parameter=output_mode>
content
</parameter>
<parameter=path>
C:\Users\samue\workspace\defense_mud\game\core.py
</parameter>
<parameter=pattern>
@COMMAND_REGISTRY.handler("drop"
</parameter>
</function>
</tool_call>
> In game/core.py:1297, there is a to do. Please complete it, including writing tests in tests/game.feature
using the existing step definitions,
⛬ <tool_call>
<function=Grep>
<parameter=-A>
20
</parameter>
<parameter=output_mode>
content
</parameter>
<parameter=path>
C:\Users\samue\workspace\defense_mud\game\core.py
</parameter>
<parameter=pattern>
@COMMAND_REGISTRY.handler("drop"
</parameter>
</function>
</tool_call><tool_call>
<function=Grep>
<parameter=-A>
20
</parameter>
<parameter=output_mode>
content
</parameter>
<parameter=path>
C:\Users\samue\workspace\defense_mud\game\core.py
</parameter>
<parameter=pattern>
@COMMAND_REGISTRY.handler("take"
</parameter>
</function>
</tool_call><tool_call>
<function=Grep>
<parameter=-A>
20
</parameter>
<parameter=output_mode>
content
</parameter>
<parameter=path>
C:\Users\samue\workspace\defense_mud\game\core.py
</parameter>
<parameter=pattern>
@COMMAND_REGISTRY.handler("equip"
</parameter>
</function>
</tool_call>
PLAN Updated: 4 total (3 pending, 1 in progress, 0 completed)
○ Understand the TODO in handle_put function and existing argument parsing patterns
○ Implement proper argument validation in handle_put at line 1297
○ Write test scenarios in tests/game.feature for the put command edge cases
○ Verify tests pass with the implementation
⛬ <tool_call>
<function=Grep>
<parameter=-A>
30
</parameter>
<parameter=-B>
5
</parameter>
<parameter=output_mode>
content
</parameter>
<parameter=path>
C:\Users\samue\workspace\defense_mud\game\core.py
</parameter>
<parameter=pattern>
class CommandRegistry
</parameter>
</function>
</tool_call><tool_call>
<function=Grep>
<parameter=-A>
30
</parameter>
<parameter=output_mode>
content
</parameter>
<parameter=path>
C:\Users\samue\workspace\defense_mud\game\core.py
</parameter>
<parameter=pattern>
def handler(
</parameter>
</function>
</tool_call>
Auto (Low) - edits and read-only commands Step-3.5-flash:free [OpenRouter] [custom]
ctrl+T to cycle modes (auto/spec), ctrl+L for autonomy ctrl+N to cycle models
>
[⏱ 1m 30s]? for help | POWERSHELL ▶