Compass 1.1.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 is about trusting the Session page while a session is still writing.

• The numbers on a session's entries stop moving. A message keeps its number (#41) for the whole session, and a check or file is numbered by the message it follows (#41.2), so a correction that names "entry #41.2 in Compass's activity list" still points at the same entry after a check re-runs or you press Show more. An open page also keeps the entries it showed as the session keeps writing, instead of losing some when large tool output pushed them out of the recent tail. See #625 and #626.
• The Drift card is easier to read. A press's answer is one short line with an info mark instead of a sentence that pushed the buttons around, what a reading sends is a labelled list behind "What is sent", and the entries "Show cited entries" marks are tinted so they stand out. See #627.
• A Claude Code reading can be allowed to see checks at launch. Start the dashboard with --allow-tool-output, or set COMPASS_ALLOW_TOOL_OUTPUT=1, and the first press asks only for the words. It grants nothing else, and --no-observer-model refuses it. See #616.
• A few smaller corrections: a written path is read from the session's own folder, a direction lookup is retried when the session wrote through it, and a correction names the entry it cites. See #617, #623 and #619.

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

No new harness, no new route and no change to the Python version Compass needs. Numbering is fixed for Claude Code sessions whose own context has loaded; other harnesses still count what the page holds. What each answer stops at is in the promise map.

What's Changed

• Run the release archive upload from the checkout by @gcko in #612
• feat(release): stamp the released version onto the marketplace listing by @gcko in #613
• chore: retire the React cutover receipts and their tooling by @gcko in #614
• chore: prune a shipped plan, a stale plan and the operator-cockpit probe by @gcko in #615
• Grant tool output at launch with --allow-tool-output by @gcko in #616
• Read a written path from the session's folder, not each record's by @gcko in #617
• Pin what the Intent and drift journey launches and sends, by test by @gcko in #618
• Say what a reading can settle, and name the entry in a correction by @gcko in #619
• Prove each Intent and drift stage, harness limit and no-reader reason in Storybook by @gcko in #621
• Hold a copied correction to three presses and no model request by @gcko in #622
• Say a goal-less check adopts the first prompt, not the latest by @gcko in #620
• Retry a direction lookup the session wrote through, and say so when it still moves by @gcko in #623
• Correct the promise: a goal-less check drafts your first prompt by @gcko in #624
• Keep what a session page showed as the session keeps writing by @gcko in #625
• feat(activity): keep each entry's number fixed for the whole session by @gcko in #626
• fix(drift): keep a press's answer to one line, list what is sent, tint cited entries by @gcko in #627

Full Changelog: v1.0.0...v1.1.0