1.4.60Desktop
A workspace keeps its keys to itself
Each workspace now has an identity of its own, and it is no longer handed to the programs you and the agent run inside it.
Improved
- Each workspace gets a fresh key every time it starts, and an archived workspace’s key stops working straight away.
- Workspaces reach your connected accounts on their own, instead of through the computer they run on.
- A cloud workspace’s connection to the machine it runs on is encrypted, and it talks only to that machine.
- Cloud workspaces restart once as this update rolls out. Your files, branches and conversations are kept; open terminals start fresh.
Fixed
- The key a workspace uses to reach your Claude, GitHub and other connected accounts no longer shows up in its terminals’ environment, in what the agent runs, or in the list of running programs.
- If a workspace on your computer cannot reach Claude, MCP servers or your environment files, or your team’s machines do not show up, update Padar: older versions can no longer reach them.