Skip to content

fix(config): expose and preserve exec allow_remote#1363

Merged
wj-xiao merged 1 commit intosipeed:mainfrom
wj-xiao:fix/allow_remote
Mar 11, 2026
Merged

fix(config): expose and preserve exec allow_remote#1363
wj-xiao merged 1 commit intosipeed:mainfrom
wj-xiao:fix/allow_remote

Conversation

@wj-xiao
Copy link
Collaborator

@wj-xiao wj-xiao commented Mar 11, 2026

📝 Description

  • Preserve tools.exec.allow_remote=true when the field is omitted during config loading, OpenClaw migration, and PUT /api/config updates.
  • Expose the allow_remote toggle in the web config UI so the setting is round-tripped explicitly instead of relying on zero-value decoding.
  • Add regression tests for config defaults, migration behavior, and the backend config update path.

🗣️ Type of Change

  • 🐞 Bug fix (non-breaking change which fixes an issue)
  • ✨ New feature (non-breaking change which adds functionality)
  • 📖 Documentation update
  • ⚡ Code refactoring (no functional changes, no api changes)

🤖 AI Code Generation

  • 🤖 Fully AI-generated (100%% AI, 0%% Human)
  • 🛠️ Mostly AI-generated (AI draft, Human verified/modified)
  • 👨‍💻 Mostly Human-written (Human lead, AI assisted or none)

🔗 Related Issue

  • N/A

📚 Technical Context (Skip for Docs)

  • Reference URL: N/A
  • Reasoning: tools.exec.allow_remote is intended to default to true, but omitted fields in config files, migration input, and web config submissions could decode to false. This change makes the default explicit, preserves it on partial updates, and adds a UI control so the value is always serialized intentionally.

🧪 Test Environment

  • Hardware: arm64 Mac
  • OS: macOS 26.3.1
  • Model/Provider: N/A (config/backend/frontend path only)
  • Channels: N/A

📸 Evidence (Optional)

Click to view Logs/Screenshots
  • make check

☑️ Checklist

  • My code/docs follow the style of this project.
  • I have performed a self-review of my own changes.
  • I have updated the documentation accordingly.

- default tools.exec.allow_remote to true when omitted in config loading
- preserve allow_remote in OpenClaw config migration and API updates
- expose allow_remote in the web config form with i18n strings
- add backend and config tests covering the new default behavior
Copy link
Collaborator

@lxowalle lxowalle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@wj-xiao wj-xiao merged commit 8949a25 into sipeed:main Mar 11, 2026
4 checks passed
dj-oyu pushed a commit to dj-oyu/picoclaw that referenced this pull request Mar 14, 2026
- default tools.exec.allow_remote to true when omitted in config loading
- preserve allow_remote in OpenClaw config migration and API updates
- expose allow_remote in the web config form with i18n strings
- add backend and config tests covering the new default behavior
dj-oyu pushed a commit to dj-oyu/picoclaw that referenced this pull request Mar 16, 2026
- default tools.exec.allow_remote to true when omitted in config loading
- preserve allow_remote in OpenClaw config migration and API updates
- expose allow_remote in the web config form with i18n strings
- add backend and config tests covering the new default behavior
j0904 pushed a commit to j0904/picoclaw that referenced this pull request Mar 22, 2026
- default tools.exec.allow_remote to true when omitted in config loading
- preserve allow_remote in OpenClaw config migration and API updates
- expose allow_remote in the web config form with i18n strings
- add backend and config tests covering the new default behavior
@wj-xiao wj-xiao deleted the fix/allow_remote branch March 23, 2026 01:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants