Enable Companion App to use session backed OpenClaw #1236

Activity

1. github-project-automation

   added this to Windows Companion Appon Aug 26, 2026
2. github-project-automation

   moved this to Backlog in Windows Companion Appon Aug 26, 2026
3. clawsweeper

   added

   clawsweeper:needs-maintainer-reviewClawSweeper marked this issue as needing maintainer review before automation.ClawSweeper marked this issue as needing maintainer review before automation.

   clawsweeper:needs-product-decisionClawSweeper marked this issue as needing a product or behavior decision.ClawSweeper marked this issue as needing a product or behavior decision.

   clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.ClawSweeper does not recommend queueing a new automated fix PR for this issue.

   issue-rating: 🌊 off-meta tidepoolIssue quality rating does not apply to this item.Issue quality rating does not apply to this item.

   P3Low-risk cleanup, docs, polish, ergonomics, or speculative feature.Low-risk cleanup, docs, polish, ergonomics, or speculative feature.

   on Aug 26, 2026
4. clawsweeper commented on Aug 26, 2026

   

   clawsweeperbot

   on Aug 26, 2026 – with ClawSweeper

   Last edited by clawsweeper

   More actions

   Codex review: this still needs some work. Reviewed October 3, 2026, 8:20 AM ET / 12:20 UTC.

   Summary
   Keep open: native onboarding and isolated-session integration now exist, but supported WSL migration and complete native Gateway management remain unfinished. No single related item covers the remaining umbrella scope.

   Likely related people: karkarl and Paul Campbell for native setup/runtime integration; samanthamsong for the requested product scope.

   Reproducibility: not applicable. this is a multi-capability feature request, and source inspection confirms both implemented native integration and unfinished management surfaces.

   Root-cause cluster
   Relationship: canonical
   Canonical: #1236
   Summary: This remains the umbrella for several explicitly linked capabilities; narrower issues and merged PRs cover only parts.

   Members:

   • partial_overlap: Session-aware Node routing skill #1323 - Tracks the session-aware Node-routing requirement added in collaborator discussion.
   • partial_overlap: Windows Gateway MSIX packaging, distribution, and update plumbing #1324 - Tracks Gateway distribution and update plumbing.
   • partial_overlap: Add README guidance for migrating to MXC Sessions #1435 - Tracks migration documentation without implementing migration.
   • partial_overlap: feat(setup): guide native Gateway installation and onboarding #1447 - Merged native capability detection, acquisition, and onboarding.
   • partial_overlap: fix: Companion cannot onboard with an isolated Gateway #1553 - Merged package-owned isolated-session integration.
   • 1 more in the report.

   Proposal only: this assessment does not dispatch repair, suppress jobs, mutate sibling items, close, or merge anything.

   Maintainer decision needed

   Question	Recommendation
   Should this umbrella remain open until WSL migration, native update/recovery controls, and Gateway-wide tool containment are delivered, or should its acceptance scope be narrowed to the implemented native onboarding?	Retain explicit remaining acceptance criteria: Keep the umbrella open, mark implemented onboarding/session ownership complete, and assign migration, management, and containment deliverables to focused owners.

   Why: The central integration has landed, but the original checklist and collaborator expansion include distinct unfinished capabilities whose acceptance boundary cannot be chosen from source alone.

   Next step
   Refresh the umbrella checklist against merged work and settle the remaining cross-repository migration and containment scope before commissioning focused implementation.

   Review details

   Best possible solution:

   Finish guided migration and native management through package-owned lifecycle APIs, with visible repair controls and separately defined Gateway tool-containment guarantees.

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

   Not applicable: this is a multi-capability feature request, and source inspection confirms both implemented native integration and unfinished management surfaces.

   Is this the best way to solve the issue?

   Partly: the package-owned isolated runtime is the maintainable foundation, but treating new native setup as WSL migration or universal tool containment would overstate what it implements.

   AGENTS.md: found and applied where relevant.

   Remaining risk / open question:

   • WSL-to-native migration still needs explicit data-preservation, credential-transfer, rollback, and recovery acceptance criteria.
   • Per-node system.run containment does not establish the requested containment policy for every Gateway tool invocation.

   Codex review notes: model internal, reasoning medium; reviewed against a6c5fb276f9f.

   Label changes

   Label changes:

   No label changes.

   Label justifications:

   • P2: This is an unfinished native setup and migration program; the report itself establishes no current emergency or blocked first-run reproduction.
   • impact:other: The request affects local Gateway hosting, installation ownership, migration, and lifecycle management.

   Evidence reviewed

   What I checked:

   • Repository policy and current revision: Read the complete root AGENTS.md. Its package-ownership and architecture guidance informed the review. The verified origin is the target repository and checkout HEAD matches the supplied current-main SHA. No code changes, builds, or tests were performed; final git status was clean. (AGENTS.md:3, a6c5fb276f9f)
   • Native capability detection is implemented: Native eligibility evaluates the actual MXC isolation-session capability and distinguishes failed checks, unsupported platforms, and unavailable capability. It preserves an explicit WSL or existing-Gateway selection. (src/OpenClaw.SetupEngine/NativeGatewaySetupEligibility.cs:16, a6c5fb276f9f)
   • Native acquisition and session ownership: Current onboarding documentation describes native setup as the first choice, automatic Store acquisition through WinGet, resumable drafts, and package-owned isolated-session lifecycle. It explicitly preserves existing WSL installations and does not enter WSL migration or cleanup pipelines. The documented dependency boundary is the versioned packaging contract, not Companion-owned session provisioning. (docs/ONBOARDING_WIZARD.md:172, a6c5fb276f9f)
   • Isolated runtime integration and regression contracts: The package client requires isolated-session-v1 and a ready session from package-qualified setup. Runtime tests cover verified listener ownership, starting and stopping an owned service, preserving a pre-existing service on detach, and explicit restart without transferring detach ownership. These are inspected test contracts, not reviewer-executed proof. (tests/OpenClaw.Connection.Tests/IsolatedGatewayRuntimeTests.cs:496, a6c5fb276f9f)
   • Native management UI remains incomplete: Connection management controls are displayed only when CanControlWslGateway is true, and Start/Stop/Restart dispatch through the WSL controller. Open fix(settings): separate native and WSL gateway management #1623 (fix(settings): separate native and WSL gateway management) explicitly excludes the missing native lifecycle, terminal, and Doctor controls; it is a partial implementation candidate, not completion of this request. (src/OpenClaw.Tray.WinUI/Pages/ConnectionPage.xaml.cs:491, a6c5fb276f9f)
   • Merged implementation provenance: GitHub verifies feat(setup): guide native Gateway installation and onboarding #1447 (feat(setup): guide native Gateway installation and onboarding) merged at dba8121, and fix: Companion cannot onboard with an isolated Gateway #1553 (fix: Companion cannot onboard with an isolated Gateway) merged at 5abfabb on 2026-09-30. Blame ties the current isolated-session contract to the latter commit. This supersedes the earlier review's assertion that native session integration was entirely missing. (src/OpenClaw.Connection/NativeGateway/NativeGatewayPackageClient.cs:11, 5abfabb38e12)

   Likely related people:

   • Karen: Raw commit dba8121 adds src/OpenClaw.SetupEngine/NativeGatewaySetupEligibility.cs:16 relative to its recorded parents. This identifies author metadata, not feature responsibility or a PR merger. (role: source-line author; confidence: high; commits: dba81213371c; files: src/OpenClaw.SetupEngine/NativeGatewaySetupEligibility.cs)
   • Paul Campbell: Raw commit 5abfabb adds src/OpenClaw.Connection/NativeGateway/NativeGatewayPackageClient.cs:11 relative to its recorded parents. This identifies author metadata, not feature responsibility or a PR merger. (role: source-line author; confidence: high; commits: 5abfabb38e12; files: src/OpenClaw.Connection/NativeGateway/NativeGatewayPackageClient.cs)
   • samanthamsong: Suggested for follow-up; no historical authorship or introduction is verified. (role: unverified routing candidate; confidence: low)

   How this review workflow works

   • 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.
5. karkarl

   assigned

   msft-yiyang

   on Aug 26, 2026
6. samanthamsong commented on Sep 2, 2026

   

   samanthamsong

   on Sep 2, 2026

   Collaborator

   More actions

   @msft-yiyang We also want a skill so that the node understands that its gateway is running in a session.

   • any UI thats for updating or migrating to the gateway
7. samanthamsong

   added

   P0Emergency: data loss, security bypass, crash loop, or unusable core runtime.Emergency: data loss, security bypass, crash loop, or unusable core runtime.

   and removed

   P3Low-risk cleanup, docs, polish, ergonomics, or speculative feature.Low-risk cleanup, docs, polish, ergonomics, or speculative feature.

   on Sep 4, 2026
8. samanthamsong

   added this to the 9/30 MXC Release milestone on Sep 4, 2026
9. clawsweeper

   added

   P2Normal priority bug or improvement with limited blast radius.Normal priority bug or improvement with limited blast radius.

   impact:otherThis issue has meaningful maintainer-visible impact outside the owned taxonomy.This issue has meaningful maintainer-visible impact outside the owned taxonomy.

   and removed

   P0Emergency: data loss, security bypass, crash loop, or unusable core runtime.Emergency: data loss, security bypass, crash loop, or unusable core runtime.

   on Oct 3, 2026