1.4.36
Your agent keeps working when your project runs out of memory
When a project's own services fill a workspace, they are what slows down or stops — the agent, your terminals and the environment panel keep answering. Idle workspaces now go to sleep on their own, and wake without losing the agent.
New
- EngineA workspace with no prompt, agent run, terminal typing or environment action for 30 minutes goes idle on its own.
Improved
- EngineA workspace whose databases and test runs use up its memory no longer takes the agent, the terminal connection or the environment panel down with it. Your project's containers and processes are stopped first.
- EngineSet idle takes effect at once, and the agent keeps running through idle and wake — mid-task included.
- EngineThe agent knows when a workspace is idle, so a command stopped by going idle is not mistaken for a bug in your code.
- DesktopEvery workspace size comes with twice the processors, and an existing workspace can move up to its new size.
- MobileThe phone offers the same workspace sizes as the desktop.
Fixed
- DesktopThe compute panel shows sleeping workspaces at what they really take, so a machine no longer looks emptier than it is.