OpenClaw proposes a full-workspace machine view with explicit desktop takeover

OpenClaw opened a desktop-first Systems proposal on September 13, turning machine inspection into a workspace rather than a small panel competing with chat. The linked product request describes local gateways, workers and paired nodes as the intended inventory. The implementation reuses existing desktop ownership and control mechanisms instead of introducing a second remote-control service.

The proposed arrangement keeps global navigation stable while replacing the lower conversation list with machines. Selecting one opens its desktop at workspace size, alongside compact reported statistics and optional details. Returning to conversations restores their sidebar and scroll position. Existing customized navigation is not forcibly rearranged: users can add Systems through Edit pinned items.

The facts

- The Systems proposal was open and unmerged when inspected; its linked request is issue #147217. - Desktop access starts view-only and requires explicit user takeover before control. - Headless, offline and removed targets remain inspectable rather than disappearing from the workspace. - The shared URL contract reserves the Systems namespace against catalog-share route collisions. - The author reports 515 focused UI regressions, 63 route tests and 168 shared URL-contract tests passing. - An isolated AWS worker reportedly installed the built package and exercised a real Gateway and RFB desktop; the author explicitly says the team Gateway was not updated.

Why it matters

This is a product-direction story about intervention, not an announcement that OpenClaw has acquired a new permission. Operators moving work among machines need to see where they can inspect or take over without losing the conversation they were managing. Giving the desktop the main pane acknowledges that operating an agent sometimes means operating its environment. Keeping viewing separate from takeover also makes the authority transition visible rather than hiding it behind a connection button.

Current

Inspected on 2026-09-14. The OpenClaw stable-channel baseline is 2026.9.4 on npm latest; extended-stable 2026.6.35. The primary source was open (not merged) when captured. Mainline merges, open proposals and packaged releases are distinct availability states; the release baseline does not establish that a proposal has shipped.

Evidence

Primary evidence: openclaw/openclaw PR #147519 (https://github.com/openclaw/openclaw/pull/147519). Supporting context: openclaw/openclaw issue #147217 (https://github.com/openclaw/openclaw/issues/147217); OpenClaw — official product README (https://raw.githubusercontent.com/openclaw/openclaw/main/README.md). Public source bodies and linked documentation were inspected. Contributor test results remain attributed reports, not independently reproduced experiments.

Operator take

Evaluate the proposed interface with one online machine, one unavailable machine and a conversation that has been scrolled away from its latest message. Check that navigation preserves that state and that reconnecting never silently transfers control. Treat reported session bindings as inventory data: they can tell an operator what is attached, but cannot by themselves establish which machine executed a past action.

Caveat

This remains a proposal, not a packaged feature announcement. The build, install and capture results are contributor-reported evidence from a disposable worker, not tests independently repeated by illmethinks. No new backend permission, persistence schema or execution-history guarantee is claimed.