openclaw - 💡(How to fix) Fix Severe regression from 2026.3.13 to 2026.4.15: web actions degraded, image grabbing worse, tasks often go silent [1 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#68761Fetched 2026-04-19 15:07:57
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Author
Participants

I upgraded from 2026.3.13 to 2026.4.15, and the regression is very obvious.

After the update, the assistant became dramatically worse. This is not a subtle change, it feels like a major capability regression and is now barely usable for normal work.

Error Message

  • no clear error At minimum, if a task cannot be completed, the assistant should provide timely feedback, clear failure signals, or actionable error reporting.

Root Cause

I upgraded from 2026.3.13 to 2026.4.15, and the regression is very obvious.

After the update, the assistant became dramatically worse. This is not a subtle change, it feels like a major capability regression and is now barely usable for normal work.

RAW_BUFFERClick to expand / collapse

Summary

I upgraded from 2026.3.13 to 2026.4.15, and the regression is very obvious.

After the update, the assistant became dramatically worse. This is not a subtle change, it feels like a major capability regression and is now barely usable for normal work.

Regressions observed

Compared with 2026.3.13, several tasks that used to work with simple instructions now frequently fail or never complete:

  • Opening and navigating web pages is much worse than before
  • Extracting or grabbing images from web pages has regressed significantly
  • Tasks that used to be handled directly now often fail to execute

Most frustrating behavior

The worst part is not only failure, but the lack of timely feedback.

A common pattern now is:

  • I give a task
  • the assistant appears to start
  • then nothing happens
  • no useful progress update
  • no clear error
  • no completion
  • it just goes silent

This "black hole" behavior happens repeatedly and makes the product very hard to use in practice.

Expected

A version upgrade should maintain or improve capability and responsiveness.

At minimum, if a task cannot be completed, the assistant should provide timely feedback, clear failure signals, or actionable error reporting.

Actual

2026.4.15 feels like a clear downgrade in both execution ability and interaction quality:

  • weaker web interaction capability
  • worse image grabbing from pages
  • more failed simple tasks
  • frequent silent stalls with no timely feedback

Please investigate

Please check whether 2026.4.15 introduced regressions in:

  • browser or web automation behavior
  • image extraction / page parsing flows
  • tool-calling reliability
  • model routing or default model selection
  • runtime/task status reporting
  • timeout / failure handling
  • progress feedback behavior

Additional note

I can provide before/after examples, exact logs, and specific failed tasks if needed.

extent analysis

TL;DR

The most likely fix is to investigate and address the regressions introduced in version 2026.4.15, focusing on browser automation, image extraction, and task status reporting.

Guidance

  • Review the changes made between 2026.3.13 and 2026.4.15 to identify potential causes of the regressions, particularly in browser automation and image extraction functionality.
  • Investigate the tool-calling reliability and model routing or default model selection to ensure they are functioning as expected.
  • Check the runtime/task status reporting and timeout/failure handling mechanisms to improve timely feedback and error reporting.
  • Consider providing additional logging or debugging information to help diagnose the issues.

Example

No specific code snippet can be provided without more information on the implementation details.

Notes

The issue seems to be related to a version upgrade, and the exact cause is unclear. Further investigation and debugging are necessary to identify the root cause of the regressions.

Recommendation

Apply a workaround by reverting to version 2026.3.13 until the issues in 2026.4.15 are resolved, as the newer version introduces significant regressions in critical functionality.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix Severe regression from 2026.3.13 to 2026.4.15: web actions degraded, image grabbing worse, tasks often go silent [1 participants]