openclaw - 💡(How to fix) Fix Request: Add cron.enabled and compaction.mode to ALLOWED_GATEWAY_CONFIG_PATHS [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#72166Fetched 2026-04-27 05:33:55
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
0
Author
Timeline (top)
closed ×1commented ×1labeled ×1

Allow cron.enabled and agents.defaults.compaction.mode to be configured via API

Error Message

Error: Configuration path is not allowed: cron.enabled
Error: Configuration path is not allowed: agents.defaults.compaction.mode

Root Cause

Yes. Users cannot programmatically configure cron.enabled or agents.defaults.compaction.mode via the OpenClaw API because these paths are hardcoded to reject API changes via the ALLOWED_GATEWAY_CONFIG_PATHS whitelist check.

Fix Action

Fix / Workaround

Current Workaround

All users who need to manage cron scheduler or agent compaction settings programmatically via the OpenClaw API. Severity: High - blocks dynamic configuration management. Workaround of direct file edits is fragile and may be overwritten on gateway restart.

Code Example

Error: Configuration path is not allowed: cron.enabled
Error: Configuration path is not allowed: agents.defaults.compaction.mode
RAW_BUFFERClick to expand / collapse

Summary

Allow cron.enabled and agents.defaults.compaction.mode to be configured via API

Problem to solve

Problem

cron.enabled and agents.defaults.compaction.mode cannot be configured through the OpenClaw API. These paths are not included in the ALLOWED_GATEWAY_CONFIG_PATHS whitelist.

Error

Error: Configuration path is not allowed: cron.enabled
Error: Configuration path is not allowed: agents.defaults.compaction.mode

Requested Solution

Add the following paths to ALLOWED_GATEWAY_CONFIG_PATHS:

  • cron.enabled
  • agents.defaults.compaction.mode

Use Cases

  • cron.enabled: Control the cron scheduler via API without manual file edits
  • agents.defaults.compaction.mode: Configure default agent compaction behavior for memory/performance optimization

Current Workaround

Direct file edits, but gateway may overwrite changes on restart if validation detects non-compliant config.

Proposed solution

Yes. Users cannot programmatically configure cron.enabled or agents.defaults.compaction.mode via the OpenClaw API because these paths are hardcoded to reject API changes via the ALLOWED_GATEWAY_CONFIG_PATHS whitelist check.

Alternatives considered

No response

Impact

All users who need to manage cron scheduler or agent compaction settings programmatically via the OpenClaw API. Severity: High - blocks dynamic configuration management. Workaround of direct file edits is fragile and may be overwritten on gateway restart.

Evidence/examples

No response

Additional information

No response

extent analysis

TL;DR

Add cron.enabled and agents.defaults.compaction.mode to the ALLOWED_GATEWAY_CONFIG_PATHS whitelist to enable configuration via the OpenClaw API.

Guidance

  • Identify the current ALLOWED_GATEWAY_CONFIG_PATHS configuration to understand the existing whitelist.
  • Add the required paths (cron.enabled and agents.defaults.compaction.mode) to the ALLOWED_GATEWAY_CONFIG_PATHS list.
  • Verify that the updated whitelist allows configuration of cron.enabled and agents.defaults.compaction.mode via the OpenClaw API.
  • Test the configuration changes to ensure they are not overwritten on gateway restart.

Example

No code example is provided as the issue does not include specific code snippets or APIs.

Notes

The proposed solution assumes that modifying the ALLOWED_GATEWAY_CONFIG_PATHS whitelist is feasible and allowed in the current system configuration.

Recommendation

Apply the workaround by adding the required paths to the ALLOWED_GATEWAY_CONFIG_PATHS whitelist, as this is the most direct solution to enable configuration via the OpenClaw API.

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 Request: Add cron.enabled and compaction.mode to ALLOWED_GATEWAY_CONFIG_PATHS [1 comments, 2 participants]