openclaw / openclaw/openclaw-windows-node

Add Windows Hub UI for gateway session maintenance settings

Open
#1,161 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

clawsweeper:needs-maintainer-review clawsweeper:needs-product-decision clawsweeper:no-new-fix-pr impact:ux-friction issue-rating: 🌊 off-meta tidepool P3
Dominant language
C#
Stars
2.1k
Forks
295
Avg merge
1d 6h
Merged PRs (30d)
99

Description

Problem

Windows Hub exposes the gateway's sessions list and a generic configuration editor, but it does not provide a dedicated UI for managing session.maintenance settings such as mode, pruneAfter, maxEntries, resetArchiveRetention, maxDiskBytes, and highWaterBytes.

Operators using Windows Hub should not need to edit raw gateway configuration to control session retention and disk usage.

Proposed UI

Add a Session maintenance section to the existing Gateway Configuration page that:

  • loads the current session.maintenance values from the connected gateway
  • exposes the supported settings with defaults and concise explanations
  • saves the full updated config through config.patch with optimistic concurrency
  • preserves unrelated gateway configuration
  • clearly handles disconnected, read-only, loading, validation, conflict, and save-result states

Acceptance criteria

  • Windows Hub can view and update all supported session.maintenance settings.
  • Omitted values display gateway defaults without unnecessarily materializing them until the user saves.
  • Numeric and duration/disk-size inputs are validated before saving.
  • Changes participate in the Configuration page's existing Save/Discard flow, preserve unrelated config, and refresh the gateway snapshot.
  • Focused model/UI contract tests cover parsing, validation, patch construction, and the Sessions page surface.
  • Current-head UI proof is attached, or an explicit Windows-host blocker is documented.

Upstream reference: docs/reference/session-management-compaction.md in openclaw/openclaw.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the existing Gateway Configuration page and its Save/Discard flow, then read docs/reference/session-management-compaction.md for the session.maintenance settings. Trace the config.patch path and existing model/UI tests before adding coverage for parsing, validation, patch construction, and the Sessions page surface. Done means all listed settings and states work without altering unrelated configuration, with current-head UI proof or a documented Windows-host blocker.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
desktop
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.