Repository navigation
Compass 1.2.0
Run as many coding agents as you like. Compass tells you which ones need you, which ones are fine, and when it is safe to walk away. One local screen, every harness you use, and nothing leaves your machine that you cannot switch off.
What this release changes
This one lets a new reader see what Intent and drift does before they have a session of their own.
- A sample session you can open and look through. Above the Sessions list, "See a sample session (view only)" opens an anonymized Claude Code session that drifted from its goal. It shows the saved goal and two expected outcomes, a High drift level, a stored reading that names the entries it rests on, and the Steer back correction Compass composed from it. Seven numbered (i) marks say what each part is for, and the banner repeats them as text. It is a real session with a real stored reading, drawn by the same Session page every session gets, and nothing in it is saved, sent or run. See #629.
- A release no longer fails on a slow frontend suite that CI passed. The release workflow now gives that suite the same 6-minute limit CI does, and a test keeps the two equal. See #628.
Upgrading
Update the plugin and restart the dashboard. A dashboard that was already running keeps serving the old page until you do. Nothing about your saved intent, goals or permissions changes, and there is no new flag you have to set.
What this release does not add
The sample is one fixed session. It does not read your sessions, run a reading or reflect what Compass says about your own work, and its reading is a snapshot that does not change when the reading prompt does. There is no new harness, server route or flag, and no change to the Python version Compass needs. What each answer stops at is in the promise map.
What's Changed
- fix(release): give the release's frontend suite the limit CI gives it by @gcko in #628
- Add a view-only sample session that shows Intent and drift by @gcko in #629
Full Changelog: v1.1.0...v1.2.0