nexus/docs/audits/2026-07-28/openclaw-core-integration/ROUTE_EVALUATION.md

Nexus Core Route Evaluation

Stand: 2026-07-28 Bewertungsziel: Wie nah ist jede Seite an einer agent-first Mission Control, die tägliche OpenClaw-Bedienung ersetzt?

Zusammenfassung

The core route set is now coherent and functionally connected, but Nexus is not yet complete OpenClaw parity.

Dimension	Reife	Bewertung
Browser -> Nexus -> OpenClaw trust boundary	9/10	Correct architectural boundary; no provider secrets in the browser
Gateway protocol foundation	7/10	Protocol v4, states, scopes and reconnect exist; remote device pairing and live interop proof remain
Runtime visibility	8/10	Tasks, sessions, agents, approvals, cron, models and events are visible
Safe runtime mutations	5/10	Cancel, abort, model patch, approval and run-now work; lifecycle coverage is incomplete
Agent-first operator workflow	6/10	Iris, Run Control and contextual recovery work; start/resume/retry/artifacts are incomplete
Full daily OpenClaw replacement	4/10	Tools, config, nodes, channels, complete scheduler and recovery are still missing
Production proof	3/10	Contract/browser QA is green; credentialed OpenClaw/OpenAI E2E is not yet recorded

Overall: solid functional control-plane foundation, not yet a production claim of “OpenClaw is no longer needed for normal operation.”

Route-by-route evaluation

Route	Current functional state	OpenClaw integration	Highest-value next improvement
/login	Owner login, rotating refresh path and return-to-route work; overlapping refresh race fixed	Indirect: protects every facade route	Add passkeys/2FA, device/session management and explicit recovery
/dashboard	Live orchestration dominates the workspace; Iris chat is an on-demand modal; model change works	Agents, sessions, tasks, activity, Gateway health and chat are real Nexus-facade data	Add streaming chat, stop/retry, live usage/cost and run-start intent
/runs	Functional work graph, inspector, tasks, sessions, approvals, cron and recent activity	Strongest integrated surface; cancel, abort, approve/deny and run-now are wired	Add start/resume/retry/branch, durable run deep links, tool trace and artifact output
/agents	Runtime inventory with status, model and workspace-safe metadata	Live agents.list plus session state	Add create/import, enable/disable, restart, capability/tool policy and drift
/agents/:id	Agent identity, activity and config workspace render; dashboard model selection patches a session	Live agents, sessions, activity and sessions.patch	Add session explorer, lifecycle controls, tools, budget, effective permissions and evals
/projects	Functional Nexus portfolio and create flow	Shared connection/recovery context; project remains correctly Nexus-owned	Correlate active OpenClaw runs, agents, approvals, usage and artifacts per project
/projects/:id	Project detail, progress and task list work	Same explicit runtime boundary	Add “delegate to Iris”, run start, project automation, budget and artifact timeline
/tasks	Parent/child task board works and opens real details; horizontal board scrolling is intentional	Shared OpenClaw status and Run Control handoff	Persist task <-> session/run correlation and add retry/resume/cancel at the task
/tasks/:id	Detail, children, activity and task mutations work	Runtime boundary is visible, but the Nexus task remains the domain record	Add linked session/run, approvals, tool calls, artifacts and replay
/memory	Search, list, selected-file and empty states work	Connection/recovery is explicit; data remains Nexus/workspace-owned	Add OpenClaw ingestion status, scope, provenance, freshness, retention and retrieval evals
/docs	Category/search/list/reader and empty states work	Same safe boundary as Memory	Add upload/import, versioning, citations, sync status and approval
/models	Live catalog, provider filter, availability reasons and detail dialog work	Direct typed models.list; no hardcoded UI catalog	Add OpenAI auth-profile status, primary/alias/fallback policy, limits, budgets and test run
/activity	Search, type/source filters and event details work	OpenClaw runtime events and Nexus events share one surface	Add durable correlation ID, actor/diff, pagination, export, retention and trace links
/calendar	Live schedule list, next/last run and owner-confirmed run-now work	cron.list and admin-scoped cron.run	Add create/edit/enable/pause/delete, timezone editor, run history, retry and delivery
/security	Real Nexus JWT settings and OpenClaw trust/pairing boundary are visible	Connection, version and trust posture are no longer invented	Add effective scope/policy audit, 2FA/passkeys, sessions/devices, secret rotation and remediation
/incidents	Incident list/detail selection and Run Control recovery link work	Runtime status is visible; incident content remains Nexus-owned	Add create/ack/assign/escalate/resolve, event correlation, remediation and postmortem
/notifications	Unread state, target routing, mark-read and mark-all work; OpenClaw approvals are summarized	Live approval queue is visible	Add inline decision, snooze, quiet hours, preference routing and incident actions
/settings	Profile/password/users plus read-only Gateway diagnostics work	Endpoint, version, protocol, scopes and recovery are visible without secrets	Add paired-device setup, validated config forms, provider policy and controlled reload/rollback

The old /chat page is intentionally removed. Iris is a contextual modal on the dashboard and a global entry links to that real destination.

Capability gaps that still force OpenClaw or break-glass access

P0

• paired device identity for remote/container Gateway access;
• one real OpenAI-over-OpenClaw E2E proof with negative auth and reconnect;
• start, resume, retry and durable deep link for a run/session;
• durable Nexus task/project <-> OpenClaw run/session correlation;
• audit/correlation/idempotency for every privileged mutation.

P1

• agent lifecycle and effective tool permissions;
• model/auth-profile/fallback/budget policy editing;
• complete cron CRUD and history;
• tool/approval trace and artifacts;
• incident lifecycle and recovery actions;
• knowledge ingestion, provenance and retrieval evaluation.

P2

• channels, connectors and node inventory/pairing;
• config schema forms, diff, backup, reload and rollback;
• provider usage/cost/latency dashboards;
• eval datasets, regression gates, export and retention.

Recommendation

Do not broaden the navigation again yet. The highest-value next slice is one real, durable run:

Iris intent
  -> create/start OpenClaw run
  -> correlate Nexus project/task
  -> observe session and tool events
  -> owner approval
  -> artifact/result
  -> stop/retry/reload recovery

That single path will close more of the “return to OpenClaw” gap than adding more read-only pages.