With this, your mind can give members one place to start an agent, return to ongoing work, inspect contexts and manage integrations. The Dash is a page in the mind’s config, not a separate service with a second copy of its data. Its member socket can reach the whole mind, so this is a privileged control panel rather than a public status page.
Start with work, keep the raw view nearby
apps/dash/public/app.js imports Dash and its panels from @iterate-com/ui. A single pages list defines their names, icons, order and components. Home now starts with the agent composer; Agents is an embedded panel, not only a link to another host. The sidebar lists recently active agents above the panels, and command search prefers agents unless a member asks for a raw context path. Contexts remains available for inspecting the durable log beneath a conversation.
const pages = [
{ id: "home", name: "Home", component: DashHome },
{ id: "agents", name: "Agents", component: DashAgents },
{ id: "contexts", name: "Contexts", component: DashContexts }
];
// Other panels can be added as rows with their own components.
The URL names the selection: ?page=<id> chooses a panel and ?agent=<path> opens a conversation. Components receive the member connection and page context, including the catalog’s agents. Keep these as navigation state rather than trusting query parameters to grant access. Larger panels load when first needed; the home composer need not load every repository or analytics view.
Keep host authority on the server
apps/dash/app.ts serves index.html, public/, the shared theme and shared live-reload files. worker.ts first applies this.auth.require(request); then host.auth.memberPage(request) handles the member socket and shell endpoints. The page uses memberItx() and mindOfHost() from the UI kit. A signed-in-person guard is not sufficient: an ordinary signed-in visitor is not necessarily a member.
Only explicitly allowlisted icons and app manifests bypass the member guard. Preserve that small exception without exposing chat actions, repo contents or the socket. Pin the browser package, React entry points and styles together in the import map. The dashboard itself needs no new vendor account or credential.
Integrations reflect the vault
The Integrations panel reads the integrations facet and secret inventory, not a browser-maintained list. cloud-accounts.ts keeps connected accounts and available connection actions aligned with the real vault. A guarded /connect/<app> route begins OAuth through the configured iterate Cloud, using cloud-scopes.ts. The vault shows the member the proposed secret and permitted destinations before consent; tokens never pass through page JavaScript. Reconnecting can replace only a secret for that app, not an arbitrary secret named in a link. Connection failures return an explicit error.
Link to observations, not guesses
For a computer pane whose captured Claude or Codex conversation is known, public/native-navigation.js can offer a link to that conversation. It matches the observed provider, session and computer against an existing catalog row, and removes the link when newer observations invalidate it. The label deliberately says “last identified”: a historical capture is not proof of the pane’s current session. This is local navigation, not permission to control another computer.
Rebuild and verify
Copy the host, assets and navigation helper, mount behind member authentication, and supply a tested UI-kit version with the home and agent-kind components. Existing integrations need their own accounts; OAuth buttons require a configured Cloud client. Keep passkey, session and membership management on platform pages instead of copying credential forms. Test direct socket requests by nonmembers, unknown panel ids, agent deep links, disconnected sessions and stale pane observations. Check narrow and desktop navigation and a first opening of onboarding. Agents describes the separate workbench; Docs describes repo editing.