Mission Control: the 3.0 cockpit ships from the MCP (rc1)
Pre-release
Pre-release
Agents Remember 3.0.0rc1 (pre-release)
The 3.0 arc, shipped: the working session is now an observable, steerable entity, and the mission-control browser dashboard is served directly from the MCP package — agents-remember dashboard starts the cockpit against your trusted settings. This release candidate spans everything since 2.9.3: the browser-dashboard substrate (#95), the post-landing task-system cleanup (#96), and the operations-integration series (#98). The rc tag means the cockpit surface is still settling toward the final 3.0.0 contract; the architecture beneath it is stable.
Highlights
- Mission-control cockpit (#2, #43): the Operations task tree with live lifecycle/phase/gate state, task-document reader, event river, engine room (provider health), hosted terminal chats — a near-read-only projection with durable gate responses, served by the MCP package and launchable via CLI.
- Observable session lifecycle: append-only
ar-observer-event/v1logs with trust provenance, ambient lifecycle signals (lifecycle_*tools), a pure projection reducer, durable approval gates, and NOTIFY-AND-CONTINUE turn ends. - Inspect–diff–converse integration (#98): File Viewer (Headless Tree + CodeMirror dual-pane), Change-Set Viewer (merge diffs with series / committed / working leaf views and master accumulation), and leaf-keyed sidebar chats — task highlights route straight into the adjacent leaf chat as a draft, never auto-submitted.
task_reopen: reopening a completed leaf reuses its exact leaf id — contract and doc reset to planning,worktree_startrecreates fresh off the current tips and restamps the doc's lifecycle. No more suffixed reopen forks;worktree_abandonends its anchored lifecycle and abandoned enclosures project terminal state.- Task documents are master/leaf-only (#96):
task_doccreate/replacerefusekind="light"and default kind context-awarely;remove_subtaskcompletes the CRUD; docs authored under a leaf contract are stamped with their lifecycle and enclosure refs. - Provider stability: every managed provider container is memory-capped (watchers 512m, falkordb/ollama 2g, runner 1g, postgres 512m) with self-recycling OOM behavior; the enriched
.cgcignore(defaults + repo.gitignore+ per-repo exclusions) now reaches the live CGC watch context; the committed dashboard bundle is excluded from watch/index work; a maintained CGC patch pops fired debounce timers (runner imagear2). - Hosted terminal hardening: wheel scrolling via tmux mouse mode (alternate-screen aware), boot-safe context paste with echo-confirmed retries, typing auto-exits copy-mode, and hosted chats can be reassigned between leaves with live catalog sync across open dashboards.
- Repo-wide quality gate: the pre-push hook (ruff + Pyright + full pytest + CRAP threshold) passes over the whole tree and gates every push.
Breaking and rc caveats
- Per the Stability promise this is the major bump that retires
kind="light"task-document authoring (existing light documents still load). - The cockpit's HTTP/SSE surface and dashboard internals may still change before 3.0.0 final.
Upgrade notes
- Pre-releases are skipped by
@latestresolvers: pin explicitly —uvx agents-remember-mcp==3.0.0rc1 --config <settings.json>for the MCP server. - Dashboard from the CLI:
uvx --from agents-remember-mcp==3.0.0rc1 agents-remember dashboard --config <settings.json>.