10.5.0 — A cell closes when its agent ends, and Antigravity tells you when it is done
A snapshot as of 10.5.0 (released 2026-10-15). It will go stale as the app moves on — that is expected, and the living reference is the guide each section links to.
New features
A cell closes when its agent ends on its own
When the agent in a cell ends by itself — you type /exit, press Ctrl+C twice, or it crashes — the cell used to stay on the grid showing [session ended]. Cells an agent opened for you piled up that way. Now the cell closes itself, exactly as if you had pressed its close button (#3051, #3049).
To try it: open an agent cell, wait for it to start, and type /exit. The cell disappears.
Changed your mind? Open the command palette and type Reopen — the closed cell is listed there, and an agent cell comes back with its conversation.
Three cases still keep the cell with its [session ended] line, on purpose:
- The agent failed to start (it ended within a moment of launching). The line is the only sign of what went wrong, so it stays.
- The agent is still running but the browser lost its connection to it. Reload the page and the cell reconnects.
- A worktree cell. Closing one asks whether to keep or remove the worktree, and that is not asked without you.
The same goes for a session an agent started while no grid was open: if its agent ended before you looked, the next grid you open no longer brings it back as a new cell (#3056, #3055).
More: Basics.
Antigravity cells light the working dot and say when they are done
An Antigravity (agy) cell now lights the working dot while a turn runs. When the turn ends it gets the attention mark, plays the finished sound and sends the “finished” push to your phone — the same as a Claude cell, under the same notification settings (#3038, #3034).
Nothing to set up. MulmoTerminal adds one hook named mulmoterminal to .agents/hooks.json in the project, beside any hooks of your own, and keeps it out of git through .git/info/exclude. There is still no signal for “Antigravity is waiting for your answer”.
More: Notifications.
A MulmoScript on the Canvas redraws when something else edits it
When a MulmoScript is open on the Files pane’s Canvas and the file is changed from outside — your editor, git, or an agent’s edit — the Canvas now redraws with the new content. It used to keep showing the old one until you reopened it (#3040, #3014). Edits made in the Canvas itself do not cause an extra redraw.
More: MulmoCast.
Talking avatars in MulmoCast: how to install them, and init checks
MulmoCast can make a speaker a talking avatar, but the parts it needs (avatarscript, onnxruntime-node) are optional and MulmoTerminal does not install them. The MulmoCast guide now has a section on writing, installing and checking them, and npx mulmoterminal@latest init prints an avatar line saying whether they were found (#3043, #3042).
More: Talking avatars.
New sound effects and richer beat previews in MulmoScript
MulmoCast 2.23 and the MulmoScript plugin 5.5 are in (#3037, #3035):
soundEffectscan use JingleScript 0.8’s effects (ding,door,dice, …) andgrandpiano.- A beat preview draws
html_tailwindbeats with their background, branding and scripts. - Still images can be generated without ffmpeg. The startup warning for a missing ffmpeg now says only movies are affected (#3036).
More: MulmoCast.
Short answers to common questions
Ten short pages answer questions people search for — running Claude Code or Codex in parallel, using several accounts, how this differs from tmux, cmux or Claude Squad, and which cell is waiting for you (#3052).
More: Answers.
What looks different
- Agent cells disappear when their agent exits. Before, they stayed with a
[session ended]line. Use Reopen in the command palette to bring one back. - The update notice for a git clone now says to run
git pull origin <branch> && yarn install && yarn build, then restart. It used to say onlygit pull, which left the browser side and the dependencies old while the notice disappeared (#3045, #3044).
Under the hood
- An agent can start a session with only some GUI tools.
spawnBackgroundChatacceptsguiGroupsfor a Claude session; the limit holds across reattach, restart and resume (#3050, #3033). - A second server started with another
HOME(for screenshots or tests) now gets its own tmux server and its own folder for dropped files. Before, it could end the first server’s idle sessions, change its tmux options and delete the copies of files you had dropped into its sessions (#3053, #3054, #3039). - Dependency updates (#3032), faster CI through a shared Chrome cache (#3031, #3047), and wording fixes in the docs and comments (#3041, #3048).
- Nothing needs doing.