Issue Station
Sign In
Tools hereToolbox

openclaw - ✅(Solved) Fix [Bug]: Agent becomes completely unresponsive during Skill installation and does not report task completion [1 pull requests, 4 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#52073•Fetched 2026-04-08 01:15:57
View on GitHub
Comments
4
Participants
3
Timeline
10
Reactions
0
Author
benbenzhuyibenbenzhuyi
Participants
benbenzhuyibenbenzhuyiGMTekAIGMTekAIRyceRyce
Timeline (top)
commented ×4labeled ×2cross-referenced ×1mentioned ×1

When instructed via Telegram to install a Skill, the agent goes completely silent — no acknowledgment, no progress update, and no completion notification after the task finishes.

Root Cause

When instructed via Telegram to install a Skill, the agent goes completely silent — no acknowledgment, no progress update, and no completion notification after the task finishes.

Fix Action

Fixed

PR fix notes

PR #52140: fix(skills): propagate abort signal to download pipeline

Description (problem / solution / changelog)

Summary

  • The download timeout from fetchWithSsrFGuard only aborted the initial HTTP request
  • If the server responded with headers but stalled mid-stream, await pipeline(readable, file) hung indefinitely, making the agent unresponsive during skill installation
  • Moved timeout to a single AbortController covering both fetch and pipeline, passing the signal to pipeline() via its signal option

Test plan

  • Install a skill with a large download — verify it completes normally
  • Simulate a stalled mid-stream response (e.g. nc server that sends headers then pauses) — verify timeout fires and the agent recovers
  • Verify the timeout cleanup (clearTimeout) runs in the finally block

Fixes #52073

🤖 Generated with Claude Code

Changed files

  • src/agents/skills-install-download.ts (modified, +18/-5)
RAW_BUFFERClick to expand / collapse

Bug type

Crash (process/app exits or hangs)

Summary

When instructed via Telegram to install a Skill, the agent goes completely silent — no acknowledgment, no progress update, and no completion notification after the task finishes.

Steps to reproduce

  1. Send a Skill installation instruction to the agent via Telegram (e.g. "Please install XXX skill")
  2. Observe that the agent returns no reply and enters a silent state immediately
  3. Send any follow-up messages during task execution — all are ignored
  4. Wait for task completion — agent sends no notification
  5. Manually message the agent — only then does it process queued messages

Expected behavior

Agent should immediately acknowledge receipt of the instruction, send progress updates during execution, and proactively notify the user upon task completion or failure.

Actual behavior

Agent goes completely silent after receiving the instruction. No acknowledgment, no progress, no completion notice. Follow-up messages queue up with no response until the task finishes.

OpenClaw version

OpenClaw 2026.3.13

Operating system

Windows 11

Install method

npm install -g [email protected]

Model

minimax2.7

Provider / routing chain

Telegram -> OpenClaw Gateway (port 18789) -> Clash proxy (127.0.0.1:7890) -> minimax-portal (api.minimaxi.com)

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

Fix Plan

The fix involves modifying the Telegram handler in the OpenClaw Gateway to properly acknowledge and process messages.

  • Update the telegram-handler.js file to include an immediate acknowledgment response:
// Send acknowledgment response
telegramBot.sendMessage(chatId, 'Skill installation instruction received.');
  • Modify the skill installation function to send progress updates:
// Send progress updates
function installSkill(skillName) {
  // ...
  telegramBot.sendMessage(chatId, `Installing ${skillName}...`);
  // ...
  telegramBot.sendMessage(chatId, `Installation of ${skillName} complete.`);
}
  • Add error handling to send failure notifications:
// Send failure notification
try {
  // ...
} catch (error) {
  telegramBot.sendMessage(chatId, `Error installing skill: ${error.message}`);
}
  • Ensure the agent processes queued messages after task completion:
// Process queued messages
function processQueuedMessages() {
  // ...
}

Verification

To verify the fix, send a Skill installation instruction to the agent via Telegram and observe the response. The agent should immediately acknowledge receipt of the instruction, send progress updates during execution, and proactively notify the user upon task completion or failure.

Extra Tips

  • Ensure the Telegram Bot API is properly configured and authenticated.
  • Test the fix with different Skill installation instructions to ensure consistency.
  • Consider adding additional logging to track the agent's state and debug any further issues.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Agent should immediately acknowledge receipt of the instruction, send progress updates during execution, and proactively notify the user upon task completion or failure.

#api#installation#conversation history#tool integration#LLM response

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING