v0.4.55

More shared memory for development tools. Newly created workspace containers and containers recreated by snapshot restores have a 1 GiB /dev/shm, up from Docker's 64 MiB default. Shared-memory usage still counts toward the workspace's memory limit. Existing containers keep their current size until recreated.

Install apps and developer tools from desktop controls. Open Install apps & tools to search the catalog and install, update or uninstall VS Code, ChatGPT, Claude Desktop, Antigravity, ripgrep, GIMP and Inkscape. Downloads happen only when requested, from official signed repositories. The panel shows installed versions and progress; uninstall keeps settings and refuses to remove a package another installed package needs. Electron launchers use --no-sandbox inside the workspace container. VS Code and Antigravity open directly from the terminal even when Docker shares a WSL2 kernel, without prompting to install the Windows app. Claude Desktop launchers use --disable-dev-shm-usage to prevent a white window and connection error caused by renderer crashes with Docker's default shared-memory limit. The panel scrolls to the top after actions to show confirmations and progress.

Notifications from the desktop reach you. A notification from an app in the desktop add-on's desktop, such as notify-send at the end of a long build, now shows at the top right of the viewer, where you can click it or its buttons. Turn on Notifications › On this computer in the desktop's controls to get them as your computer's own notifications while the viewer is in the background; an installed desktop app also counts unseen ones on its icon.

The browser tab names the window you are working in. The desktop viewer's tab, and an installed desktop app's window, now take the title of the window in front of the desktop, so you can tell desktops apart in the tab bar and the window switcher.

Everyday apps in the desktop. The desktop add-on now installs a text editor, Meld for comparing and merging files, an image viewer, an archive manager, screenshots, a task manager and a calculator, and PDFs open in Firefox. Upgrading an installed desktop adds them.

The desktop on a phone or tablet. A keyboard button at the bottom right of the viewer, or Show keyboard in its controls, brings up the on-screen keyboard to type into the desktop, with a row of the keys it lacks: Esc, Tab, Ctrl, Alt and the arrows. The desktop makes room above the keyboard, and its Help explains the touch gestures: tap to click, touch and hold to right-click, two fingers to scroll. On an iPhone, where a page cannot go full screen, the controls no longer offer it.

The desktop picks up where you left off. After the desktop restarts, is upgraded or its workspace restarts, its terminals reopen in the folders they were in, and Firefox reopens with its windows and tabs. The desktop saves what is open every minute and before it stops.

Help in the desktop add-on. A Help button in the desktop's controls opens a guide over the desktop: how copy and paste work between your computer and the desktop (and why a copy from the desktop sometimes waits for a click), dropping and downloading files, keyboard shortcuts the browser keeps, sound and the microphone, and what to know about a desktop everyone shares. The controls now also close when you click anywhere outside them.

Paste JPEG, WebP, GIF and other images into the desktop. Pasting an image used to work only for PNGs, such as screenshots. An image in any format your browser can show, such as an image file copied in Explorer or Finder, is now converted to PNG on the way in (an animation keeps its first frame).

Paste files into the desktop. Copy files on your computer and paste them into the desktop's file manager, or onto its desktop, and they land in the folder you pasted them in. Until now, pasting a copied file did nothing; only dragging it onto the desktop worked. A single image file still pastes as an image.

A progress bar for files copied into the desktop. Dropping or pasting a large file shows how much of it has arrived.

Find add-ons in the dashboard. A new Add-ons page in the sidebar lists what you can add to a workspace you already have, with a guide for each. The desktop add-on's guide gives you the install command for your DevGrail to copy into the workspace's terminal, and walks through adding its subdomain, signing in, its options, RDP, upgrading and removing it. Pick a workspace on the page to get links straight to its terminal and settings.

The desktop add-on moved on the DevGrail website. Its guide is now at /addons/desktop, and the install command is curl -fsSL …/addons/desktop/install.sh | bash. The upgrade command the desktop shows uses the new address once the add-on is installed or upgraded from it.

Breaking: the desktop image and the dashboard's Desktop tab are gone. The desktop add-on replaces them: install it into any workspace, from the guide on the Add-ons page, and reach its desktop through an app subdomain. The installer no longer offers or downloads devgrail-desktop, its --desktop-image flag is gone, and Container images and Updates no longer list it. Before upgrading, move anything you want to keep out of workspaces created from the desktop image into a default workspace (add the desktop add-on there if it needs a desktop), then delete them. One left running keeps running, but its desktop no longer connects, and it cannot be recreated once the image is removed. After upgrading, remove the old image with docker rmi $(docker images -q devgrail-desktop), and delete the DEVGRAIL_DESKTOP_IMAGE and DEVGRAIL_DESKTOP_IMAGE_DECLINED lines from /opt/devgrail/deploy/.env, which nothing reads any more.

Breaking: an agent can no longer read API keys and secrets it was never given. A script run puts the values of its @[apikey:…] and @[secret:…] references into the workspace, where the agent can read them. Any API key holding run_script and write access to one workspace could therefore name any of your keys or secrets — including a full-access key with external access — and read it. A run an agent starts may now only use the agent's own key, a key with no more access than it (and without external access unless the agent's key has it), and secrets granted to its key. Anything else stops the run before it starts, with a message naming the key or secret. Runs you start from the dashboard and automations are unchanged.

Breaking: secrets are granted to API keys. The key editor has a new Secrets section, with an "all my secrets" option like the ones for scripts and skills. Existing keys hold no secrets. If an agent runs scripts that use your secrets, or updates or deletes secrets over MCP, open its key under API keys and tick the secrets it should use. A secret an agent creates is granted to its key automatically. A secret whose value is a file in a workspace is usable through its grant alone, even by a key with no access to that workspace, so grant one only to agents that may read that file.

Breaking: an agent saving a script may only add references it could use itself. Creating, editing or cloning a script over MCP is refused when it would add a reference to a key or secret the agent's key may not use, so an agent cannot leave one for you to run. References a script already had do not block an edit.

Deleting a workspace shows that it is under way. The delete dialog closes as soon as you confirm, and removing a workspace can take a while. Its card on the Workspaces page now dims and its Delete button spins and reads "Deleting…" until the workspace is gone, instead of looking untouched.

Signing in to the desktop add-on works. In v0.4.54 the browser was told to leave out where a request came from, so the desktop turned away its own sign-in form with "This sign-in did not come from the desktop's own page". Once signed in, the picture and sound connections were turned away the same way, so the desktop kept showing "Desktop disconnected" and reconnecting. Run the install command again in the workspace to upgrade it.

Strangers can no longer keep you out of the desktop add-on. The desktop's sign-in allows thirty attempts a minute in all, to slow down password guessing from many addresses at once, and anyone who kept that limit used up could stop the owner from signing in. A browser that has signed in to the desktop before is now remembered and is not held up by that limit, only by its own five attempts a minute. Addresses on one IPv6 network now count as one address. Run the install command again in the workspace to upgrade.

Adding the Claude.ai connector can no longer be blocked from outside. DevGrail keeps at most 1,000 connector registrations, and registering needs no sign-in, since Claude.ai registers before you sign in. Anyone who kept registering could keep that table full, and adding a connector then failed with "temporarily unavailable". A new registration now pushes out the oldest one that never became a connection. Connectors in use are never touched.

Sign-in lockouts count an IPv6 network as one address. After five wrong passwords the dashboard holds back further sign-ins from that address for fifteen minutes. An IPv6 caller could previously move to the next address on its network and keep guessing; addresses on one IPv6 network (/64) now share one count. The connector registration limit counts them the same way.