[bug] Failure to call a tool due to an extra space in the tool name.

Description

Using Kimi K2 Thinking (and possibly other modes), it often fails because it tries to call tools like " bash" or " edit" instead of "bash" and "edit." After that, OpenCode tends to stop or start looping, repeating the same actions and consuming the quota.

OpenCode version

1.0.62

Steps to reproduce

Select Kimi K2 Thinking
Use it for a while

Screenshot and/or share link

Operating System

debian 13

Terminal

yakuake

This issue might be a duplicate of existing issues. Please check:

Tool calling when using opencode-skills plugin seem to loop and fail. #4158: Tool calling loops and failures with certain models - similar symptoms of looping and consuming quota
Kimi K2: thinking block does not render <think> tags #4263: Another Kimi K2 Thinking model issue with rendering problems - same model affected
OpenCode v1.0.25 Hangs Indefinitely with LM Studio + Qwen Models Due to Empty tool_calls Array #4255: Tool calling hangs and failures with LM Studio - similar hanging behavior after tool call failures

While these issues have different root causes (plugin conflicts, rendering issues, empty arrays vs spaces), they all involve tool calling problems that result in hanging, looping, or failure to proceed. The pattern of tool calling failures causing OpenCode to stop or loop appears consistent across these reports.

Feel free to ignore if none of these address your specific case with the extra space in tool names.

What provider is hosting this one?

We can prolly trim prefixed spaces... I doubt many people would have tools that have that...

What provider is hosting this one?
We can prolly trim prefixed spaces... I doubt many people would have tools that have that...

This is from openrouter.ai (very popular one).

It is said that the issue appears in other suppliers except for the main supplier of kimi.

I believe I'm facing the same issue. I'm on v1.0.72, using kimi k2 thinking using open router + vertex AI

This seems to only happen with this specific command for some reason? when I installed the package manually, and told it the package is installed, it kept going just fine, and is using tools correctly

I happen to have the exact same issue (leading space=error, openrouter and kimi-k2-thinking). Could it be possible to trim the tool name at some point before calling?

I just stumbled into this problem with new Kimi 2.5 model:

 invalid [tool= read, error=Model tried to call unavailable tool ' read'. Available tools: invalid, >uedtout. bash, read, glob, grep, edit,
     write, task, webfetch, todowrite, todoread, skill.]

I ran into it with Kimi 2.5, I made a plugin to solve it, here: https://github.com/EmanuelNog/opencode-trim-toolname-plugin

stumbled upon this on the new Kimi 2.6 model as well:

⚙ invalid [tool= edit, error=Model tried to call unavailable tool ' edit'. Available tools: invalid, question, bash, read, glob, grep, edit, write, task, webfetch, todowrite, skill, compress.]
Thinking: The edit call failed because of a space before the tool name. Let me try again properly.

@EmanuelNog

I ran into it with Kimi 2.5, I made a plugin to solve it, here: https://github.com/EmanuelNog/opencode-trim-toolname-plugin

HI @EmanuelNog
Thanks for creating this plugin to address the common issue where LLMs occasionally call tools with leading/trailing spaces (e.g., " read" instead of "read").

I was looking at how opencode(v1.4.20) handles tool execution, and I'm wondering if the current implementation actually catches the tool name before the AI SDK tries to resolve it. Based on my review of the opencode source code, it seems like tool.execute.before is triggered after the tool has already been successfully matched and identified by the AI SDK's streamText() function.

So by the time your hook receives the input.tool, the AI SDK has already (hopefully) resolved the correct tool name, or the error has already occurred. Your hook receives item.id which is the correct tool name from the registry, not the raw name from the LLM.

Have you been able to successfully test this scenario where the LLM sends " bash" and the plugin corrects it to "bash" before the error occurs?

I might be missing something ? 🤔

Have you been able to successfully test this scenario where the LLM sends " bash" and the plugin corrects it to "bash" before the error occurs?

Sorry for late reply, in fact I have not through-out tested it, I had no time to check implementation, I let kimi create the plugin and run it once, it worked, I'm still using it and have not had the same trailing space issue again, even in 2.6

To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.

Navigation Menu

Repository navigation

[bug] Failure to call a tool due to an extra space in the tool name. #4279

Description

OpenCode version

Steps to reproduce

Screenshot and/or share link

Operating System

Terminal

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[bug] Failure to call a tool due to an extra space in the tool name. #4279

Description

Description

OpenCode version

Steps to reproduce

Screenshot and/or share link

Operating System

Terminal

Activity

github-actions commented on Nov 13, 2025

rekram1-node commented on Nov 13, 2025

burbilog commented on Nov 14, 2025

EasyDevv commented on Nov 15, 2025

youcefs21 commented on Nov 18, 2025

bodzebod commented on Jan 31, 2026

burbilog commented on Feb 2, 2026

EmanuelNog commented on Feb 22, 2026

debemdeboas commented on Apr 22, 2026

KrabsWong commented on Apr 29, 2026

EmanuelNog commented on May 26, 2026

github-actions commented on Jul 26, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions