Open-source AI teammates in Slack, Teams, Discord, Telegram and Mattermost. Self-host it, with any agent harness and any model.
Python agent-orchestrationaiai-agentschatopsdiscordlangchainmcpmicrosoft-teamsmulti-agentopen-sourceopenaiself-hostedslack
Scrub internal references now the repo is public (CHOO-2023) (#201)
Louis Amaudruzfc3e595ea1af
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex aa2e957a9..a961a6c8e 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -7,7 +7,7 @@ and this project aims to adhere to [Semantic Versioning](https://semver.org/specSwitch ships several independently-versioned artifacts, each with its ownsection below. Every artifact carries three-part semver (`MAJOR.MINOR.PATCH`)-and a changelog, without exception (CHOO-1865).+and a changelog, without exception.A version says **where an artifact is** — which release you are running. It saysnothing about what that release can talk to. Compatibility is carried separately@@ -56,7 +56,7 @@ version of their own to them without also giving them a release of their own.#### Added- The Discord collaboration bridge registers native slash commands (`/…`) thatmap onto the same in-room command dispatcher as typed `!` commands, giving- Discord the interaction surface Slack already had (CHOO-1879). One+ Discord the interaction surface Slack already had. Oneimplementation, two entry points: a slash invocation is reassembled into thesame positional `@token` string the `!` handlers already parse. Argument shapescome from a new shared `Command.args_spec` in the command registry — validated@@ -68,18 +68,18 @@ version of their own to them without also giving them a release of their own.#### Changed- **Breaking (agent-facing):** `read_context` returns`{threads, truncated, oldest_timestamp}` rather than a bare list of thread- groups, and every entry carries a `kind` (CHOO-2034). Both connector skills+ groups, and every entry carries a `kind`. Both connector skillsare updated.#### Fixed- `read_context` seeks to a `before` window via the homeserver's`timestamp_to_event` rather than paging over everything newer to reach it,and falls back to a scan with its own page budget when the server cannot- answer (CHOO-2034). Previously the walk shared the read budget, so a window+ answer. Previously the walk shared the read budget, so a windowdeep in a busy room returned empty however small a `limit` was asked for.- `read_context` now pages the homeserver instead of reading a single`/messages` page, so agents see the whole room rather than the last slice of- it (CHOO-2034). `before` pages backwards into older history rather than+ it. `before` pages backwards into older history rather thanfiltering one page, and the response reports `truncated` and`oldest_timestamp` so a shortened read can never pass as a complete one. Roomjoins now appear in the timeline as `kind: "room_join"` entries. The@@ -87,27 +87,27 @@ version of their own to them without also giving them a release of their own.flat message list when it has always been thread groups and so returned noevents at all, is fixed with it.- Discord no longer silently drops outbound messages over its 2,000-character- limit (CHOO-1879). Both send paths caught the 400, logged it, and returned+ limit. Both send paths caught the 400, logged it, and returned`None`, so the message never reached the channel; text is now split on line (orword) boundaries, reopening a fenced code block across the break so a torn fencedoesn't render the remainder as plain text. `help`, at 2,063 characters, hadbeen failing to post as `!help` for as long as the command list has been thislong.- The "no agents in this channel" notice now gives each platform its own invite- syntax instead of one Slack-shaped `/invite-agent @agent-name` line (CHOO-1879).+ syntax instead of one Slack-shaped `/invite-agent @agent-name` line.Discord names the argument as a field (`/invite-agent agent:agent-name`), andMattermost and Teams — which register no slash commands — no longer point at acommand that does not exist.- Outbound `@name` mentions on the Slack bridge resolve to real `<@U…>` mentionsfrom the `external_users` table, primed at startup and topped up as puppets are- created (CHOO-1781). The name→id map was previously filled only as a side effect+ created. The name→id map was previously filled only as a side effectof resolving an inbound sender, so it was empty after every restart and whethera person was actually notified depended on whether they happened to have postedsince — otherwise the mention went out as plain text. Matching is nowcase-insensitive, and app/bot rows, whose `B…` id cannot form a valid usermention, are skipped.- The first message from a channel member the room does not yet know is no longer- dropped (CHOO-1781). Provisioning the sender's puppet only *invited* it; the+ dropped. Provisioning the sender's puppet only *invited* it; thejoin landed asynchronously from the puppet's own sync loop while the triggeringmessage was relayed immediately, and a send issued before the join is rejectedby the homeserver — a failure that was then swallowed.@@ -121,7 +121,7 @@ version of their own to them without also giving them a release of their own.#### Added- Cross-artifact version compatibility, part 1 — every artifact declares what it- is and what it speaks (CHOO-1865). `artifacts.yaml` is the one authored+ is and what it speaks. `artifacts.yaml` is the one authoredregistry of contract revisions; per-language modules are generated from it andCI fails if they are stale or hand-edited. switch-core reads its own releaseversion, discloses it and its ranges on authenticated surfaces only (the@@ -131,25 +131,25 @@ version of their own to them without also giving them a release of their own.declares nothing connects exactly as before.- The authentication surface is now **frozen**: never versioned, permanentlybackward-compatible, and excluded from `gateway-api`, so a client can always- authenticate far enough to be told what is wrong (CHOO-1865).+ authenticate far enough to be told what is wrong.#### Fixed- The agent-protocol check no longer defaults a silent client to the server's ownversion. It defaulted to agreement, and since no shipped client ever sent`?protocol=`, the check had never once fired. Absent now records as unknown —- and still connects (CHOO-1865).+ and still connects.- A protocol refusal names which side is behind. It always said "update theSwitch agent runtime", which for a client ahead of the server sent the user to- downgrade the side that was already right (CHOO-1865).+ downgrade the side that was already right.- The compatibility check is a range overlap rather than exact equality. The two- numbers are equal today, so nothing changes yet (CHOO-1865).+ numbers are equal today, so nothing changes yet.- `SWITCH_VERSION` is required by the standalone compose instead of defaulting to`latest`, which silently floated the whole stack to whatever had most recently- been published (CHOO-1865).+ been published.- The Helm chart no longer claims a version it has not been at for months. The- real one is stamped at package time; the file now says `0.0.0-dev` (CHOO-1865).+ real one is stamped at package time; the file now says `0.0.0-dev`.- Refreshed the stale switch-core version in `uv.lock`, which the release- procedure never re-locked (CHOO-1865).+ procedure never re-locked.#### Security- Bump core Python dependencies (cryptography, aiohttp, starlette, mcp,@@ -159,13 +159,13 @@ version of their own to them without also giving them a release of their own.#### Added- Collaboration bridges expose a workspace/home deeplink so a client can open- the messaging app's workspace from the gateway (CHOO-1784).+ the messaging app's workspace from the gateway.#### Security- Admin-gate every collaboration-bridge write: updating and deleting a bridgewere ungated, so any authenticated user could toggle agent greetings or deletea bridge (which cascades into deleting every room on it) — now admin-only- (CHOO-1784).+.### [0.12.2] - 2026-08-07@@ -175,13 +175,13 @@ version of their own to them without also giving them a release of their own.to (instead of staying where the turn opened), and the agent — not the bridgewatching traffic — decides when it moves (new `anchor_event_id` on theruntime-state protocol), so it no longer jumps below a human's message before- the agent has been handed it (CHOO-1104).+ the agent has been handed it.#### Fixed- Runtime-indicator robustness: serialise refresh vs repositioning, and don't- strand the indicator when a turn ends mid-move (CHOO-1104).+ strand the indicator when a turn ends mid-move.- Discord: delete an agent's messages through the same webhook that posted them- (CHOO-1104).+.- Agent bridge: clamp a resumed cursor to the in-memory buffer head on heartbeat,so a connection no longer silently skips events up to a stale cursor after aswitch-core restart.@@ -192,33 +192,32 @@ version of their own to them without also giving them a release of their own.### [0.12.1] - 2026-08-05#### Security-- Retire the unauthenticated `/collab` bridge-admin API (CHOO-1251, H5, #120).-- Re-scan and bump dependency CVEs (CHOO-1251, M5, #123).+- Retire the unauthenticated `/collab` bridge-admin API (#120).+- Re-scan and bump dependency CVEs (#123).- Local stacks are secure by default: published ports bind to `127.0.0.1`(`SWITCH_BIND_ADDR=0.0.0.0` is now an explicit opt-in for network exposure),`.env.example` ships every secret blank, and `just init-env` generates strong- random credentials — no more `admin/admin` reachable on `0.0.0.0` (CHOO-1251,- M1, #122).+ random credentials — no more `admin/admin` reachable on `0.0.0.0` (#122).#### Fixed- Enforce one session of an agent per room: `connect_to_room` now refuses withHTTP 409 when another session of the same agent already holds the room, and atakeover evicts and reports the displaced session — instead of silently- stranding a session in a room whose events go elsewhere (CHOO-1419, #109).+ stranding a session in a room whose events go elsewhere (#109).### [0.12.0] - 2026-08-04#### Added- Codex registered as its own gateway known-agent (connector_type "Codex") witha Codex-flavored "no live session" command, instead of falling back to Claude's- builder (CHOO-1436, #91).+ builder (#91).- `cancel_task` agent operation — a requester can abandon a task it delegated,recording the reason and notifying the room; served on both the MCP server and- the HTTP front door (CHOO-1436, #79).+ the HTTP front door (#79).#### Changed- `list_participants` now includes each participant's `status` and `alias` (both- null when unset) (CHOO-1436, #79).+ null when unset) (#79).### [0.11.0] - 2026-08-03@@ -230,7 +229,7 @@ version of their own to them without also giving them a release of their own.union of heartbeat and live connection, and connection status is derived fromwhat a connection observes rather than a declared `connection_model`. Backwardcompatible — polling keeps working and old/new state are read together- (CHOO-1857, #100).+ (#100).### [0.10.0] - 2026-07-30@@ -239,7 +238,7 @@ version of their own to them without also giving them a release of their own.directions across Slack, Mattermost, and Discord. Non-image files are relayedinstead of silently dropped, multi-file messages are coalesced into a singleplatform post, and the 20MB size cap is now enforced inbound too; oversize or- failed files are disclosed in the room rather than dropped (CHOO-1802, #93).+ failed files are disclosed in the room rather than dropped (#93).### [0.9.0] - 2026-07-29@@ -247,36 +246,36 @@ version of their own to them without also giving them a release of their own.- Every room now gets a collaboration bridge by default: a bridge can be markeddefault and is used when a room names none, with `internal_only` as theexplicit opt-out; a bundled Mattermost is provisioned across compose and Helm- (CHOO-1674, #84).+ (#84).#### Changed- Restyle the Switch Gateway web UI onto the Hoot design system — new light/darktheme, icon-rail shell, and consistent formatting conventions; nav- destinations unchanged (CHOO-1782, #87).+ destinations unchanged (#87).### [0.8.1] - 2026-07-24#### Fixed- Prevent a duplicate Switch room from being created when provisioning a Slack- channel (race on bridge channel provisioning) (CHOO-1660).+ channel (race on bridge channel provisioning).### [0.8.0] - 2026-07-24#### Added- Scoped agent-addressing permissions — control which agents and rooms an agent- may address, enforced server-side (CHOO-1585).+ may address, enforced server-side.### [0.7.0] - 2026-07-24#### Added- Microsoft Teams collaboration bridge — rooms can bridge to Teams channels,- joining Slack, Mattermost, and Discord as supported platforms (CHOO-1281).+ joining Slack, Mattermost, and Discord as supported platforms.- Discord bridge polish: deeplink redirect, room icon, and outbound image relay- (CHOO-1588).+.#### Changed- Relicensed to Apache-2.0 + Commons Clause, with a CLA gate for contributions- (CHOO-1251).+.#### Fixed- Detach dependent rooms before removing a bridge, so bridge removal no longer@@ -286,14 +285,14 @@ version of their own to them without also giving them a release of their own.#### Added- Discord collaboration bridge — rooms can bridge to Discord channels, joining- Slack and Mattermost as supported platforms (CHOO-1365).+ Slack and Mattermost as supported platforms.### [0.5.0] - 2026-07-20#### Added- New `POST /gateway/auth/refresh` endpoint: re-mints the `switch_auth` cookiefrom a still-valid session, enabling clients (switchdash) to silently renew- sessions before the 24h expiry (CHOO-1435).+ sessions before the 24h expiry.- Standalone compose: bind address and host ports are configurable via envvars (`SWITCH_BIND_ADDR`, `POSTGRES_HOST_PORT`, `API_HOST_PORT`, …) —consumed by switchdash's local-server mode.@@ -304,13 +303,13 @@ version of their own to them without also giving them a release of their own.- The standalone Docker Compose file is published to GHCR as a versioned OCIartifact (`standalone-compose:<version>`, plus `latest`) on every release,pinned to the same version as the images and chart — switchdash's- local-server mode consumes it (CHOO-1428).+ local-server mode consumes it.### [0.3.0] - 2026-07-17#### Added- Agents can send images from rooms, relayed out through the Slack and- Mattermost collaboration bridges (CHOO-1396).+ Mattermost collaboration bridges.### [0.2.1]@@ -340,7 +339,7 @@ version of their own to them without also giving them a release of their own.#### Changed- Distribution endpoints (electron-updater target, plugin-marketplace source,image registry/namespace) centralized so the eventual public-repo move- (CHOO-1260) is a configuration flip.+ is a configuration flip.- Initial internal version. History predating the changelog lives in the git log.@@ -381,7 +380,7 @@ version of their own to them without also giving them a release of their own.app-secrets store), fetched only on expand so the secret does not cross into therenderer for everyone who opens the page. When a value cannot be read the cardnames which one is missing rather than showing a placeholder that could be- mistaken for a real password (CHOO-1787).+ mistaken for a real password.- A per-host cap on how many remote terminals stay attached at once(`remote.maxAttachedSessionsPerHost`, default 4), exposed as an Interfacesetting. Beyond the cap the least-recently-viewed session on that host is@@ -398,7 +397,7 @@ version of their own to them without also giving them a release of their own.`switchdash://` scheme, npm packages, `SWITCHDASH_*` env vars) so an existinginstall updates in place rather than being stranded. The source tree moved from`dash/` to `console/` and the release tag prefix is now `switch-console-v*`- (CHOO-2008).+.- Local-server mode now bundles and pulls **switch-core `0.13.0`** (was`0.12.3`): the app's bundle pin / `COMPATIBLE_SWITCH_VERSION` is raised so amanaged local stack runs the current core release.@@ -414,7 +413,7 @@ version of their own to them without also giving them a release of their own.are unaffected because they come from hook events and the session poll, not froma PTY.- Search no longer returns filesystem results, and the per-location file indexer- behind them is removed (CHOO-2009). File hits were appended after the relevance+ behind them is removed. File hits were appended after the relevancecut and the 30-item slice, so up to 20 irrelevant rows survived regardless ofranking; the row navigated to the session, not a file. Removing search's onlyreader of the index also drops the crawl it ran on every location and the@@ -438,29 +437,29 @@ version of their own to them without also giving them a release of their own.at. Room state was loaded and reported across every server at once while thesidebar only ever shows one, so a healthy selected server could be buried underwarnings about unrelated ones. Room state is now scoped to the server on screen- (cross-server search still loads every server, but only when opened) (CHOO-1943).+ (cross-server search still loads every server, but only when opened).- The sidebar no longer presents unknown room state as fact. A server that couldnot be read kept its last-known rooms with no hint they were stale; a room whosename had not loaded showed a short id styled like a name; an agent whosemembership lookup failed vanished from its rooms. These are now discloseddistinctly ("asked and failed" vs "not connected, never asked"), an unloaded namerenders as provisional, and a retry is offered. A room's member count, list and- invite picker are now one read so they can't disagree (CHOO-1943).+ invite picker are now one read so they can't disagree.- A server you are not signed into now prompts you to sign in instead of reporting"couldn't reach" it with a Retry that cannot work. Signed-out, dormant, andgenuinely-unreachable are now distinguished, and only a real failure offersRetry. Agent names are also read from the local database instead of fetchedper-row from the gateway, which could silently render a plausible wrong name on- failure (CHOO-1943).+ failure.- Selecting a session, agent or room from outside the sidebar (keyboard, commandpalette, notifications, menu, modals, deep links, or the view restored atstartup) now scrolls the highlighted row into view, expanding whatever grouphides it. Previously only the deeplink handler scrolled, and only for sessionrows. It scrolls only when the row is off-screen, never while dragging, and keys- on the selection so a reorder can't yank the viewport (CHOO-2010).+ on the selection so a reorder can't yank the viewport.- The per-room channel icon, the room pane's "Open in …" button and the Slackbridge card's Open button now open bridged channels even without the native- desktop app installed (CHOO-2043). They handed the OS a native+ desktop app installed. They handed the OS a native`mattermost://` / `slack://` deeplink, which nothing answers when no desktop appis registered, so the click did nothing. Links are now translated to thechannel's web address, which works either way. Opens now also report a failure@@ -468,7 +467,7 @@ version of their own to them without also giving them a release of their own.- The bundled chat's sign-in prompt no longer offers to sign in "on your phone".The managed stack publishes onto `127.0.0.1` and the URL shown is a `localhost`one, which no other device can reach, so it now says "on this computer"- (CHOO-1787).+.- The server page no longer sits on _"Checking sign-in options…"_ forever afterconnectivity returns. Which login methods a server offers was read once whenthe page mounted, and a read that failed was never retried, so a blip left the@@ -476,7 +475,7 @@ version of their own to them without also giving them a release of their own.on the signals connection status already used — the page's Refresh button,returning to the app window, and a remote host becoming reachable again. TheRefresh button in particular re-checked only the connection status, so the one- control a user would reach for did nothing visible (CHOO-2042).+ control a user would reach for did nothing visible.- A server whose gateway cannot be reached now says so in one line and retrieson its own, instead of stacking three surfaces that each described the samefailure differently: a red banner quoting a raw internal error@@ -484,24 +483,24 @@ version of their own to them without also giving them a release of their own."Not signed in" row, and a sign-in panel that claimed to be checking optionsit would never receive. There is nothing to sign into while the gateway isdown, so the sign-in form no longer appears at all. The underlying error goes- to the console (CHOO-2042).+ to the console.- The sidebar no longer offers "Sign in" on a server it cannot reach, which wasan action that could not work. Unreachable is now modelled apart fromsigned-out, so the rooms list also stops reporting an unreachable server asmerely needing sign-in. A server whose data is unavailable shows a red dotrather than amber, for both causes: neither is a transitional state- (CHOO-2042).+.- A directory that already holds agents for one Switch server can now onboard itsagents to another. "Already onboarded" was judged per directory rather than perserver, so every candidate was filtered out as a duplicate and the modal offeredan empty list — of agents that existed, on a server that did not have them- (CHOO-2044).+.- The sidebar no longer draws a directory's agents under a server they do notbelong to. A directory resolved to a single server — whichever of its agents wasreturned first — and then every agent in it was rendered under that one, soonboarding a single agent to a second server appeared to drag the rest acrosswith it. Nothing had been onboarded; each agent is now drawn under its own- server, and a shared directory shows under all of them (CHOO-2044).+ server, and a shared directory shows under all of them.- Onboarding an agent whose credentials belong to **another** Switch server nolonger overwrites those credentials. The import path looked the existingidentity up on the target server, did not find it, and fell back to minting a@@ -509,27 +508,27 @@ version of their own to them without also giving them a release of their own.silently breaking the agent the other server was still running. It now refusesand names the server the identity belongs to. Such agents are listed in theAdd Agent modal but not selectable, with the reason shown; a plain definition- carrying no Switch identity is still adopted as before (CHOO-2044).+ carrying no Switch identity is still adopted as before.- The Add Agent modal no longer offers a permanently disabled button over a listit will not submit. A directory carrying another server's leftover`.claude/settings.local.json` took the detected-agent branch, verified thatforeign agent against the current server, failed, and disabled the only buttonon screen — with the onboardable agents listed above it. The onboard action nowtakes precedence, and a detected agent belonging to another server says so- (CHOO-2044).+.- The Add Agent modal no longer shows the create form, or the existing-agentslist, before an agent type is picked. Both depend on the type — it decideswhich agents can be brought in and how a new one runs — so the form asked for aname, a description and a config, then ended at a button that could not bepressed. Everything below the directory now waits for the type, and the modal- asks for it instead (CHOO-2044).+ asks for it instead.### [0.19.3] - 2026-08-09#### Added- Declares its `sidecar-control` range in the sidecar's ready file, and readsback whatever a running sidecar declares. A sidecar that declares nothing- records as unknown, never as agreement (CHOO-1865).+ records as unknown, never as agreement.#### Fixed- A gateway call to a managed server whose stack is **stopped** now fails with@@ -537,23 +536,23 @@ version of their own to them without also giving them a release of their own.`Could not reach http://localhost:<port>` — a local address that was neverthe problem. It is logged as the modeled state it is rather than as an RPCerror, and the proactive session renewal no longer warns about the same- absence a second time (CHOO-1780).+ absence a second time.- A managed server whose deployed switch-core version **cannot be read** is nowsurfaced as such, in the banner and the sidebar. It previously reported "nodrift" — the identical result a healthy, in-step stack gives — so a failed- probe rendered as a green server and the user was told nothing (CHOO-1865).+ probe rendered as a green server and the user was told nothing.- Starting a stack whose version cannot be compared to this build's pin now saysso loudly. It passed in complete silence, in the same branch as a clean match,- while carrying the same risk as a downgrade (CHOO-1865).+ while carrying the same risk as a downgrade.- CI verifies the bundled standalone compose is in step with the repo's copy.Nothing checked before — the two could drift with only a comment askingnicely, which is how the sync script once silently stopped running- (CHOO-1865).+.- The host-unreachable panel now also shows on a location that mounted while itshost was up, not only one that never mounted. Such a location stayed `ready`and kept every control live over a dead SSH transport — the sidebar showed thetrouble icon, the main pane did not; it restores itself when the host returns- (CHOO-1682).+.#### Security- Bump bundled dependencies for two advisories — DOMPurify `SAFE_FOR_TEMPLATES`@@ -565,26 +564,26 @@ version of their own to them without also giving them a release of their own.#### Added- Connect a messaging app (Slack/Mattermost/Discord/Teams) to a server fromwithin switchdash — per-platform setup-guide links and a Teams icon; open a- messaging app's workspace from the server page (CHOO-1784).+ messaging app's workspace from the server page.#### Changed- New macOS app icon (max.tam's mark); a dark mark for non-release (canary/dev)- channels; dropped the leftover emdash DMG art/wordmark (CHOO-2004).+ channels; dropped the leftover emdash DMG art/wordmark.- Bump the bundled switch-core for local managed servers to `0.12.3`(`COMPATIBLE_SWITCH_VERSION`).#### Fixed-- Restore sidebar drag-to-reorder for agents and rooms (CHOO-2007).+- Restore sidebar drag-to-reorder for agents and rooms.- Set `GATEWAY_PUBLIC_URL` so "Open in SwitchDash" links work; redact thecredential key names configs actually use; vendor the real Teams logo- (CHOO-1784).+.### [0.19.1] - 2026-08-07#### Changed- switchdash sessions report their latest-message anchor so thecollaboration-bridge runtime indicator can follow the agent to the foot of the- conversation (CHOO-1104).+ conversation.- Bump the bundled switch-core for local managed servers to `0.12.2`(`COMPATIBLE_SWITCH_VERSION`), so a fresh local stack pulls the latestswitch-core and existing stacks flag the drift for a one-click update.@@ -592,7 +591,7 @@ version of their own to them without also giving them a release of their own.#### Fixed- Fix an import cycle that could leave the view registry half-built — a renderercrash ("Cannot access 'remoteHostsView' before initialization"), deterministic- in CI and load-order-dependent locally (CHOO-1104).+ in CI and load-order-dependent locally.### [0.19.0] - 2026-08-07@@ -600,22 +599,22 @@ version of their own to them without also giving them a release of their own.- Remote-host onboarding rewritten as per-host pages with a staged,one-click-per-prerequisite setup: install each prerequisite individually withlive progress, inline GitHub CLI sign-in, and agent creation gated on host- readiness (CHOO-1809).+ readiness.- Surface and act on available updates on a remote host — detect Codex/CLIupdates remotely, re-check one dependency at a time, and show which version an- update brings, flagged in the sidebar (CHOO-1809).+ update brings, flagged in the sidebar.- Discover and onboard already-configured agents on a shared remote host- (CHOO-1937, #130).+ (#130).- Detect switch-core drift on a managed stack and update it; flag drift on the- sidebar server rows (CHOO-1736).+ sidebar server rows.- Command palette now searches across your agents and rooms — not justnavigation — labelling what each result is, jumping into another server's- scope, and adding an "Add Switch Server" command (CHOO-1423, #140).+ scope, and adding an "Add Switch Server" command (#140).#### Changed- Split an agent type into separate CLI and connector rows; drop the- servers-sidebar text actions (CHOO-1809, CHOO-1953).-- Pin switch-core `0.12.1` for the managed stack (CHOO-1736).+ servers-sidebar text actions.+- Pin switch-core `0.12.1` for the managed stack.#### Fixed- Remote-host setup hardening: a host without the GitHub CLI no longer reports@@ -624,15 +623,15 @@ version of their own to them without also giving them a release of their own.longer treated as a broken dependency; only CLI updates switchdash canactually perform are offered; agent creation refuses an unchecked type; theagent type clears when the run location changes; remote-host pages scroll; and- a remote install no longer hangs on an unanswerable prompt (CHOO-1809).+ a remote install no longer hangs on an unanswerable prompt.- Dialogs opt out of the window drag region; the alert action no longer overlaps- its text (CHOO-1953, CHOO-1736).+ its text.- Migration safety: register migration 0046 in the drizzle journal, fail loudwhen a migration isn't registered, and assert the migration runner's timestamp- precondition (CHOO-1809).+ precondition.- Command-palette matching: a hyphenated query is no longer split into separateterms, matches no longer land mid-word, results rank like the sidebar, and the- search index no longer treats `item_type` as content (CHOO-1423, #140).+ search index no longer treats `item_type` as content (#140).### [0.18.3] - 2026-08-06@@ -644,7 +643,7 @@ version of their own to them without also giving them a release of their own.skill but none of the tools it describes. The plugin also auto-approves theSwitch tools, which no `approval_policy` setting could do: measured againstcodex-cli 0.146.0, that setting does not govern MCP tool calls at all- (CHOO-1935).+.⚠️ Codex upgrades a plugin only when a user clicks Update in Settings andcaches each version separately, so an install still on an older connector has@@ -654,10 +653,10 @@ version of their own to them without also giving them a release of their own.- Bypass permissions is applied to sessions again: the toggle is stored on theagent but every launch read a copy frozen into the session at creation, sochanging it never affected an existing session — on restart or resume — while- the settings copy promised the opposite (CHOO-1935).+ the settings copy promised the opposite.- Codex runtime status reports tool calls ("Running tool …") instead of sittingon "Working on it…" for a whole turn; no tool hook was registered for Codex,- so nothing could ever produce an activity update (CHOO-1935).+ so nothing could ever produce an activity update.- In-app release links resolve again: the sidebar update indicator and theSettings Update card pointed at `.../releases/tag/v<version>`, which is not areal tag (the app is tagged `switch-console-v<version>`), so the user hit a 404;@@ -668,7 +667,7 @@ version of their own to them without also giving them a release of their own.#### Changed- The per-agent Codex profile carries only model, reasoning effort andinstructions. An agent that sets none of them no longer gets a profile at all- (CHOO-1935).+.### [0.18.2] - 2026-08-05@@ -677,7 +676,7 @@ version of their own to them without also giving them a release of their own.server takes away (or refuses with HTTP 409 because another session of theagent holds it) is now reported as roomless and is not reconnected under aroom it no longer attends — the remote-session reconciler and sidecar no- longer strand two sessions in one room (CHOO-1419, #109).+ longer strand two sessions in one room (#109).### [0.18.1] - 2026-08-05@@ -687,7 +686,7 @@ version of their own to them without also giving them a release of their own.#### Fixed- A session's Switch connection id is now derived deterministically, so asupervisor/sidecar restart no longer strands a remote session with a stale- connection id (CHOO-1931, #125).+ connection id (#125).### [0.18.0] - 2026-08-04@@ -699,14 +698,14 @@ version of their own to them without also giving them a release of their own.approval (validated — an unknown value fails rather than silently widening thesandbox); a Codex agent defaults to a `codex.<repo>.<user>` identity; andswitchdash registers the Switch MCP runtime for Codex itself via a per-agent- Codex profile (CHOO-1436, #91, #79).+ Codex profile (#91, #79).#### Fixed- Codex session correctness: per-agent Switch credentials are written to disk forproviders without repo-agents (so Codex sessions actually receive `SWITCH_*`);Codex room tracking follows `connect_to_room` mid-session; and Codex hookpayloads post correctly (local Codex sessions had been posting empty bodies to- a portless URL) (CHOO-1436, #79).+ a portless URL) (#79).### [0.17.2] - 2026-08-04@@ -716,28 +715,28 @@ version of their own to them without also giving them a release of their own.downloading, a restart prompt once ready, and a warning tint on failure — andopens a panel (current → new version, the right action, a link to the GitHubrelease) instead of just jumping to Settings. User-triggered failures are- toasted and the real error message is shown (CHOO-1434, #107).+ toasted and the real error message is shown (#107).#### Fixed- The onboarding/home page can drag the window again: the empty home surface isnow a drag region (action buttons opted out), so the window is no longer stuck- when Home is the active view (CHOO-1430, #106).+ when Home is the active view (#106).### [0.17.1] - 2026-08-04#### Added- Linux x64 desktop builds are shipped again (AppImage, deb, rpm), with a stabledesktop-entry name so the launcher, icon and pinning behave; INSTALL docs and- release notes now cover Linux (CHOO-1905, #104).+ release notes now cover Linux (#104).#### Changed- Release builds macOS and Linux artifacts in parallel (the GitHub Release is- created in its own job), cutting ~5 minutes off a release (CHOO-1905, #104).+ created in its own job), cutting ~5 minutes off a release (#104).#### Fixed- A dropped-events "gap" no longer wakes an agent and spends a turn: switchdashdefers the warning onto the next event it was already going to surface, instead- of injecting an addressed prompt (CHOO-1906, #105).+ of injecting an addressed prompt (#105).### [0.17.0] - 2026-08-04@@ -745,18 +744,18 @@ version of their own to them without also giving them a release of their own.- In-app Switch room creation: create a room from switchdash (name, description,messaging app, agents, optional instructions) instead of the operator web app —the picker offers only running bridges and every created room is bridged- (CHOO-1875, #103).+ (#103).- Room-centric sidebar: a room tree listing rooms by membership and ownership(not only rooms with a live session), showing each room's members, managingmembership (add/remove agents), starting a session in a room with the agentpre-chosen, and opening the room in its messaging app when the gateway supplies- a deeplink; rooms sort and filter on their own properties (CHOO-1875, #103).+ a deeplink; rooms sort and filter on their own properties (#103).#### Fixed- Sessions launched for a room now declare that room when their connection opens— both sidebar-started and auto-spawned (messaging-app-addressed) sessionsappear under the correct room immediately instead of sitting under- "Unassigned" until the agent calls `connect_to_room` (CHOO-1875, #103).+ "Unassigned" until the agent calls `connect_to_room` (#103).### [0.16.1] - 2026-08-03@@ -764,17 +763,17 @@ version of their own to them without also giving them a release of their own.- Local GitHub-auth detection in Switch setup: a requirement row reporting `gh`missing / not logged in / missing `read:packages`, with an inline device-flowlogin that requests the scope. Sessions that can't fetch the runtime now toast- the reason instead of starting silently broken (CHOO-1873, #102).+ the reason instead of starting silently broken (#102).#### Fixed- GitHub auth changes now take effect without restarting: the updater no longerleaves a boot-time token in `GH_TOKEN` (which shadowed the keyring for `gh`),and the scope check judges the active account only (`gh auth status --active`)- rather than any known account (CHOO-1873, #102).+ rather than any known account (#102).- A dialog's own terminal now receives keystrokes (the `gh auth` prompt wassilenced inside the Agent Settings modal); agent usage — not just install — isgated on GitHub access; managed servers pinned to switch-core `0.11.0` (was- `0.8.1`) (CHOO-1873, #102).+ `0.8.1`) (#102).### [0.16.0] - 2026-08-03@@ -783,11 +782,11 @@ version of their own to them without also giving them a release of their own.shared connection per session claims its room server-side instead of scrapingit from a hook, backed by the new `@sandbox-quantum/switch-agent-runtime`shared protocol client used by both switchdash and the connector plugin- (CHOO-1857, #100).+ (#100).#### Removed- First-run welcome page and residual Emdash artwork; first run now lands on the- existing home empty state with an "Add Switch agent" action (CHOO-1398, #96).+ existing home empty state with an "Add Switch agent" action (#96).### [0.15.3] - 2026-07-31@@ -808,7 +807,7 @@ version of their own to them without also giving them a release of their own.the local log) so local logs are debuggable while exported logs stay as safeas before; on-demand sidecar log capture folded into bug reports; andboot/exit + enumerated error markers to pinpoint crashes and launch failures- (CHOO-1683, #83).+ (#83).#### Fixed- Stop a destroyed managed server's agents from polling forever: resetting a@@ -816,7 +815,7 @@ version of their own to them without also giving them a release of their own.the main process), room connections are keyed per session with`ON DELETE CASCADE` so orphaned entries are unrepresentable, and the bootsweep refuses to restore sessions for orphaned agents instead of hammering a- dead endpoint (CHOO-1802 follow-up, #95).+ dead endpoint (#95).### [0.15.1] - 2026-07-30@@ -824,7 +823,7 @@ version of their own to them without also giving them a release of their own.- Surface non-image attachments to dash-managed sessions: switchdash's ownsession-notification builder now downloads and annotates any file type (notjust images) and names failed downloads, so agents running under switchdash- are actually told about files posted in a room (CHOO-1802, #94).+ are actually told about files posted in a room (#94).### [0.15.0] - 2026-07-29@@ -832,13 +831,13 @@ version of their own to them without also giving them a release of their own.- Built-in chat: switchdash renders each room's default bridge conversationinline (Mattermost) with per-room embed resolution, a chromeless guest view,theming, and link/deeplink routing; Slack rooms get a deeplink and agent-only- rooms a stated reason (CHOO-1674, #84).+ rooms a stated reason (#84).#### Fixed- Gate remote managed servers on host reachability, so an unreachable host nolonger shows a stale green "Running" card or a spinning sign-in — the serverpage shows a "host unreachable" state and disables actions until it recovers- (CHOO-1780, #85).+ (#85).### [0.14.3] - 2026-07-28@@ -847,7 +846,7 @@ version of their own to them without also giving them a release of their own.switchdash stops the unbounded reconnect/reconcile retries against anunreachable host (one bounded backoff probe per host), persists the stateacross restarts, and surfaces a clear "host unreachable — work paused" panel- with a global Retry instead of raw SSH errors (CHOO-1682, #82).+ with a global Retry instead of raw SSH errors (#82).### [0.14.2] - 2026-07-28@@ -860,59 +859,59 @@ version of their own to them without also giving them a release of their own.#### Fixed- Reap sidecars orphaned when their tmux session name changes across upgrades,- instead of leaving duplicates running for the same agent directory (CHOO-1425).+ instead of leaving duplicates running for the same agent directory.### [0.14.0] - 2026-07-27#### Added- Remote sidecar now persists durable state and versioning, so running sessions- survive sidecar restarts, upgrades, and token rotation (CHOO-1425).+ survive sidecar restarts, upgrades, and token rotation.#### Fixed- Client no longer deletes healthy sessions when it briefly can't reach thesidecar; fixes cross-build kill loops and deaf clients after a sidecar restart- (CHOO-1425).+.### [0.13.1] - 2026-07-26#### Fixed- Fix slow boot caused by the agent-storage migration, and restore sessions that- vanished after the 0.13.0 upgrade (CHOO-1440 follow-up).+ vanished after the 0.13.0 upgrade.### [0.13.0] - 2026-07-26#### Changed- Removed the subagent concept — agents are now flat and repository-defined;- existing subagents migrate forward automatically on first launch (CHOO-1440).+ existing subagents migrate forward automatically on first launch.#### Fixed- Honor the bypass-permissions toggle for remote agents and clear a stale- session guard (CHOO-1664).-- Skip the connection-status probe for a stopped managed server (CHOO-1657).+ session guard.+- Skip the connection-status probe for a stopped managed server.### [0.12.0] - 2026-07-24#### Added-- Configure per-agent addressing policy from the app and gateway (CHOO-1585).+- Configure per-agent addressing policy from the app and gateway.#### Fixed- Data-entry modals no longer dismiss on outside-click, so in-progress input- isn't lost (CHOO-1659).+ isn't lost.### [0.11.4] - 2026-07-24#### Added-- Reset a remote agent — kill and reset all of its tmux sessions (CHOO-1656).+- Reset a remote agent — kill and reset all of its tmux sessions.### [0.11.3] - 2026-07-24#### Changed-- Sidebar and session UX polish (CHOO-1644).+- Sidebar and session UX polish.### [0.11.2] - 2026-07-24#### Added-- Delete and rename connected Switch servers (CHOO-1486).+- Delete and rename connected Switch servers.- Per-agent bypass-permissions setting — defaults off, on for remote agents(#57).@@ -920,58 +919,58 @@ version of their own to them without also giving them a release of their own.#### Added- Agent delete now tears down its credentials and optionally deletes the agent- from Switch (CHOO-1364).-- Agent error indicator with a retry button (CHOO-1639).+ from Switch.+- Agent error indicator with a retry button.#### Changed- Discord bridge polish: deeplink redirect, room icon, and outbound image relay- (CHOO-1588).+.- Relicensed to Apache-2.0 + Commons Clause, with a CLA gate for contributions- (CHOO-1251).+.### [0.11.0] - 2026-07-20#### Added- Managed Switch servers can now run on a remote host over SSH — the appprovisions the Docker stack remotely, with port-forwarded access, alongside- the existing local mode (CHOO-1432).+ the existing local mode.### [0.10.1] - 2026-07-20#### Added- Silent session token refresh — sessions renew before the 24h expiry insteadof bouncing to sign-in; the managed local server is always-signed-in, and- its gateway web page opens pre-authenticated in-app (CHOO-1435).+ its gateway web page opens pre-authenticated in-app.- Editing a server's API URL cascades to its member agents' configs- (CHOO-1431).+.#### Fixed- Remote sessions recover their room connection after an app restart or- machine sleep (CHOO-1417).+ machine sleep.### [0.10.0] - 2026-07-20#### Added- Local-server mode: run a managed Switch stack via Docker straight from theapp — pulls the versioned standalone compose artifact, provisions- env/secrets/ports, and monitors health (CHOO-1428).+ env/secrets/ports, and monitors health.#### Fixed- Injected prompts are always bracketed-pasted, so prompts containing @ no- longer swallow the submit (CHOO-1395).+ longer swallow the submit.### [0.9.2] - 2026-07-19#### Added-- Sidebar agents are labelled by their registered Switch name (CHOO-1082).+- Sidebar agents are labelled by their registered Switch name.### [0.9.1] - 2026-07-19#### Changed- Replaced the workspace/project abstraction with first-class Locations —- agents attach directly to a location (working directory) (CHOO-1426).+ agents attach directly to a location (working directory).- Collapsed sessions to a single conversation each and simplified- session/conversation management throughout (CHOO-1424).+ session/conversation management throughout.Existing databases migrate forward automatically on first launch (schemamigrations 0031–0036, including a locations backfill).@@ -979,16 +978,16 @@ migrations 0031–0036, including a locations backfill).### [0.9.0] - 2026-07-17#### Added-- Newly created subagents default to auto-session on (CHOO-1397).+- Newly created subagents default to auto-session on.#### Removed- Removed the telemetry/analytics stack entirely — the app ships no trackingor phone-home behavior.#### Fixed-- tmux mouse scroll works again (set-option target parsing) (CHOO-1403).+- tmux mouse scroll works again (set-option target parsing).- Switch setup re-points stale plugin-marketplace sources after the repo move- and surfaces failed refreshes instead of silently skipping (CHOO-1405).+ and surfaces failed refreshes instead of silently skipping.### [0.8.8] - 2026-07-15@@ -1019,10 +1018,10 @@ The Switch protocol client and MCP runtimenothing on disk — anyone, inside or outside SandboxAQ, can run the connectorplugins. GitHub Packages required a `read:packages` token even for publicpackages, which `gh auth login` does not grant, so external consumers hit a- 404 naming neither the registry nor the missing credential (CHOO-2021).+ 404 naming neither the registry nor the missing credential.- Publishing now authenticates by **npm trusted publishing (OIDC)** and runs inthe `release` environment, so a pushed tag queues the publish for approval;- builds carry `--provenance` and no npm token is stored (CHOO-2021).+ builds carry `--provenance` and no npm token is stored.The package name (`switch-agent-runtime`) and the runtime's behavior areunchanged — only where and under what scope it ships. Version `0.2.x` was@@ -1034,37 +1033,37 @@ skipped to `0.3.0` by request.- Resolves its own Switch identity and credentials from the local agent store(`./.switch/agents/`), not only from the environment — so a connector-pluginsession that is handed the server but no identity can start standalone instead- of exiting before the handshake (CHOO-1962).+ of exiting before the handshake.- `select_agent` tool: when the store names several agents on one server,identity is left open and `select_agent` binds it; the event stream and- heartbeat start on bind rather than at boot (CHOO-1962).+ heartbeat start on bind rather than at boot.- Degraded startup: on a resolution failure — no credentials, an ambiguousmulti-server store, or an unreachable Switch — the runtime starts anyway andserves a single `switch_unavailable` tool whose result is the diagnostic,- instead of vanishing so Switch tools read as silently missing (CHOO-1962).+ instead of vanishing so Switch tools read as silently missing.#### Changed- An unexpanded `${SWITCH_*}` placeholder now counts as absent rather than as avalue, so a Claude connector session falls through to the store instead ofdying on its own placeholder. Half a set of vars still refuses to start- (CHOO-1962).+.### [0.1.6] - 2026-08-09#### Added- Declares its `agent-protocol` range, artifact name and release version on theevent stream it already opens, so switch-core can record what is connecting- (CHOO-1865).+.- Logs the server's declaration from the `connection_state` frame, so whichversions were actually talking to each other is answerable from a bug report- rather than a guess (CHOO-1865).+ rather than a guess.#### Changed- Reports a failing event stream on a curve — first failure, then powers oftwo, plus a line when it recovers — instead of once per reconnect. Thereconnect itself is unchanged; only the reporting is rationed, so a stackthat is simply stopped costs a handful of log lines rather than one per- session per 30s, forever (CHOO-1780).+ session per 30s, forever.### [0.1.5]@@ -1092,7 +1091,7 @@ by Switch Console rather than published on its own.#### Added- Declares its `sidecar-control` range in the ready file switchdash already- reads (CHOO-1865).+ reads.#### Changed- Three-part semver: `1.7` becomes `1.8.0`. **The major stays at 1** — every@@ -1100,10 +1099,10 @@ by Switch Console rather than published on its own.two parts, so `1.7` and `1.8.0` order correctly and neither sidereplaces the other. `2.0.0` would have every existing install treat thissidecar as incompatible and replace it while a newer install replaces it back- (CHOO-1937, CHOO-1865).+.- The version no longer carries compatibility. It says which release is running;what the sidecar can speak is the `sidecar-control` range it now declares in- its ready file (CHOO-1865).+ its ready file.- The version is declared in `artifacts.yaml` and generated into the code.Nothing else declares it — the sidecar is deployed by switchdash rather thanpublished, so it has no packaging file of its own.@@ -1132,7 +1131,7 @@ compatibility signal. History for those is in the git log.installs re-download.- Skill: document `read_context`'s new response shape — `truncated` /`oldest_timestamp` and the per-entry `kind` — and tell the agent not to- conclude anything from a truncated read (CHOO-2034).+ conclude anything from a truncated read.#### Removed- Dropped the bundled `configure` skill as part of removing the private-repo /@@ -1143,7 +1142,7 @@ compatibility signal. History for those is in the git log.#### Changed- Bump the pinned `@sandbox-quantum/switch-agent-runtime` to `0.1.6`, so sessionspick up its rationed stream-failure reporting and version declaration- (CHOO-1780, CHOO-1865). The plugin version bumps with the pin so installs+. The plugin version bumps with the pin so installsre-download it.### [0.7.8]@@ -1170,13 +1169,12 @@ manifest history.`env_vars` in `.mcp.json` — `npx` no longer needs a GitHub token now that theruntime is on public npmjs (CHOO-2023).- Skill updated for `read_context`'s new response shape — `truncated` /- `oldest_timestamp` and the per-entry `kind` (CHOO-2034).+ `oldest_timestamp` and the per-entry `kind`.### [0.2.1] - 2026-08-09#### Changed-- Bump the pinned `@sandbox-quantum/switch-agent-runtime` to `0.1.6` (CHOO-1780,- CHOO-1865). The plugin version bumps with the pin so installs re-download it.+- Bump the pinned `@sandbox-quantum/switch-agent-runtime` to `0.1.6`. The plugin version bumps with the pin so installs re-download it.### [0.2.0]diff --git a/CLAUDE.md b/CLAUDE.mdindex e1a211bb4..65e6536bb 100644--- a/CLAUDE.md+++ b/CLAUDE.md@@ -2,6 +2,24 @@This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.+## This repository is public++Everything you write here is world-readable, permanently, including in git+history — a later commit cannot take it back. Keep internal detail out of it:++- **No credentials or tokens**, not even expired or "test" ones, and not in+ fixtures. A secret committed here is a secret to rotate, not to delete.+- **No internal infrastructure**: hostnames, IPs, cluster or account names,+ bucket names, ARNs, internal URLs. Test fixtures use obvious placeholders.+- **No personal data**: individual email addresses, Slack ids, employee names.+ Prefer a role address to a person's.+- **Keep internal tooling in `internal/`**, which is untracked and stays that+ way. Do not reference internal-only systems from tracked files.+- **Ticket keys** (`CHOO-…`) are fine in source comments and design notes as+ traceability, but write so the comment stands on its own without the ticket —+ a reader outside the company cannot open it. Keep them out of user-facing+ docs and the changelog.+## Project OverviewSwitch is an AI agent orchestration and governance platform. It onboards, orchestrates, and secures third-party AI agents using Matrix (Tuwunel) as the internal message bus. Agents register via the Agent Bridge API and communicate through Matrix rooms with room-scoped protection, observability, and collaboration bridges to external platforms (Slack, Mattermost).diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.mdnew file mode 100644index 000000000..64abe10be--- /dev/null+++ b/CODE_OF_CONDUCT.md@@ -0,0 +1,131 @@+# Contributor Covenant Code of Conduct++## Our Pledge++We as members, contributors, and leaders pledge to make participation in our+community a harassment-free experience for everyone, regardless of age, body+size, visible or invisible disability, ethnicity, sex characteristics, gender+identity and expression, level of experience, education, socio-economic status,+nationality, personal appearance, race, caste, color, religion, or sexual+identity and orientation.++We pledge to act and interact in ways that contribute to an open, welcoming,+diverse, inclusive, and healthy community.++## Our Standards++Examples of behavior that contributes to a positive environment for our+community include:++- Demonstrating empathy and kindness toward other people+- Being respectful of differing opinions, viewpoints, and experiences+- Giving and gracefully accepting constructive feedback+- Accepting responsibility and apologizing to those affected by our mistakes,+ and learning from the experience+- Focusing on what is best not just for us as individuals, but for the overall+ community++Examples of unacceptable behavior include:++- The use of sexualized language or imagery, and sexual attention or advances of+ any kind+- Trolling, insulting or derogatory comments, and personal or political attacks+- Public or private harassment+- Publishing others' private information, such as a physical or email address,+ without their explicit permission+- Other conduct which could reasonably be considered inappropriate in a+ professional setting++## Enforcement Responsibilities++Community leaders are responsible for clarifying and enforcing our standards of+acceptable behavior and will take appropriate and fair corrective action in+response to any behavior that they deem inappropriate, threatening, offensive,+or harmful.++Community leaders have the right and responsibility to remove, edit, or reject+comments, commits, code, wiki edits, issues, and other contributions that are+not aligned to this Code of Conduct, and will communicate reasons for moderation+decisions when appropriate.++## Scope++This Code of Conduct applies within all community spaces, and also applies when+an individual is officially representing the community in public spaces.+Examples of representing our community include using an official email address,+posting via an official social media account, or acting as an appointed+representative at an online or offline event.++## Enforcement++Instances of abusive, harassing, or otherwise unacceptable behavior may be+reported to the community leaders responsible for enforcement at+**[email protected]**.++All complaints will be reviewed and investigated promptly and fairly. All+community leaders are obligated to respect the privacy and security of the+reporter of any incident.++Security vulnerabilities are **not** reported here — see [SECURITY.md](SECURITY.md).++## Enforcement Guidelines++Community leaders will follow these Community Impact Guidelines in determining+the consequences for any action they deem in violation of this Code of Conduct:++### 1. Correction++**Community Impact**: Use of inappropriate language or other behavior deemed+unprofessional or unwelcome in the community.++**Consequence**: A private, written warning from community leaders, providing+clarity around the nature of the violation and an explanation of why the+behavior was inappropriate. A public apology may be requested.++### 2. Warning++**Community Impact**: A violation through a single incident or series of+actions.++**Consequence**: A warning with consequences for continued behavior. No+interaction with the people involved, including unsolicited interaction with+those enforcing the Code of Conduct, for a specified period of time. This+includes avoiding interactions in community spaces as well as external channels+like social media. Violating these terms may lead to a temporary or permanent+ban.++### 3. Temporary Ban++**Community Impact**: A serious violation of community standards, including+sustained inappropriate behavior.++**Consequence**: A temporary ban from any sort of interaction or public+communication with the community for a specified period of time. No public or+private interaction with the people involved, including unsolicited interaction+with those enforcing the Code of Conduct, is allowed during this period.+Violating these terms may lead to a permanent ban.++### 4. Permanent Ban++**Community Impact**: Demonstrating a pattern of violation of community+standards, including sustained inappropriate behavior, harassment of an+individual, or aggression toward or disparagement of classes of individuals.++**Consequence**: A permanent ban from any sort of public interaction within the+community.++## Attribution++This Code of Conduct is adapted from the [Contributor Covenant][homepage],+version 2.1, available at+https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.++Community Impact Guidelines were inspired by+[Mozilla's code of conduct enforcement ladder][mozilla].++For answers to common questions about this code of conduct, see the FAQ at+https://www.contributor-covenant.org/faq. Translations are available at+https://www.contributor-covenant.org/translations.++[homepage]: https://www.contributor-covenant.org+[mozilla]: https://github.com/mozilla/inclusiondiff --git a/CONTRIBUTING.md b/CONTRIBUTING.mdindex c9c0dfc9f..0fb623725 100644--- a/CONTRIBUTING.md+++ b/CONTRIBUTING.md@@ -3,6 +3,10 @@Thanks for your interest in contributing! This guide covers what you need toget a change merged.+Participation is governed by our [Code of Conduct](CODE_OF_CONDUCT.md). To+report a security vulnerability, follow [SECURITY.md](SECURITY.md) rather than+opening an issue.+## Development setup```bashdiff --git a/README.md b/README.mdindex 817fba83e..c9084d1bc 100644--- a/README.md+++ b/README.md@@ -9,8 +9,7 @@**Create organizations where AI agents and humans work side by side.**[](LICENSE)-[](#)-[](#)+[](docs/)[](CONTRIBUTING.md)</div>@@ -206,3 +205,6 @@ derives substantially from it); all other Apache 2.0 grants are unchanged.## ContributingSee [CONTRIBUTING.md](CONTRIBUTING.md) for how to get a change merged.+Participation is governed by our [Code of Conduct](CODE_OF_CONDUCT.md), and+security vulnerabilities go through [SECURITY.md](SECURITY.md) rather than a+public issue.diff --git a/console/AGENTS.md b/console/AGENTS.mdindex 592bade3b..d0d295ba1 100644--- a/console/AGENTS.md+++ b/console/AGENTS.md@@ -1,5 +1,10 @@# Project Overview+**This repository is public.** Everything written here is world-readable and+permanent, git history included. See "This repository is public" in the root+`CLAUDE.md` for what that rules out — credentials, internal hostnames and+infrastructure names, personal addresses. It applies to test fixtures too.+Switch Console is a cross-platform, local-first Electron app for orchestrating multiple AIcoding agents in parallel. Each agent runs in its own session in its location's directory(there are no Git worktrees). An agent runs either locally or — when configured remote — on andiff --git a/console/docs/INSTALL.md b/console/docs/INSTALL.mdindex a376b9498..65599b08a 100644--- a/console/docs/INSTALL.md+++ b/console/docs/INSTALL.md@@ -72,7 +72,7 @@ Linux builds are **unsigned**. Pick the format your distro uses:> The app does not yet set a `desktopName`, so desktop environments may not> associate its windows with the installed `.desktop` entry (the icon can appear-> as a duplicate or generic entry in the taskbar). Tracked under CHOO-1905.+> as a duplicate or generic entry in the taskbar).## Updatingdiff --git a/docs/ARCHITECTURE.md b/docs/ARCHITECTURE.mdindex 6fb939cef..df8ed2ab4 100644--- a/docs/ARCHITECTURE.md+++ b/docs/ARCHITECTURE.md@@ -35,11 +35,15 @@ The backend is a single FastAPI service, assembled in[`core/switch_core/main.py`](../core/switch_core/main.py). The Agent Bridge app isthe root ASGI app; the MCP server, health check, and gateway are mounted onto it:-- `POST/GET /agents/...` — Agent Bridge HTTP API+- `POST/GET /agents/...` — Agent Bridge HTTP API, including the+ `/agents/{id}/ops` operation-dispatch surface- `/mcp` — MCP server (agent tool surface)- `/health` — health check+- `/version` — build and contract version+- `/deeplink/session` — public redirect into the desktop app's URL scheme- `/gateway` — gateway management API (backs the operator dashboard); includes- the admin-gated collaboration-bridge admin API (`/gateway/collaborations`)+ the collaboration-bridge admin API (`/gateway/collaborations`), where reads are+ open to any authenticated user and mutations are admin-only```mermaidflowchart LR@@ -84,6 +88,7 @@ flowchart LR| Component | Where | Responsibility ||-----------|-------|----------------|| Agent Bridge | `bridges/agent/` | Server-side entry point for agents: HTTP API + MCP server, event delivery, task protocol, mediation, moderation. |+| Server-side connectors | `bridges/agent/server_connectors/` | Switch-hosted connectors that drive an external agent host (e.g. OpenCode) from the server, rather than the agent connecting in. Registered by type at startup and managed via `/gateway/connectors`. || Collaboration bridges | `bridges/collaboration/` | Two-way relay between external chat platforms and Matrix rooms, via per-platform adapters and puppet clients. || Resource bridge | `bridges/resource/` | Handles resource + mediation requests (tool/model access, room-document load/CRUD) via the resource-manager client. || Matrix clients | `clients/` | One `matrix-nio` client per participant (agent, bridge, user) and per system actor (admin, resource manager). |@@ -129,6 +134,8 @@ The relational schema is defined in(external pointers, internal docs, and bundles), each with independentread/write visibility.- **CollaborationBridge** — configured external chat bridges.+- **ServerConnector** — a Switch-hosted connector driving an external agent host+ (e.g. OpenCode) from the server, rather than the agent connecting in.- **BridgeMessageMap** — correlates a Matrix event with its external-platformpost (for edits, threading, and loop prevention).- **Tool** / **Model** / **Skill** — capabilities attached to agents, consulted@@ -200,7 +207,9 @@ address it. With no policy an agent is open to any room participant (today'sbehaviour). When a policy is set and the sender is not permitted, `AgentClient`demotes the message to unaddressed room chatter and posts a one-shot reply to thesender; `delegate_task` (an explicit, tracked addressing vector) instead fails-loud with a `PermissionError`. Configured via `PUT /agents/{id}/addressing-policy`.+loud with a `PermissionError`. Configured via+`PUT /gateway/agents/{id}/addressing-policy` — a gateway route under cookie-JWT+auth with an owner-or-admin check, not an agent-facing one.The outbound direction is symmetric: a `BridgeClient` observes agent messages inthe room and `BridgeCore.handle_outbound_message` relays them back out under the@@ -238,9 +247,13 @@ agent's name/icon, preserving threads and attachments.registers a future per request; the `ResourceManagerClient`([`clients/resource_manager_client.py`](../core/switch_core/clients/resource_manager_client.py))evaluates the request (e.g. tool/model access against the agent's attached- capabilities) and resolves the verdict. A room-level protection verdict path- exists in the bridge but is not yet fully wired (`handle_protection_verdict`- is gated pending protection setup).+ capabilities) and resolves the verdict.+- **Room-level protection is stubbed, not wired.**+ `BridgeCore.handle_protection_verdict`+ ([`bridges/collaboration/bridge_core.py`](../core/switch_core/bridges/collaboration/bridge_core.py))+ has no callers — note it sits in the *collaboration* bridge, not this one.+ `Room.protection_config` is persisted and settable via+ `PUT /gateway/rooms/{id}/protection`, but nothing reads it yet.### 4.4 In-room commands@@ -250,6 +263,11 @@ in [`bridges/agent/commands.py`](../core/switch_core/bridges/agent/commands.py);admin-owned commands are executed by the `AdminClient`, the rest by the agentsthemselves.+On Discord the same registry is also published as native slash commands+([`bridges/collaboration/discord/slash.py`](../core/switch_core/bridges/collaboration/discord/slash.py)):+a slash invocation is reassembled into the positional form the `!` handlers+already parse, so both entry points reach one implementation.+### 4.5 Room provisioning & lifecycle`RoomService.create_room`@@ -271,10 +289,13 @@ Everything ingress-facing, and where to find it:| Entry point | Path / transport | Auth | Code ||-------------|------------------|------|------|| Agent Bridge API | `/agents/*` (HTTP) | Bearer (agent API key / registration token) | `bridges/agent/api/`, `auth.py` |+| Agent operations | `/agents/{id}/ops`, `/agents/{id}/ops/{operation}` | Bearer | `bridges/agent/api/operations.py`, `bridges/agent/operations/` || Agent event stream | `/agents/{id}/events` (SSE) | Bearer | `bridges/agent/protocol/stream.py`, `protocol/connections.py` |-| MCP server | `/mcp` (HTTP, FastMCP) | Bearer | `bridges/agent/mcp/server.py` |+| MCP server | `/mcp` (HTTP, FastMCP) | Bearer (agent API key, or an OIDC token when configured) | `bridges/agent/mcp/server.py` || Health | `/health` | public | `main.py` |-| Collaboration admin | `/gateway/collaborations` | cookie JWT + admin | `gateway/collaborations.py` |+| Version | `/version` | public | `bridges/agent/api/version_routes.py` |+| Session deeplink | `/deeplink/session` | public | `bridges/agent/deeplink.py` |+| Collaboration admin | `/gateway/collaborations` | cookie JWT (reads) / + admin (writes) | `gateway/collaborations.py` || Gateway API | `/gateway/*` | cookie JWT (`switch_auth`) | `gateway/app.py`, `gateway/auth.py` || Platform ingress | adapter transports (Slack/MM/Discord WebSocket; Teams HTTP :3978) | platform token / Teams JWT+HMAC | `bridges/collaboration/*/adapter.py` |@@ -291,7 +312,10 @@ Auth-bypass path prefixes for the Bearer middleware are enumerated in([`bridges/agent/auth.py`](../core/switch_core/bridges/agent/auth.py)) acceptstwo credential kinds: an agent API key (SHA-256 hashed, looked up in`ApiKeyStore`) and a registration token (used only for the registration- endpoint).+ endpoint). On `/mcp` only, and only when `OAUTH_ISSUER_URL` is configured, a+ third kind is accepted: an OIDC access token, resolved to an agent by the+ `oauth_client_id` matching its `azp`/`client_id` claim. That path is what the+ `/oauth` auth-bypass prefix serves.- **Gateway authentication** — cookie-based JWT([`gateway/auth.py`](../core/switch_core/gateway/auth.py)): passwords hashedwith bcrypt, a `switch_auth` HS256 cookie (`httponly`, `samesite=lax`),@@ -340,8 +364,11 @@ A quick index for navigation:| App assembly & startup | `core/switch_core/main.py` || Configuration | `core/switch_core/config.py` || Authorization policy | `core/switch_core/authz.py` |+| Scoped addressing policy | `core/switch_core/addressing.py` || Token encryption | `core/switch_core/crypto.py` || Agent Bridge (API, MCP, protocol, auth, commands) | `core/switch_core/bridges/agent/` |+| Agent operation registry | `core/switch_core/bridges/agent/operations/` |+| Server-side connectors | `core/switch_core/bridges/agent/server_connectors/` || Collaboration bridges (adapters, core, lifecycle) | `core/switch_core/bridges/collaboration/` || Resource bridge | `core/switch_core/bridges/resource/` || Matrix clients | `core/switch_core/clients/` |@@ -353,6 +380,8 @@ A quick index for navigation:| Gateway API (backend) | `core/switch_core/gateway/` || Operator dashboard (SPA) | `gateway/` (top level) || Desktop app | `console/` |+| Connector plugins (Claude Code, Codex) | `connectors/` |+| Deployment assets (Helm, Compose) | `deploy/` |---diff --git a/docs/api/AGENT_PROTOCOL.md b/docs/api/AGENT_PROTOCOL.mdindex c0c65c770..2dd03495d 100644--- a/docs/api/AGENT_PROTOCOL.md+++ b/docs/api/AGENT_PROTOCOL.md@@ -1,6 +1,13 @@# Agent Bridge Protocol-Status: **design, under review** (CHOO-1857)+Status: **Stages A and B implemented; Stage C outstanding** (CHOO-1857, closed)++This began as a design proposal and is now largely built. The connection model,+scope/filter/room slots, the heartbeat and state machine, the event envelope and+its payloads, the operations registry and both front doors all describe shipped+behaviour. What remains is Stage C — retiring `connection_model` — plus the+individual items still marked as proposed below. Trust a section that describes+current behaviour; check anything labelled *proposed*.This document specifies the protocol between an agent and Switch: how an agentconnects, what it receives, what it sends, and what happens when things break.@@ -11,9 +18,12 @@ authoritative spec for the connection model `ARCHITECTURE.md` §4.3 summarises.## 1. Why this changes-Four problems in the current model, all structural rather than incidental.+Four problems in the model this replaces, all structural rather than+incidental. Three are now fixed; the fourth is Stage C and still live.-**Two sources of truth for "which session is in which room."** `connect_to_room`+**Two sources of truth for "which session is in which room."** *(fixed —+`connect_to_room` claims the room on the caller's own connection.)*+`connect_to_room`is an MCP tool that writes a row keyed on the MCP transport session id, whileevents are fetched over an unrelated HTTP request that never mentions it. Thething that joined the room and the thing receiving that room's events are two@@ -22,22 +32,26 @@ other dies. Clients then keep their own copies — Switch Console persists asession→room map to SQLite, the remote reconciler mirrors it, the sidecar keepsa third — so the same fact is stored four times and reconciled nowhere.-**Events are held in memory and destroyed on read.** The event queue is a-per-agent, per-room `asyncio.Queue`. A poll *removes* what it returns, so only-one consumer can exist (hence `SWITCH_CHANNEL_DISABLE_POLL`, which Switch Console-sets to stop the connector stealing its events). Nothing survives a restart,-and there is no way to ask "what did I miss?" because no record is kept.--**Liveness is guessed from timestamps by every reader independently.** Three-heartbeat endpoints with three cadences and three TTLs exist because there are-three connection models. Each caller compares `last_seen_at` against a TTL at-read time; nobody owns the answer. There is no session-close signal at all, so-bindings linger until they expire.+**Events are held in memory and destroyed on read.** *(fixed — the buffer is+read, never drained, with a cursor per reader.)* The event queue was a+per-agent, per-room `asyncio.Queue`. A poll *removed* what it returned, so only+one consumer could exist (hence `SWITCH_CHANNEL_DISABLE_POLL`, which Switch+Console set to stop the connector stealing its events; the variable still+exists, repurposed — see below). Nothing survived a restart, and there was no+way to ask "what did I miss?" because no record was kept.++**Liveness is guessed from timestamps by every reader independently.** *(fixed —+`POST /connection/beat` owns the answer, and status computation takes the+connection registry.)* Three heartbeat endpoints with three cadences and three+TTLs existed because there were three connection models. Each caller compared+`last_seen_at` against a TTL at read time; nobody owned the answer. There was no+session-close signal at all, so bindings lingered until they expired.**Connection models leak agent implementation details into the server.**+*(still true — this is Stage C.)*`always_on` / `session_addressable` / `session_passive` / `auto_session` is-branched on in 22 places, but almost all of those reduce to "is there a live-connection, and what does it cover" — facts the server could observe rather+branched on throughout the server, but almost all of those reduce to "is there a+live connection, and what does it cover" — facts the server could observe ratherthan be told.### Non-goals@@ -47,8 +61,8 @@ than be told.memory). This design assumes one process and notes the seams where thatassumption is load-bearing.- Replacing MCP. MCP remains the agent's tool surface.-- AG-UI (CHOO-1685). This design should not make it harder to land; it does not- attempt it.+- AG-UI (CHOO-1685), which is being worked separately. This design should not+ make it harder to land; it does not attempt it.---@@ -100,9 +114,9 @@ selects *events within them*.A session uses `single` + `all` — it needs unaddressed traffic for context andfor missed-message counts. A daemon uses `all` + `addressed` — it is watching-for a reason to start a session, not following conversations. This replaces-the separate `/notifications` endpoint and collapses the two notification-builders (CHOO-1810) into one.+for a reason to start a session, not following conversations. This is what+makes the separate `/notifications` endpoint and the second notification builder+(CHOO-1810) removable — neither has actually been removed yet.### 2.4 Room slots@@ -119,9 +133,12 @@ builders (CHOO-1810) into one.Exactly one recipient per room at all times: no duplicate delivery, nocoordination needed for handoff in either direction.-This rule already exists — implemented client-side in-`auto-session-watcher.ts`, which skips a room when Switch Console's own map says a-session covers it. Moving it into the protocol is the split-brain fix.+This rule was originally implemented client-side in `auto-session-watcher.ts`,+which skipped a room when Switch Console's own map said a session covered it.+That move into the protocol has happened: the server answers the question by+never delivering the event, and the client keeps no copy of the fact. What+remains client-side is only a narrow spawn-in-flight guard over the live+connection map, which is deliberately not a persisted mirror.**Collision.** If a `single` connection tries to claim a room already claimedby a live connection of the same agent, the claim is **rejected** with an error@@ -194,8 +211,8 @@ increasing **sequence number**. Events are appended when produced and removedonly when confirmed or aged out — **never on read**.Delivery becomes a read, which makes it repeatable, resumable and verifiable.-It also permits more than one reader, which is what allows-`SWITCH_CHANNEL_DISABLE_POLL` to be deleted.+It also permits more than one reader, which removed the reason+`SWITCH_CHANNEL_DISABLE_POLL` existed (see §12 for what became of it).The buffer is **in memory** for the first implementation. Restart losesundelivered events — accepted, and made loud (§5.5). It sits behind a narrow@@ -423,7 +440,7 @@ data: {"type":"message","room_id":"…","bridge_id":"…","channel_type":"channe|---|---|---|| `type` | string | one of the types below || `room_id` | string | Switch room id |-| `room_name` | string | *new* — `all`-scope clients receive events for rooms they never explicitly connected to |+| `room_name` | string | *proposed, not implemented* — `all`-scope clients receive events for rooms they never explicitly connected to || `bridge_id` | string \| null | collaboration bridge, if any || `channel_type` | string \| null | `channel_public`, `channel_private`, `direct` || `payload` | object | per type |@@ -482,9 +499,9 @@ New, carried on the same stream:| type | payload | meaning ||---|---|---|-| `connection_state` | `connection_id`, `scope`, `filter`, `rooms`, `cursor`, `protocol`, `server`, `client` | first event on every stream |+| `connection_state` | `connection_id`, `agent_id`, `scope`, `filter`, `spawn_capable`, `rooms`, `cursor`, `protocol`, `heartbeat_interval_seconds`, `server`, `client` | first event on every stream || `subscription_changed` | `rooms`, `reason` | scope changed — including a room going dark because another connection claimed it |-| `gap` | `from_sequence`, `reason` | events were dropped; re-read context. Carried to the agent on the next surfaced event, not as a wake of its own (§4.2) |+| `gap` | `from_sequence`, `resumed_at`, `reason` | events were dropped; re-read context. Carried to the agent on the next surfaced event, not as a wake of its own (§4.2) || `evicted` | `reason` | this connection lost its slot or was taken over; it must stop acting |`gap` and `evicted` exist so that degradation is always visible. A client that@@ -658,37 +675,44 @@ in memory — nothing to transmit, leak or get wrong. The connection id neverappears in a prompt or a config file, and the process can refuse a tool callimmediately when its own stream is down.-**This is what ships now.** The runtime lives in the plugin at-`connectors/claude-code-plugin/runtime`. It holds the stream, serves the whole+**This is what ships now.** The runtime's source lives at+`console/packages/switch-agent-runtime`. It holds the stream, serves the wholeoperation surface over stdio, and turns each tool call into`POST /ops/{operation}` carrying its own connection id — so an agent nevertalks to Switch directly and correlation is structural.-**Distribution is not solved yet.** A marketplace installs a plugin from its-own subtree (`source: ./connectors/claude-code-plugin`), so the runtime has to-sit *inside* the plugin to be installed with it — a sibling directory is not-copied and the path dangles. With a second connector plugin that means a-second copy, which is the thing worth avoiding. The answer is to publish the-runtime as a package each plugin depends on (the launcher already runs an-install step, so this is a small change), and that should happen before the-Codex plugin ships rather than after.+**Distribution is solved.** The runtime is published to npmjs as+`@sandboxaq/switch-agent-runtime`, and each plugin's bundled `.mcp.json` runs it+via `npx`. There is no copy of the runtime inside either plugin subtree, so the+second connector plugin cost nothing to add — which is why the original plan of+one copy per plugin was abandoned before the Codex plugin shipped.The operation list is fetched from the server at startup rather than hardcoded,-so the tool surface is whatever the server actually offers. If that fetch-fails the runtime refuses to start: an empty tool surface would look like-"Switch has nothing to offer" rather than a broken connection.+so the tool surface is whatever the server actually offers. That surface is the+server's registry **plus** three tools the runtime serves itself:+`send_attachment`, `download_attachment`, and `select_agent` where the working+directory names more than one agent. If the fetch fails the runtime does not+refuse to start — it **degrades**, serving a single `switch_unavailable` tool+that reports why. Dying before the MCP handshake left the session with no+explanation at all, which is worse than an honest one-tool surface.Planned second mode off the same code: *daemon* (long-lived, `scope: all`,`spawn_capable`) alongside today's *session* mode (child of the agent,`scope: single`).-- **Claude Code** — plugin `.mcp.json` at the plugin root, `${CLAUDE_PLUGIN_ROOT}`- for the path, `${VAR}` expansion for endpoint and token.-- **Codex** — Codex expands neither, and a stdio server cannot be expressed on- argv the way an HTTP one can, so Switch Console writes a per-agent Codex profile- (`$CODEX_HOME/<slug>.config.toml`) registering the server and launches with- `--profile <slug>`. It controls the launch, so it can also inject per-session- credentials.+Both hosts now register the server the same way — from the plugin's own bundled+`.mcp.json`, running the published runtime over `npx`. Neither needs a path+placeholder or `${VAR}` expansion, because the runtime resolves its own+credentials from `.switch/agents/` in the working directory rather than being+handed them in the config. The remaining difference is what the *host* adds:++- **Claude Code** — nothing beyond the plugin; the bundled `.mcp.json` is the+ whole registration.+- **Codex** — Switch Console writes a per-agent Codex profile+ (`$CODEX_HOME/<slug>.config.toml`, launched with `--profile <slug>`) carrying+ model, reasoning effort and instructions. It registers **no** MCP server; the+ plugin does that. An agent that specializes none of those three gets no+ profile at all.### 9.2 Remote MCP (fallback)@@ -775,8 +799,13 @@ Two consequences, stated rather than hidden:resumes wherever the server's cursor sits. Left honestly broken; the fix isto migrate the client.-`SWITCH_CHANNEL_DISABLE_POLL` can be deleted as soon as reads are-non-destructive — before SSE exists.+`SWITCH_CHANNEL_DISABLE_POLL` was expected to be deletable once reads became+non-destructive. It was not deleted — it was **repurposed**, keeping the name+for compatibility. It no longer stops a second poll (there is no poll to steal);+it suppresses *notification surfacing* in the runtime, so a session whose events+Switch Console already delivers into the pane does not also receive them as MCP+notifications. Same variable, different problem: double delivery, not double+poll.Polling endpoints are removed in a later, separate release.@@ -867,16 +896,14 @@ three renews is unaffected and unaware.`AdminClient` and the bridge app — the Matrix clients are wired before thebridge, so the bridge could no longer own it.-5. Switch Console (`RoomConnection` → session-grained connection that repoints- rooms; daemon mode) and the sidecar, which reuses the same class verbatim —- `sidecar-runtime.ts` constructs `RoomConnection` directly, so the two migrate- together rather than separately. The `auto_session` watcher's- `/notifications` poll folds into an `all`-scope connection, and its three- heartbeat loops collapse into one beat.+5. *(implemented)* Switch Console (`RoomConnection` → session-grained connection+ that repoints rooms; daemon mode) and the sidecar, which reuses the same+ class verbatim — `sidecar-runtime.ts` constructs `RoomConnection` directly,+ so the two migrated together rather than separately. The `auto_session`+ watcher's `/notifications` poll folded into an `all`-scope connection, and+ its three heartbeat loops collapsed into one beat.- Note `RoomConnection` has no client-side cursor today: the poll URL carries- only `timeout` and the server drains the queue on read. Resume is something- this migration *adds*, not something it has to preserve.+ `RoomConnection` resumes from a cursor; the pre-migration poll did not.**Stage C — the removals. Gated on the clients having transitioned.**@@ -898,12 +925,14 @@ versions must be updated when the agent-facing contract changes.## 14. Related work-- **CHOO-490** — HTTP protocol parity. Overlaps directly; this document is the- contract both should serve.-- **CHOO-1810** — two notification builders. Closed by §2.3: one delivery path- with a declared filter.-- **CHOO-1685** — AG-UI. Not addressed; the event envelope is versioned and- additive so it stays landable.+- **CHOO-490** — HTTP protocol parity. Delivered: the operation surface has an+ HTTP front door (`GET /agents/{id}/ops`, `POST /agents/{id}/ops/{operation}`)+ serving the same registry as MCP.+- **CHOO-1810** — two notification builders. §2.3 shipped, but this is **not**+ closed: both builders still exist, and `GET /agents/{id}/notifications` is+ still a live route.+- **CHOO-1685** — AG-UI. Being worked separately rather than here; the event+ envelope is versioned and additive so it stays landable.- **CHOO-1101 / CHOO-1366 / CHOO-1811** — bugs caused by the polling model.Useful as tests of whether this design makes them impossible rather thanmerely fixed.diff --git a/justfile b/justfileindex cf8a79a15..7c83c0eb8 100644--- a/justfile+++ b/justfile@@ -4,10 +4,6 @@set dotenv-load := true-# SandboxAQ-internal recipes (AWS/EKS/ECR deploy, Helm install, dev VMs).-# Optional so the public repo — which has no internal/ — still works.-import? 'internal/justfile'-# ── List available recipes ─────────────────────────────────────────────────────default:@just --list