openclaw / openclaw/openclaw-windows-node

Follow up Workspace file rail parity gaps

Open
#871 3 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

The initial Windows Workspace file rail adds the core session files experience: session-touched files, read/edited/missing state, metadata, path-driven folder browsing, server-side search/truncation messaging, copy-path actions, browser-only preview guards, and safe preview via the typed sessions.files.list / sessions.files.get APIs.

Remaining follow-up gaps to close against the main Control UI experience:

  • Show artifacts in the workspace rail when available.
  • Consider refresh/collapse affordances if they fit the Windows Workspace page layout.
  • Further polish visual sectioning if the page later moves closer to the chat-side rail presentation.

This should build on the existing WorkspaceFilesModel projection layer and canonical typed gateway APIs rather than duplicating protocol DTOs or parsing raw gateway payloads.

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 by tracing the existing WorkspaceFilesModel projection layer and the typed sessions.files.list and sessions.files.get gateway APIs. Compare the Windows Workspace rail with the main Control UI to determine how available artifacts, refresh or collapse affordances, and visual sectioning should fit the page. Done means the selected parity gaps are implemented without duplicating protocol DTOs or parsing raw gateway payloads.

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
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.