openclaw - 💡(How to fix) Fix [Bug]: JOSN string was truncated [1 comments, 2 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#77276Fetched 2026-05-05 05:50:14
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
2
Timeline (top)
closed ×1commented ×1labeled ×1

Root Cause

RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

image URL from json was truncated. https://dashscope-7c2c.oss-accelerate.aliyuncs.com/1d/e6/20260504/70729cf4/6aeada26-fd55-418a-863e-829f9ecf5aeb_0.png?Expires=1777980597&OSSAccessKeyId=LTAI5t…rym1&Signature=nRm46h…0%3D

There are three dots in the URL.

Steps to reproduce

Read URL from JSON field. The number of characters exceed a limit value. The URL was truncated, and three dots was used to replace the ommited characters. Web and TUI also have the same problem.

Expected behavior

Show the full URL

Actual behavior

The URL was truncated, and there are three dost in the URL.

OpenClaw version

2026.5...2

Operating system

Debian12

Install method

docker

Model

qwen3.6-plus

Provider / routing chain

OpenClaw->WebUI

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

The issue can be resolved by increasing the character limit for the JSON field to accommodate the full URL.

Guidance

  • Verify the current character limit for the JSON field and check if it can be increased to prevent truncation.
  • Investigate if there are any existing configuration options or parameters that can be adjusted to allow longer URLs.
  • Consider implementing URL shortening or a separate storage mechanism for long URLs to prevent truncation.
  • Check if the truncation is occurring at the JSON parsing level or during the rendering of the URL in the WebUI or TUI.

Example

No code example is provided as the issue does not specify the programming language or framework used.

Notes

The solution may depend on the specific implementation of the JSON field and the URL rendering in the WebUI and TUI. Additional information about the character limit and the truncation mechanism may be necessary to provide a more detailed solution.

Recommendation

Apply workaround: Increase the character limit for the JSON field or implement URL shortening to prevent truncation, as the root cause of the issue is likely related to the character limit.

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

Show the full URL

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 [Bug]: JOSN string was truncated [1 comments, 2 participants]