1.3.17
One stuck workspace no longer stops the rest
A workspace that stopped responding used to take the whole app down with it — every other workspace slowed to a crawl, and the stuck one stayed stuck until somebody noticed. Now the rest keep working, and the stuck one comes back on its own.
Improved
- DesktopThe agent keeps going through a brief disconnection. It used to lose the turn outright, and git would lose access to GitHub with it, if the connection dropped for a second.
- DesktopNew workspaces come in 1, 2 and 4 vCPU. Existing workspaces keep the size they already have.
- MobileA teammate you tag reads as a person on your phone rather than as raw text, and the notification opens the workspace they were tagged in.
Fixed
- DesktopYour other workspaces keep working when one stops responding. Requests to a workspace that has stopped answering now give up instead of waiting forever, so nothing else queues behind them.
- EngineA workspace that stops responding is rebuilt for you, in about a minute, instead of sitting there until someone notices. Anything you had not committed in it does not survive the rebuild — push before you step away.
- DesktopThe agent can tell when a message is addressed to a teammate rather than to it, and stays out of the way.