openclaw / openclaw/openclaw-windows-node
[Feature] Native chat: local slash command handling and compaction/context visibility
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2.1k
- Forks
- 295
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 99
Description
Environment
- Windows Hub: v2026.7.1-4 (stable, x64)
- OS: Windows 10 LTSC 21H2 (build 19044.2311), zh-CN locale
- Gateway: OpenClaw 2026.8.2 on WSL2
Three gaps between the native chat window and the web Control UI:
-
Slash commands: typing
/statusin native chat is sent to the agent as a plain message; the web Control UI handles it client-side and renders a status card. Please intercept client-side commands locally (at least/status,/compact). -
Compaction marker: after history compaction, the web Control UI shows a folding summary card, but Hub chat shows nothing — older history just disappears from view with no indication why. Please surface a compaction indicator.
-
Context usage: thanks for #551 (usage in the assistant timestamp footer) — works well. A persistent context-usage indicator would be a nice follow-up.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing native chat behavior with the web Control UI for /status and /compact, then inspect how native chat renders history and assistant usage. Done means local handling produces the corresponding status or compaction UI, and a persistent context-usage indicator is visible without sending commands to the agent.
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
- 52/100