Skip to content

docs: propose demand-driven session sidebar collections - #64

Draft
clawsweeper wants to merge 2 commits into
mainfrom
rfc/0031-demand-driven-session-sidebar
Draft

docs: propose demand-driven session sidebar collections#64
clawsweeper wants to merge 2 commits into
mainfrom
rfc/0031-demand-driven-session-sidebar

Conversation

@clawsweeper

@clawsweeper clawsweeper commented Aug 23, 2026

Copy link
Copy Markdown

Related: openclaw/openclaw#126701
Related: openclaw/openclaw#126708
Discussion: https://discord.com/channels/1456350064065904867/1541083365103370340

What Problem This Solves

The Control UI sidebar currently derives heterogeneous groups from a bounded
global session page. An expanded category can therefore look complete while
omitting sessions that fall beyond the global page, and loading another global
page can redistribute rows into several unrelated groups.

This RFC gives maintainers a concrete architecture to review before replacing
that behavior.

Why This Change Was Made

The proposal models the sidebar as an async tree: a lightweight root manifest
returns authoritative section summaries, while each expanded and visible
collection owns an independent cursor-backed child connection. A single
flattened virtual list controls rendered demand, and collapsed or distant groups
load no child rows.

The RFC also defines exact local counts, a canonical attention summary,
collection membership precedence, filter/cursor fencing, live invalidation,
bounded caching, failure states, migration steps, alternatives, and unresolved
thresholds.

The RFC remains status: draft; its implementation issue stays blank until
maintainer acceptance.

AI-assisted: yes. Jesse Merhi directed the product requirements and is credited
as an RFC author and commit co-author.

User Impact

This PR changes no shipped behavior. If accepted and implemented, operators
will get complete ordinary groups when they open them, accurate collapsed
counts and attention indicators, and no background loading for sidebar groups
they are not viewing.

Evidence

  • Started from rfcs/0000-template.md and includes all required frontmatter
    and top-level sections.
  • Audited the current OpenClaw sidebar grouping, pagination, catalog, and
    session-attention owners before defining the proposal.
  • Compared the design with VS Code Tree Views, MUI lazy tree loading, TanStack
    Virtual, and the Relay cursor connection contract.
  • git diff --cached --check passed before commit.
  • Direct documentation review found no broken structure, inconsistent
    ownership rule, or unsupported new dependency.
  • External-model autoreview was not run because its safety gate did not
    authorize exporting the unpublished RFC before publication.
Co-authored-by: jesse-merhi <79823012+jesse-merhi@users.noreply.github.com>
@clawsweeper

clawsweeper Bot commented Aug 23, 2026

Copy link
Copy Markdown

🦞👀
ClawSweeper picked this up.

Pull request received. I will update this pull request when review starts.

@clawsweeper clawsweeper Bot added P3 Low-risk cleanup, docs, polish, ergonomics, or speculative feature. rating: 🐚 platinum hermit Good normal PR readiness with ordinary maintainer review expected. status: 👀 ready for maintainer look ClawSweeper has no concrete contributor-facing blocker left for this PR. labels Aug 23, 2026
@clawsweeper

clawsweeper Bot commented Aug 23, 2026

Copy link
Copy Markdown

Codex review: needs real behavior proof before merge. Reviewed September 1, 2026, 1:57 AM ET / 05:57 UTC.

ClawSweeper review

What this changes

The PR adds a draft RFC proposing independently paginated, demand-driven session collections for the Control UI sidebar.

Merge readiness

Blocked until real behavior proof is added - 4 items remain

Keep open for RFC acceptance: this is a structurally compliant draft that proposes a substantial Gateway and Control UI contract, with implementation intentionally deferred until maintainers accept the direction.

Priority: P3
Reviewed head: 04bec7369788586004cf6efbae04503c99b9f166
Owner decision: Required. See Decision needed.

Review scores

Measure Result What it means
Overall readiness 🧂 unranked krab (1/6) The RFC is well-structured and internally coherent, but it lacks the real-behavior evidence required for this external PR before merge.
Proof confidence 🧂 unranked krab (1/6) Needs real behavior proof before merge: The RFC describes a future Gateway and sidebar behavior, but the supplied PR body contains no real setup evidence of the claimed sidebar failure or an after-change demonstration; the literal docs-only exception does not cover this file under rfcs/. After adding proof, update the PR body; ClawSweeper should re-review automatically. If it does not, the PR author or someone with repository write access can comment @clawsweeper re-review.
Patch quality 🐚 platinum hermit (4/6) No actionable review findings were identified.

Verification

Check Result Evidence
Real behavior Needs proof Needs real behavior proof before merge: The RFC describes a future Gateway and sidebar behavior, but the supplied PR body contains no real setup evidence of the claimed sidebar failure or an after-change demonstration; the literal docs-only exception does not cover this file under rfcs/. After adding proof, update the PR body; ClawSweeper should re-review automatically. If it does not, the PR author or someone with repository write access can comment @clawsweeper re-review.
Evidence reviewed 6 items RFC lifecycle policy: The repository requires new RFCs to start as draft PRs, leave the implementation issue blank until acceptance, and merge only after acceptance.
Draft lifecycle metadata: The added RFC is marked draft, leaves its implementation issue blank, and links this RFC PR, matching the repository lifecycle.
Implementation is deliberately deferred: The proposal specifies acceptance followed by a separately created implementation issue and boundary tests, so this branch adds no shipped runtime behavior.
Findings None None.
Security None None.

How this fits together

The RFC repository records design decisions before implementation work begins. This proposal routes sidebar filters through Gateway-owned collection summaries and per-collection pages into a virtualized Control UI session list.

flowchart LR
A[Sidebar filters] --> B[Gateway collection layer]
B --> C[Collection summaries]
B --> D[Per-collection pages]
C --> E[Sidebar manifest]
D --> F[Virtualized session sidebar]
E --> F
Loading

Decision needed

Question Recommendation
Should maintainers accept this collection-level Gateway and sidebar architecture as the direction for replacing global-roster grouping? Accept the RFC direction: Create the implementation issue, set the RFC to accepted, and scope delivery into Gateway and Control UI migration slices.

Why: The branch changes no runtime behavior, but it proposes a broad cross-component contract and explicitly leaves several policy and rollout choices unresolved.

Before merge

  • Add real behavior proof - Needs real behavior proof before merge: The RFC describes a future Gateway and sidebar behavior, but the supplied PR body contains no real setup evidence of the claimed sidebar failure or an after-change demonstration; the literal docs-only exception does not cover this file under rfcs/. After adding proof, update the PR body; ClawSweeper should re-review automatically. If it does not, the PR author or someone with repository write access can comment @clawsweeper re-review.
  • Resolve merge risk (P1) - Merging while the RFC remains a draft would bypass the documented acceptance and implementation-issue lifecycle.
  • Resolve merge risk (P1) - The proposed Gateway/UI contract leaves cursor budgets, catalog-summary semantics, and transport batching for maintainer product and ownership decisions.
Agent review details

Security

None.

Review metrics

Metric Value Why it matters
Design surface 1 RFC added; 412 lines The single document defines a broad future Gateway and Control UI contract that merits focused design review.

Merge-risk options

Maintainer options:

  1. Decide the mitigation before merge
    Resolve the architecture questions through RFC review, then create a scoped implementation issue covering Gateway collection boundaries, Control UI migration slices, and browser proof before merging an accepted RFC.
  2. Pause or close
    Do not merge this PR until maintainers decide whether the risk is worth taking.

Technical review

Best possible solution:

Resolve the architecture questions through RFC review, then create a scoped implementation issue covering Gateway collection boundaries, Control UI migration slices, and browser proof before merging an accepted RFC.

Do we have a high-confidence way to reproduce the issue?

Not applicable: the branch adds a future-facing design document, not an executable behavior change. The referenced sidebar problem is outside this repository and was not independently reproduced here.

Is this the best way to solve the issue?

Unclear: the collection contract is coherent and explicitly preserves key boundaries, but the unresolved catalog, cursor, and rollout choices require maintainer acceptance before it is the settled implementation path.

AGENTS.md: not found in the target repository.

Codex review notes: model internal, reasoning high; reviewed against 967d9aac7472.

Labels

Label changes:

  • add rating: 🧂 unranked krab: Overall readiness is 🧂 unranked krab; proof is 🧂 unranked krab and patch quality is 🐚 platinum hermit.
  • remove rating: 🐚 platinum hermit: Current PR rating is rating: 🧂 unranked krab, so this older rating label is no longer current.

Label justifications:

  • P3: This draft design proposal changes no shipped behavior and awaits product-direction review.
  • rating: 🧂 unranked krab: Overall readiness is 🧂 unranked krab; proof is 🧂 unranked krab and patch quality is 🐚 platinum hermit.
  • feature: ✨ showcase: ClawSweeper spotlight: unusually compelling feature idea for maintainer attention. The proposal gives a detailed, user-centered architecture for making heterogeneous sidebar collections complete without eager loading.
  • status: 📣 needs proof: The PR needs real behavior proof before ClawSweeper can clear the contributor ask. Needs real behavior proof before merge: The RFC describes a future Gateway and sidebar behavior, but the supplied PR body contains no real setup evidence of the claimed sidebar failure or an after-change demonstration; the literal docs-only exception does not cover this file under rfcs/. After adding proof, update the PR body; ClawSweeper should re-review automatically. If it does not, the PR author or someone with repository write access can comment @clawsweeper re-review.

Evidence

What I checked:

Likely related people:

  • Jesse Merhi: Suggested for follow-up; no historical authorship or introduction is verified. (role: unverified routing candidate; confidence: low)

Rank-up moves

Optional improvements that raise the rating; they are not merge blockers.

  • Add a redacted screenshot, recording, or runtime trace showing the current truncated-group behavior and any available expected-result comparison to the PR body, then request a fresh review.
  • Obtain maintainer direction on the proposed collection contract and record the resulting implementation boundary.

Rating scale

Score Internal tier Crab rank Meaning
6/6 S 🦀 challenger crab Exceptional readiness
5/6 A 🦞 diamond lobster Very strong readiness
4/6 B 🐚 platinum hermit Good normal PR; ordinary maintainer review
3/6 C 🦐 gold shrimp Useful, but confidence is limited
2/6 D 🦪 silver shellfish Proof or implementation needs work
1/6 F 🧂 unranked krab Not merge-ready
N/A NA 🌊 off-meta tidepool Rating does not apply

Overall follows the weaker of proof and patch quality.
Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

Workflow

  • ClawSweeper keeps one durable marker-backed review comment per issue or PR.
  • Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
  • A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
  • PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
  • Maintainers can also comment @clawsweeper review to request a fresh review only.
  • Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
  • Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
  • Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

History

Review history (14 earlier review cycles; latest 8 shown)
  • reviewed 2026-08-25T19:30:28.189Z sha 04bec73 :: needs real behavior proof before merge. :: none
  • reviewed 2026-08-26T06:01:16.093Z sha 04bec73 :: needs real behavior proof before merge. :: none
  • reviewed 2026-08-26T17:15:02.087Z sha 04bec73 :: needs real behavior proof before merge. :: none
  • reviewed 2026-08-27T12:17:14.264Z sha 04bec73 :: needs real behavior proof before merge. :: none
  • reviewed 2026-08-29T16:59:06.995Z sha 04bec73 :: needs real behavior proof before merge. :: none
  • reviewed 2026-08-29T23:05:16.930Z sha 04bec73 :: needs real behavior proof before merge. :: none
  • reviewed 2026-08-30T07:44:19.929Z sha 04bec73 :: needs real behavior proof before merge. :: none
  • reviewed 2026-08-31T18:10:45.331Z sha 04bec73 :: needs real behavior proof before merge. :: none
@clawsweeper clawsweeper Bot added rating: 🦞 diamond lobster Very strong PR readiness with only minor maintainer review expected. rating: 🐚 platinum hermit Good normal PR readiness with ordinary maintainer review expected. feature: ✨ showcase ClawSweeper spotlight: unusually compelling feature idea for maintainer attention. and removed rating: 🐚 platinum hermit Good normal PR readiness with ordinary maintainer review expected. rating: 🦞 diamond lobster Very strong PR readiness with only minor maintainer review expected. labels Aug 23, 2026
@clawsweeper clawsweeper Bot added status: 📣 needs proof The PR needs real behavior proof before ClawSweeper can clear the contributor ask. rating: 🧂 unranked krab Not merge-ready due to missing proof or serious correctness/safety concerns. and removed status: 👀 ready for maintainer look ClawSweeper has no concrete contributor-facing blocker left for this PR. rating: 🐚 platinum hermit Good normal PR readiness with ordinary maintainer review expected. labels Aug 31, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

feature: ✨ showcase ClawSweeper spotlight: unusually compelling feature idea for maintainer attention. P3 Low-risk cleanup, docs, polish, ergonomics, or speculative feature. rating: 🧂 unranked krab Not merge-ready due to missing proof or serious correctness/safety concerns. status: 📣 needs proof The PR needs real behavior proof before ClawSweeper can clear the contributor ask.

2 participants