Canopy 0.4.8

Canopy 0.4.8 runs the companion and its Slack replies properly from a cloud workspace, lets your agents talk to the agents in a cloud workspace, makes the workspace browser preview much smoother, keeps your agents' conversations when you switch accounts, keeps a busy workspace from being stopped by hang recovery, and brings its agents back after a restart.

Companion in cloud workspaces

While you are connected to a cloud workspace, the companion now runs on your computer, as it does locally, instead of failing with "The Linux workspace does not support companion_spawn yet". Its Canopy tools still act on the workspace's projects. Slack messages to the companion are now picked up and answered from your desktop.

Slack replies from Codex

A companion running on Codex no longer answers Slack with "this session isn't running inside a Canopy terminal". Canopy now passes Codex the connection its Canopy tools need; existing setups pick this up the next time Canopy starts.

Agents across your cloud workspace

Agents on your desktop can now list the agents running in a cloud workspace, with their names, tasks and status and whether the workspace is online, and message them. Replies come back to the terminal that sent the message, and a message that fails is reported there instead of being dropped. Workspace agents can reply, but cannot yet start a conversation with your desktop agents.

Smoother workspace browser preview

In our tests, scrolling the workspace browser preview runs at about three times the frame rate, and each frame is about a third of the size. Fixed a race that could leave the preview blank.

Switching accounts

Switching to another account from the status bar asks again whether to reload your running agents, even when the side panel is closed. Before, the question only appeared while the side panel was open, so agents stayed on the old account. Claude and Codex agents continue the same conversation under the new account. When no running agent can move, Canopy now says why.

Agents come back after a workspace restart

When a cloud workspace restarts (hang recovery, a crash you resume, or a stop and resume), the Claude and Codex agents that were running start again in their own folders with their conversations, launch flags and Canopy tools, and go back into their tabs. A resumed agent waits at its prompt. Builds and commands you typed are not re-run; their terminals are marked interrupted.

Workspace reliability

A workspace that stops responding is now restarted in place, keeping its container and files, and only after 5 minutes without a response. Before, a busy workspace could be stopped after 30 seconds and stay stopped until you resumed it. A workspace you stopped on purpose is never restarted. Teammates' access to a shared workspace no longer lapses after the workspace service restarts. Fixed agents in a cloud workspace sometimes losing their Canopy tools when they started while the workspace was checking its terminals.

The agent list, hang recovery, agent restart, teammate access and agent tools fixes need your workspace's latest host software, installed separately. The faster preview also needs the latest workspace image, which your workspace picks up the next time it is resumed.