openclaw - ✅(Solved) Fix [Bug]: Control UI Raw mode disabled (snapshot cannot safely round-trip raw text). [1 pull requests, 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#67926Fetched 2026-04-17 08:28:56
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Participants
Timeline (top)
labeled ×2

Since version 2026.3.31, the configuration file has been unable to be edited。#59330 Someone has already proposed it,Add #59336 has also been fixed, I thought it would be released soon. But after so many versions, it hasn't been merged yet. Does everyone not use this feature? Or who can tell me how to temporarily fix it. Sorry, my English is not very good and I am using translation software.

<img width="4596" height="2358" alt="Image" src="https://github.com/user-attachments/assets/5ef0d44b-f087-4ca4-aafc-f23a80047df8" />

Root Cause

Since version 2026.3.31, the configuration file has been unable to be edited。#59330 Someone has already proposed it,Add #59336 has also been fixed, I thought it would be released soon. But after so many versions, it hasn't been merged yet. Does everyone not use this feature? Or who can tell me how to temporarily fix it. Sorry, my English is not very good and I am using translation software.

<img width="4596" height="2358" alt="Image" src="https://github.com/user-attachments/assets/5ef0d44b-f087-4ca4-aafc-f23a80047df8" />

PR fix notes

PR #59336: fix: Config Raw mode permanently disabled due to round-trip check regression

Description (problem / solution / changelog)

Summary

Fixes #59330 — Control UI Config editor permanently shows "Raw mode disabled (snapshot cannot safely round-trip raw text)" since 2026.3.31.

Root Cause

Two issues cause shouldFallbackToStructuredRawRedaction() to always return true:

1. normalizeExecSafeBinProfilesInConfig assigns void 0 instead of deleting keys

When safeBinProfiles/safeBinTrustedDirs are empty, the normalize function assigns undefined:

typedExec.safeBinProfiles = ... ? normalizedProfiles : undefined;

This creates keys with undefined values. JSON-parsed objects can never have undefined-valued keys, so isDeepStrictEqual() always fails:

isDeepStrictEqual({ safeBinProfiles: undefined }, {}) // → false

2. shouldFallbackToStructuredRawRedaction compares against materialized config

The round-trip check compares the restored (raw-parsed) config against snapshot.config (the materialized runtime config), which contains transformations not present in the raw source:

  • ~/ paths expanded to absolute paths
  • Model api field inherited from provider level
  • Auto-generated alias fields on model entries
  • Default empty config: {} added to plugin entries

The comparison should use snapshot.parsed (the source config before materialization).

Changes

  1. src/config/normalize-exec-safe-bin.ts: Use delete instead of assigning undefined when profiles/dirs are empty.

  2. src/config/redact-snapshot.raw.ts:

    • Accept optional sourceConfig parameter for comparison target
    • Normalize both sides with JSON.parse(JSON.stringify()) to strip any remaining undefined-valued keys
  3. src/config/redact-snapshot.ts: Pass snapshot.parsed as sourceConfig to the round-trip check.

Testing

  • Verified locally: redactConfigSnapshot() now returns raw as a string (not null)
  • Raw mode is re-enabled in Control UI after these changes
  • Confirmed the fix handles all materialization diffs (path expansion, field inheritance, alias generation, default objects)

🤖 AI-assisted (Claude via OpenClaw). Fully tested locally against real config. I understand what the code does.

Changed files

  • src/config/normalize-exec-safe-bin.ts (modified, +10/-4)
  • src/config/redact-snapshot.raw.ts (modified, +26/-1)
  • src/config/redact-snapshot.ts (modified, +1/-0)
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Since version 2026.3.31, the configuration file has been unable to be edited。#59330 Someone has already proposed it,Add #59336 has also been fixed, I thought it would be released soon. But after so many versions, it hasn't been merged yet. Does everyone not use this feature? Or who can tell me how to temporarily fix it. Sorry, my English is not very good and I am using translation software.

<img width="4596" height="2358" alt="Image" src="https://github.com/user-attachments/assets/5ef0d44b-f087-4ca4-aafc-f23a80047df8" />

Steps to reproduce

none

Expected behavior

none

Actual behavior

none

OpenClaw version

2026.3.31

Operating system

Ubuntu 24.04

Install method

No response

Model

none

Provider / routing chain

none

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 with the configuration file being unable to be edited since version 2026.3.31 may be resolved by applying the fix proposed in pull request #59336.

Guidance

  • Review the changes proposed in pull request #59336 to understand the potential fix for the configuration file editing issue.
  • Consider reaching out to the maintainers or contributors of the OpenClaw project to inquire about the status of the pull request and potential alternatives for a temporary fix.
  • If possible, try applying the changes from the pull request manually to see if it resolves the issue.
  • Check the project's issue tracker and discussion forums for any updates or workarounds related to this issue.

Example

No code example is provided as the issue does not contain sufficient technical details to create a specific code snippet.

Notes

The provided information lacks specific technical details, and the issue seems to be related to a pending pull request. The effectiveness of the proposed fix is uncertain without further context.

Recommendation

Apply workaround: The best course of action seems to be to apply the fix proposed in pull request #59336, as it directly addresses the configuration file editing issue. However, this should be done with caution and ideally after consulting with the project maintainers or contributors.

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

none

Still need to ship something?

×6

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

Back to top recommendations

TRENDING