v0.4.11

Added

• A house size for new workspaces, set once instead of per workspace. Settings has a Workspace defaults card holding a default CPU limit, a default memory limit and a process limit. Until now the first two did not exist: a workspace created without limits was created with none, so keeping a shared box from being swallowed by one runaway container meant remembering to pick limits every single time — including on the workspaces an agent creates over MCP, where nobody is there to remember. The defaults apply wherever a workspace is created from, and they are a default rather than a ceiling: a workspace that names its own limits keeps them.

  Changing the default never resizes a workspace that already exists. Each one records the limits it was actually given at creation, so what you see on a workspace is what it is running with, and a later change to the house default cannot quietly re-size it on its next restart or rebuild.

  The create form now labels its first CPU and memory option with the default your deployment will really apply — "Default (2)" rather than a flat "Unlimited" that would be untrue as soon as you set one. Picking "Unlimited" explicitly still does what it says.

• The workspace process limit is adjustable. It caps how many processes one workspace may spawn, so a fork bomb or a runaway build cannot exhaust the host's process table and take every other workspace down with it. It has always been there at 4096 and stays there unless you change it; the reason to raise it is a genuinely build-heavy workspace hitting the ceiling, which previously needed a custom build. There is deliberately no "unlimited" setting — it is a guard on a shared host, not a sizing preference — and it applies to a workspace the next time it is created or recreated.