Compass 1.3.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 makes the Drift panel on the session page easier to read, after readers said the budget line, the "Not accurate?" control and the "What it read" panel were hard to follow. See #630.

• You can run up to 100 drift analyses in a rolling 24 hours, up from 12. The limit is still shared across sessions and providers, and the page no longer shows a running "N of M left today" count. Once the limit is spent, a banner holds the top of the session page, names the limit and says when you can analyze again, and the refusal under Analyze uses the same words. The background checks you can turn on with --unasked-readings keep their own cap of 12.
• "Not accurate?" is now "Mark as inaccurate", and it says what it does before you press it: the analysis stops setting the drift level and Steer back, and nothing is sent or re-run. After you press it, a status beside the control says what changed, the control becomes Undo, and the empty level slot says it is hidden because you marked the analysis inaccurate. The control stays where it was when the level and Steer back leave the column above it, so the page no longer jumps.
• "What it read" is now "What the analysis read", grouped under Model, Your intent, The session and Not read. Your intent shows its version, when it was saved, where it came from and each line quoted, with a note when the goal was cut at 240 characters. The sentence saying how much of the session was read is now plain sentences with the same counts, for example "Read all 4 entries after your intent: 1 from you, 3 messages from the agent. The oldest is from about 13h ago." Analyses stored before this release keep the sentence they were stored with.

Upgrading

Update the plugin and restart the dashboard. A dashboard that was already running keeps serving the old page until you do. Your saved intent, goals, permissions and stored analyses carry over, and there is no new flag to set. Analyses you already ran in the past 24 hours still count toward the new limit.

One thing to know: the higher limit means reader-requested analyses can spend more of your Claude Code or Codex capacity in a day than before. The limit is still enforced across tabs and processes, failed attempts still count, and --no-observer-model still refuses every model call.

What this release does not add

The analysis itself is unchanged: it reads the same evidence, reaches the same verdicts and sends the same words. 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

• Raise the drift analysis cap and make Mark as inaccurate and What the analysis read clearer by @gcko in #630

Full Changelog: v1.2.0...v1.3.0