Bridge
Statuschecking
Modecontrol
SurfaceLifeOps
Overview
A separate LifeOps page for power users; Omni stays simple.
WebUI update available.
Authentication
Stored only in this browser's localStorage. Never sent in URLs.
Workload
Kanban tasks0
Active sessions0
Recent events0
Controls
Authenticate to load controls.
Recent Kanban
Recent events
Sessions
Kanban cockpit
Usage model
| Current | Bridge-local status, sessions, events, feature toggles, attachments, and Kanban summaries. |
|---|---|
| OpenClaw inspiration | Token/cost timelines, per-session exports, cache status, daily CSV/JSON, model/fallback accounting. |
| Tracked | Missing usage analytics are queued in Kanban so they can be accepted, deferred, or rejected deliberately. |
Events
Agents
Omnilive
Default user-facing LifeOps session.
Kanban workersboard
Durable specialist work routed through Hermes Kanban profiles.
OpenClaw sandboxtest-only
Reference UI/front desk only; no privileged LifeOps authority.
Skills & nodes parity
OpenClaw exposes agents, nodes, MCP/plugin areas, model settings, fallback state, memory, tool-call visibility, and logs as first-class cockpit screens. LifeOps currently exposes the pieces users most need: chat, features, attachments, approvals, events, and Kanban. The missing power-user surfaces are tracked as parity tasks.
Approvals
Live bridge behavioravailable
Dangerous command prompts render Approve/Deny controls inside chat when Hermes emits the approval payload.
Missing dedicated queuetracked
OpenClaw has approvals as a first-class control surface. LifeOps still needs a standalone approvals queue/history if we want that power-user workflow.
Files
Attachmentslive
Authenticated image/file send, receive, inline preview, and download are present in Web Command.
Workspace filestracked
OpenClaw has a broader files/workspace surface. LifeOps should decide whether a separate safe file browser is worth adding.
Theme options
Feature parity notes
Usage analytics/exportmissing
OpenClaw has timeline metrics, session/daily token and cost views, and CSV/JSON exports.
Dedicated approvals queuemissing
LifeOps approval controls exist in chat, but not as a separate queue/history screen.
Model, MCP, memory, tools, logs, workspace filesmissing
OpenClaw exposes these as control-plane screens. LifeOps should add only the ones that fit the trusted-backend model.