v0.4.50

Containers are now called workspaces throughout the dashboard. The sidebar entry, the list, the create page and every page that mentions one say workspace, and the pages have moved from /containers to /workspaces. Old links and bookmarks still work: they forward to the same page, tab included. Container is kept where it means the Docker container a workspace runs in, which a snapshot restore can replace while the workspace stays. The Workspaces page forgets whether you chose the grid or the list once, after the upgrade, and the Terminal tab forgets which terminals you had tiled in its grid; the terminals themselves keep running.

Breaking: the API says workspace too. Every /api/v1/containers… path is now /api/v1/workspaces…, and /api/v1/admin/container-domains is /api/v1/admin/workspace-domains. The old paths are gone rather than aliased. Schemas and operation IDs follow (WorkspaceResponse, CreateWorkspaceRequest, listWorkspaces, …), and so do the fields that name a workspace: container_id is workspace_id, container_name is workspace_name, and attached_container_* and source_container_* are attached_workspace_* and source_workspace_*. An API-key grant on a workspace has resource_type workspace, not container. Automations have a create_workspace action (was create_container), a workspace parameter type, and a workspace_id field on run_script and create_api_key steps. Keys, saved automations and automation history are moved onto the new names when the server upgrades. Error messages follow: "workspace is not running", "workspace is delete-locked".

Breaking: so do the MCP tools. The fourteen tools named after containers are named after workspaces: list_workspaces, get_workspace, get_workspace_logs, create_workspace, update_workspace, delete_workspace, start_workspace, stop_workspace, restart_workspace, list_project_workspaces, add_workspace_to_project, remove_workspace_from_project, add_workspace_subdomain and remove_workspace_subdomain, in a tool group called workspaces. Arguments and results follow: container_id is workspace_id, source_container_id is source_workspace_id, and list_workspaces returns workspaces. Keys granted the old tools, and automations that list them for a new key, are moved onto the new names when the server upgrades. A Claude.ai connector sees a new tool list and asks again before using the renamed tools.

Breaking: a workspace's id is in DEVGRAIL_WORKSPACE_ID. New workspaces, and any workspace a snapshot is restored onto, get DEVGRAIL_WORKSPACE_ID instead of DEVGRAIL_CONTAINER_ID. A workspace whose container was created before this release keeps the old variable until then, because a running container's environment cannot be changed; the instructions file DevGrail writes into it states the id either way. The agent-instructions placeholder is {{DEVGRAIL_WORKSPACE_ID}}: saved instructions are moved onto it when the server upgrades, and {{DEVGRAIL_CONTAINER_ID}} still renders.

The database says workspace as well: the containers table is workspaces, container_domains, container_snapshots and container_subdomains are workspace_domains, workspace_snapshots and workspace_subdomains, and every container_id column is workspace_id. The tables are renamed in place when the server upgrades; no data is copied. This matters only if you query the SQLite file yourself. A backup taken after the upgrade restores only onto this release or a later one, as with any schema change.

The server log says workspace too: a log line about a workspace names it under workspace or workspace_id, not container or container_id. This matters only if you filter the server's logs by those keys.

The MCP server now gives agents instructions when they connect: what a workspace is, and that /workspace is a directory inside one. The tool descriptions and the instructions DevGrail writes into each workspace say workspace too, so asking an agent for "the test workspace" no longer sends it searching /workspace for files. Each workspace's dashboard_url now points at /workspaces/<id>.

The create page no longer says a volume lets a workspace be "recreated", or that an ephemeral workspace loses its files when recreated for a new image. Recreating was replaced by restoring a snapshot onto the current image. An ephemeral workspace's /workspace goes into its snapshots and is replaced when one is restored over it.

Opening several terminals in a workspace now connects each pane to its own session. Before, every pane could display and control the same session.

sudo devgrail passwd and sudo devgrail add-user keep spaces at the start or end of a password. Before, they dropped them, so the password saved was not the one you typed and you could not log in with it. A password set that way before this release still works without those spaces.

Both commands also take the password from a pipe, so a provisioning script can run them: printf '%s\n' "$PASSWORD" | sudo devgrail add-user alice. At a terminal they prompt twice as before.

Secret names are limited to 64 characters, as the API reference always said. Before, the dashboard and the API accepted longer names and only the MCP tools refused them. A secret that already has a longer name keeps it, and you can still change its value without renaming it.

Creating a workspace with a launch script whose parameters are missing or wrong no longer leaves an unused volume behind. The volume was made before the parameters were checked, and was not removed when they failed. Volumes left this way by earlier versions are listed under the Volumes tab of the Containers page, where you can delete them.

A project's name and description are saved the same way wherever they come from: spaces at the start and end are dropped, and the documentation is kept exactly as written. Before, the dashboard kept spaces around a description, and a project an agent created lost the indentation at the start of its documentation, which could break a Markdown code block.

When the server cannot reach Docker, the System page and the Orphaned networks page load again: the one shows what it can, the other says Docker is unavailable. Before, the server dropped both requests without an answer, so the pages showed an error.

A folder or multi-file download that breaks partway through, for example because the workspace stopped, now shows as failed in the browser. Before, it could look finished and leave a zip that would not open.

The dashboard, the guides and the built-in agent skills now talk about Antigravity CLI (agy) rather than Gemini CLI, which workspaces stopped shipping in v0.4.40. An agent helping you set up Antigravity is pointed at the Antigravity scripts, its sign-in token and agy mcp add, instead of at gemini commands that no longer exist in a current workspace.