v0.4.40

Workspaces now come with Google's Antigravity CLI instead of Gemini CLI. Google has retired Gemini CLI in favour of Antigravity, so gemini is gone from the workspace image and agy takes its place — the same account, a different command. Type agy in the terminal to start it. It is a compiled binary rather than an npm package now, so it installs into your own ~/.local/bin and keeps itself up to date from there. Existing workspaces are untouched until you recreate them — gemini stays where it is, for as long as Google keeps answering it.

Guides now start by saying what DevGrail is. Every guide so far assumed you already knew what a workspace, a project, a script, a skill and an API key were — the words the rest of the dashboard is written in. A new What DevGrail is guide defines those five in one page, alongside what the product actually runs and what an agent holding one of your keys can reach. It sits first under Guides, hands you on to the get-started walkthroughs, and is offered beside them on the panel a brand-new install lands on — where the walkthroughs now say plainly that they are the agent route. It also answers the question a developer arrives with — why run an agent here rather than on the laptop — in a paragraph, and then at length: a workspace per branch instead of two agents fighting over one checkout, port 3000 and one local database; approvals asked once instead of at every step of a forty-file change; the dev server reachable on a real HTTPS URL you can send to someone; test suites and builds that carry on after you close the lid; a toolchain that is a script rather than a machine that drifted, on the same Linux the code deploys to; and an agent whose reach is the key you handed it rather than every repo and credential on your disk.

DevGrail now describes itself without borrowing another product's name. The sign-in page, the guides and the instructions every workspace hands its agent all led with “cPanel for AI developers” — a description that only lands if you happen to have run cPanel. They now say the same thing in plain words: a machine of its own for every coding agent, self-hosted on a single server you control.

A brand-new install now sees one thing, and the same thing everywhere. Before you have a workspace, the dashboard led with meters of an idle host and two empty "heaviest workspaces" lists, and the invitation to make your first one sat underneath them. That invitation is now the whole page — the capacity cards, the usage lists and the header's "New Container" button stay away until you have something to measure. Containers shows the same panel, pointing at the getting-started guide rather than only offering a bare container: the tab strip, the view toggle and that page's own header button all stand aside for it, so a first install has one thing to read and one thing to do. Volumes and Re-add come back with your first workspace, along with everything else.