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
Merge remote-tracking branch 'origin/main' into fix/CHOO-4067-attachment-followups
Simon Flackfeb2bf52812f
diff --cc CHANGELOG.mdindex 321e6d9f3,93f14f567..132c0f328--- a/CHANGELOG.md+++ b/CHANGELOG.md@@@ -453,13 -576,35 +576,42 @@@ version of their own to them without altoken again; revocation is still checked on every request.#### Fixed+- **A file that names nobody now follows the conversation like text does.**+ A post with one or more files and no mention never reached the room's+ assigned agent, the agent whose thread it was posted in, or the agent the+ sender was just talking to, even with follow-ups on; the same words as a+ text message did. A post is now decided by the same rules, read from its- first file's text and thread, and the agent gets the post with every file- on it.++ first file's caption and thread, and the agent gets the post with every++ file on it, in that thread.+ - **The dashboard offers only the room changes the server would allow.** On+ a publicly writable room, the default, anyone could change the Access+ setting and press Save, only for the server to refuse it. Someone who could+ only read a room was still offered adding and removing its agents and+ users, attaching and detaching its resources, linking it to other rooms and+ deleting its room documents. A document, reference or package's page+ offered attaching it to, and detaching it from, rooms the viewer could not+ change. The rooms list offered archiving, and the groups page filing,+ rooms the viewer could not change; a bulk archive skipped those without+ saying so. Each of these was refused when tried. Access is now read-only for+ everyone but the room's owner and admins, and its description says so.+ Everything else is offered only to those who may write to the room, and+ only rooms they may write to are offered for attaching. A reader still sees+ each agent's "Notify on join" setting, but cannot change it. A publicly+ writable room's other settings stay editable by everyone, as before.+ - **Those taking part in a private room can read its resources.** The room+ itself could be read by its participants, but its references, documents,+ packages and linked rooms were refused to anyone but its owner and admins.+ - **Deleting a room document from the room page asks first.** It cannot be+ undone, and its own page already asked.+ - **Reconnecting Google Workspace no longer ends the new connection.** On a+ reconnect, Switch revoked the sign-in it replaced. Google ends every+ sign-in of the account through the client when one is revoked, so the new+ connection also stopped working, and the next token refresh asked the+ person to reconnect again. A reconnect to the same Google account through+ the same client no longer revokes the old sign-in. A reconnect to another+ account still revokes it, and so does a disconnect. A sign-in that Switch+ does not keep, because the workspace switched Google Workspace off during+ it, no longer ends the existing connection either.- **A client in more than 32,767 rooms starts reading them.** The reads aclient makes as it starts matched its rooms with one parameter each, andPostgres takes at most 32,767 per statement. Switch's own client is in