Changelog

• Daemon Code-Host Tools — Agents open and manage GitHub pull requests and issues through the daemon instead of the gh CLI, so pull requests carry the attribution footer. GitHub, GitLab, and Gitea tools are grouped by object, add merge, state, issue, and label operations, and can act on another repository the agent is authorized for.
• Coordinator and Tasks — A coordinator can run on its own model, set beside the task model, and a task can change its model, effort, and approval mode from its own thread. Task threads accept images and files.
• Webchat Updates — The composer offers console commands such as stop and model on / and !, and suggests the runtime's predicted next prompt, which you can accept with Tab. Slack DMs also offer that suggestion. A NEW line marks what arrived since you last read, with Jump to latest and a turn map.
• Webhook Instructions — A generic webhook can carry its own instructions, with each payload passed as data, so systems with a fixed payload format can post straight to an agent.
• More Runtimes on Cloud — Kilo, Qwen Code, GitHub Copilot CLI, and goose use the deployment's managed model gateway, and Kilo and goose ship in the full runtime image.
• Per-Agent Desktops (Preview) — Each agent gets its own Linux desktop on a Computer that supports it, and you can pick which desktop to watch. Computers remain behind the computer-use flag.
• Daemon Auto-Upgrade Default — Organization owners can turn auto-upgrade on by default for newly created daemons.

Behavior change: The OpenCode runtime now runs OpenCode 2 (@opencode/cli), and OpenCode 1 is no longer supported. Per-agent desktops are on by default on Linux Computers that support them; turn them off from the tray or with desktops off.

This release fixes the relay sometimes losing a message, such as a webhook delivery, sent to a daemon shortly after the daemon's connection dropped and reconnected. The relay now sends to the daemon's newest connection instead of an older one that may no longer be alive.

• Single Sign-On — Self-hosted deployments can sign in through their own identity provider over OIDC or SAML, without configuring a social provider. Setup Server guides you through creating the connector and entering the provider's details.
• Redesigned Webchat Turns — Agent answers read as prose under a single work line that shows what the agent is running and how long it took, and approvals appear inside the turn that asked for them. Coordinator task cards open the task expanded over the conversation.
• Agent Environment Variables — Agents can set their own plain environment variables through the admin MCP updateAgent tool.

This release also fixes Slack Code channel diffs, task replies landing in the wrong thread, coordinator tasks missing admin tools in webchat, and another agent's Slack posts showing as a raw bot ID.

• Windows Background Service — agentconnect install-service now works on Windows, installing the daemon as a per-user task that starts at logon without administrator rights. up, down, restart, status, and upgrade --restart work through it as on macOS and Linux.
• Coordinator Tasks in Webchat — A task the coordinator starts appears as a card you can open to read and reply in its thread. A coordinator webchat session can be continued from its page, and its owner can change its visibility.
• Conversation-Aware MCP Servers — An HTTP MCP server can opt in to receive headers identifying the channel, thread, and session that calls it, so it can keep per-conversation state.

This release also fixes coordinators losing their conversation when their runtime session is recreated, and stale coordinator or task locks left behind when an agent moves.

• Auto Session Mode — A new Auto mode runs a conversation through a coordinator that reads incoming messages and hands work to titled tasks, each in its own thread. Tasks can delegate tasks of their own and keep summaries, follow-ups become watch tasks, and coordinators get a work board across places. New rooms and group DMs start on Auto.
• Slack Code Channels and Native Reports — A coding task can get its own Slack code channel with its plan, task list, and work steps. Agents can also publish collapsible reports and sortable tables, and Slack shows "Needs attention" while a turn waits on an approval.
• GitHub Apps per Agent — An organization can add its own GitHub Apps and give an agent one of them, so a reviewing agent acts as a different GitHub user from the agent that wrote the pull request.
• Daemon Auto-Upgrade — A daemon can upgrade itself to the release shown in the console once it is idle. This is a per-daemon switch, off by default.
• More Capability Requests — Agents can now request any setting on their agent form, including the runtime, and a scheduled task.
• Draft Pull Requests — GitHub pull-request integrations can skip drafts until they are marked ready for review.
• AHP Clients — Agent Host Protocol clients such as VS Code can sign in with AgentConnect through OAuth, and daemons now serve AHP by default where the deployment enables it.

Behavior change: New rooms and group DMs start in Auto mode on daemons that support it; existing conversations keep their mode. Session transcripts are now kept for 90 days by default, while session workspaces are still reclaimed after 7 days. Container images now run on Node.js 26; published npm packages still support Node.js 24.12 and later.

• Capability Requests — Any agent, not only one in assistant mode, can ask for what it lacks: settings, tools, repository access, connections such as MCP sign-ins or code hosts, and secrets. Request cards appear on every chat platform, and a person completes the request in the console. New live secrets reach a running agent on demand through the agentconnect-secrets helper and are masked in output. This remains behind the capability-requests flag.
• Computer Use Updates (Preview) — Agents can run commands and work with files on a Linux Computer instead of only working through screenshots. Approval is now asked once per session and answered by the Computer's allowed members. You can watch and take control of the agent's Computer from the session dock. The desktop image includes Chromium, LibreOffice, and developer toolchains, and the desktop app adds a macOS menu bar and a Windows service with a taskbar menu. Computers remain behind the computer-use flag.
• Webchat Files — Webchat uploads of any size are sent directly to the object store in parts, and message attachments appear as file cards.
• AHP and VS Code — VS Code can connect over the Agent Host Protocol more reliably, and file edits made by the runtime appear as edit results.

This release also fixes interrupted webchat streams after a relay gap and remote MCP grant renewal during long webchat sessions.

• Capability Requests (Preview) — An assistant-mode agent that lacks a setting or tool it needs can ask for it. A person completes the request in the console under their own sign-in, and the agent continues in the same conversation. This is off unless a deployment turns on features.capabilityRequests.
• AHP Clients — Third-party Agent Host Protocol clients that cannot send headers, including VS Code, can now authenticate and attach.
• Microsoft Teams Improvements — Channel rows name their team, a team's channels are listed on install, replies under the welcome card are answered, and conversations keep their team and endpoint across restarts.

This release also fixes runtimes that nest their own sandbox, such as Codex, failing under the srt strategy on self-hosted daemons, OAuth connections to MCP servers such as HubSpot that require client_secret_post, and the Slack working indicator while a delegated task runs. Agents now propose work they noticed on their own instead of starting it unasked.

This release fixes the Computer desktop image, whose desktop session could sometimes fail to start, either on first start or after a container restart.

• Microsoft Teams — Connect agents to Teams through your own bot or the deployment's Teams app. Agents can read channel history, answer approvals and questions with cards, and send editor approvals to the editor's own Teams chat. Session access can follow Teams permissions, and Microsoft sign-in is available.
• DingTalk — Connect agents to DingTalk, including international-edition apps. DingTalk supports streaming replies, attachments, tap-to-answer questions, group mentions, and direct messages.
• Share Any File — Agents can share any workspace file into a conversation, such as reports, spreadsheets, and archives, not only images.
• Computer Use (Preview) — Agents can see and control a desktop through new computer tools, with approvals, an audit trail, and a live viewer in the console. Computers can be self-hosted desktops or Linux machines from the Kubernetes pool. The console shows them only where the computer-use flag is on, which is off by default.
• Console Updates — Billing usage now groups charges by agent and model, with a per-day breakdown.

This release also adds early support for the Agent Host Protocol (AHP), which stays off unless an operator enables it.

Behavior change: Gemini CLI is retired as a runtime; agents that used gemini need to switch to Antigravity (antigravity-acp) and sign in there. New agents, and agents switched to another runtime, start in that runtime's auto mode, and the built-in agent on pool-backed installs now runs on Claude Code. An agent now replies with the "not enabled here" notice to every message that addresses it in a conversation where it is off, except conversations held By decision.

This security release completes the move to Node.js 24.22.1 for the October 20, 2026 Node.js security release, after v2.5.1 updated the service images. The runtime sandbox images that agent sessions run in are rebuilt on Node.js 24.22.1; they previously used 24.21.0. The database migration runner used by the Helm chart and Docker Compose now uses prisma-cli:7.8.0-node24-r2, which runs Node.js 24.22.1 instead of 24.18.0.

Upgrade note: If you override the migration image tag, through AGENTCONNECT_PRISMA_CLI_VERSION in Docker Compose or migrate.tag in the Helm chart, set it to 7.8.0-node24-r2.