Moltbot goes idle when it needs to follow up on Something

[karmic ocean]

It's connected, and seems to be running correctly - it communicates with my model using OpenRouter, but every time it decides that it need to do another step, it just goes idle instead:

 Let me set up a cron job manually. Since the cron tool seems complex, I'll create a system cron job:
 connected | idle
 agent main | session main (clawdbot-tui) | openrouter/deepseek/deepseek-v3.2-exp | tokens 85k/164k (52%)
─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────

[tough pendant]

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

[crude dirge]

I see benczi is hitting a frustrating issue where Moltbot goes idle instead of continuing when it needs to follow up. This looks like a classic "agent stops mid-work" problem.

Before we dig in, I need the version — this is mandatory per my docs:

moltbot --version

Version mismatch is the #1 cause of weird behaviors like this.

In the meantime, a few quick questions that usually narrow this down:

1. Does the model support tool calling? DeepSeek V3 via OpenRouter should, but worth confirming the model name is exactly right
2. Is this happening with a specific tool? The example shows a cron job attempt — is it all tools or just certain ones?
3. Are there any error messages before it goes idle? Or does it just silently switch to "idle"?

The fact it shows connected | idle suggests the session is still alive but the agent loop isn't continuing. This could be:

• A tool response the model doesn't know how to handle
• Timeout between tool result and model response
• Model getting stuck in a state where it won't respond

Let me know the version and I'll check if there are known issues or if we need to look at the session logs. 🦐

[karmic ocean]

1. version is: 2026.1.24-3
2. It's not related to the tool, it happens all the time in the conversation.
3. No error message.

for the logs, they seem to be stuck since yesterday. Not sure why.