Skip to content

Open-source AI teammates in Slack, Teams, Discord, Telegram and Mattermost. Self-host it, with any agent harness and any model.

Merge remote-tracking branch 'origin/verified-token-memo' into scale-core

Abel Dantas3585cd5df336
diff --cc CHANGELOG.md
index 11f4db9fc,48a31492c..652d618c2
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@@ -324,89 -224,11 +324,92 @@@ version of their own to them without al
group whose subgroup would move up next to a namesake is refused too, and
the dashboard now shows why. Names can no longer contain `/` or be blank.
Existing duplicates are left as they are and can be reached by id.
+- **Delivering an event to an agent behind a controller no longer reads the
+ agent's head first.** The notification of a new agent event already carries
+ its number, and the controller's stream now keeps it as the agent's head, so
+ a delivery costs the agent's own read alone, where it read the heads of all
+ the controller's agents first. The heads are still read after each idle
+ interval, when an agent is attached, and after the listener reconnects.
+- **Delivering an event to an agent costs three statements, where it cost
+ seven.** The rooms dropped after the agent's cursor are read with its
+ events, and the unread count reads the agent's baseline, the room's window
+ and the agent's user id in the statement that counts.
+- **Writing a message no longer costs four statements for each agent it is
+ for.** The agents' own events are stored together, in two statements and
+ one savepoint, where each agent's event took a savepoint, a numbering, an
+ insert and a release of its own.
+- **A controller's stream waits on three events, where it waited on one per
+ agent and two more.** Every attached agent's doorbell now rings the stream's
+ one bell.
+- **Reading an agent's own events no longer builds its query each time.**
+ Each shape of the read is built once and run with bind parameters.
+- **A message addressed to a connected agent no longer reads the agent's
+ membership after it commits.** That read stops an agent removed from the
+ room in the meantime from saying anything there, and a connected agent has
+ nothing to say about a message addressed to it, so the read is now made only
+ before a refusal or an offline notice is posted, or a machine woken.
+- **Message telemetry reads a workspace's rooms, clients and agents at once.**
+ The first lookup that misses reads all of them, where each room, sender and
+ agent was read on its own, so in a large workspace most messages no longer
+ cost a lookup.
+- **Registering, renaming or deleting an agent no longer makes every process
+ read every client and agent.** The change now names the clients it touched,
+ and each process reads only those, where it read every client of the
+ workspace and, with a messaging app connected, every agent as well. The
+ 30-second re-check reads every client only when a fingerprint of the
+ workspace's clients and agents has changed since its last full read, where
+ it read them all every time.
+- **The 30-second re-check of which controller runs each agent reads one
+ query, and nothing when no placement changed.** Every process read every
+ placed agent's definition, document included, then each controller with a
+ query of its own. It now reads the columns a binding is made of in one
+ query per workspace, and only when a fingerprint of the placements has
+ changed since its last full read.
+- **The 30-second re-check of who holds each controller's socket no longer
+ reads every controller each time.** It compares a fingerprint of their
+ connections and of the live processes first, and when it reads, reads only
+ the connection columns, where it read every row with its status and
+ platform, and the rooms of every agent on a controller another process held.
+- **Writing to a room for the first time through a process no longer reads the
+ room.** A process's clients now share the room ids they look up, where each
+ kept its own, and the first one a process misses reads every open room of
+ the workspace at once, so with many agents behind a load balancer most sends
+ no longer start with a read of the room.
+- **Checking a message against Switch Trust no longer reads its settings each
+ time.** Each process keeps the settings it read until they change: saving or
+ clearing them in the gateway tells every process, so a change still takes
+ effect on the next message. Settings are read again after 30 seconds at most,
+ for a change whose signal was lost.
+- **Reading an agent's budget standings no longer builds their query each
+ time.** The standings are read twice for every message an agent posts, and
+ building the query cost more than running it; it is now built once.
+- **Reading a room's context costs one transaction.** The room's newest
+ message number, the membership check and the history read share one
+ session, where each opened its own.
+- **A controller's requests no longer read its row and its agent's row each
+ time.** They were kept for 5 seconds, and a controller's requests, spread
+ over several processes, rarely came back to one within that. They are now
+ kept until a signal says they changed, which triggers on `agents` and
+ `agent_controllers` send, and a miss reads all of the controller's agents
+ at once. `CONTROLLER_AUTH_CACHE_MAX_AGENTS` (20,000) bounds the agent rows
+ kept.
+- **Reading an agent's rooms uses an index.** `room_agents` is indexed on
+ `agent_id`; reads by agent scanned the whole table, 2.9 ms each at 10,000
+ agents.
+- **Recording a message's usage builds its statement once.** The insert was
+ built for every message an agent sent; it is built once and run with bind
+ parameters.
+ - **A controller's access token is verified once.** Each process keeps the
+ tokens that verified until they expire, where every request verified its
+ token again; revocation is still checked on every request.
#### Fixed
+- **A client in more than 32,767 rooms starts reading them.** The reads a
+ client makes as it starts matched its rooms with one parameter each, and
+ Postgres takes at most 32,767 per statement. Switch's own client is in
+ every room of its workspace, archived ones included, so past that many it
+ failed to start, retried, and failed again while the process ran, taking
+ up rooms one at a time in between. The rooms now go as one array.
- **On Slack, the 👀 and the activity card no longer arrive after the agent's
reply.** Every running turn's card was redrawn every 5 seconds to tick its
clock. Slack closes a streamed card after 10 minutes, so on a longer turn