# Moontors 0.8.2 Released November 5, 2026. Moontors, the agentic development environment (ADE) for Claude Code, Codex, Gemini CLI and Grok Build, now runs Claude Code 2.1.318, Codex 0.166.0, Gemini CLI 0.66.0 and Grok Build 1.0.70. This release brings terminals that come back after an update; adding an MCP server, and signing in to one with all four agents; trusting a folder right in Moontors; a blue Done for the sessions you haven't seen; your sent messages on Up and Down, and what you're writing kept as you move between sessions; hooks that say what went wrong; and projects as shortcuts you can remove at any time. What's new: - Terminals come back after an update. When Moontors restarts to update, or a newer version takes over its background service, each running terminal is back in its tab, in its folder and its order, with its name and its history, on a new shell. The programs that were running in it stop, and a line under its history says so; the update notice says so before you restart. Its history sits in a private file on your computer only until the new version reads it. One whose shell had exited doesn't come back, nor one in a folder that's gone, or that no open session works in and you no longer have as a project. If the background service crashes or is killed, no running terminal or its history comes back. The first restart into this version can't bring them back either, as the version you're updating from keeps none. See [The terminal](https://moontors.com/docs/terminal/#limits). - **Add MCP server**, under the MCP servers on the agent's tab in **Configuration**, adds a server by its command or its URL, for that agent and any others you choose. **This project** and **All projects** keep it in Moontors, its env and header values in your system's keychain, and it reaches only Moontors' sessions: your agent's own terminal and editor extensions don't see it. **Shared** writes it to the agent's own file in the project (`.mcp.json`, `.codex/config.toml`, `.gemini/settings.json` or `.grok/config.toml`), so it reaches the agent outside Moontors too, and everyone who opens the project shares it, its values as you typed them. The form warns you first, naming the file, and the rest of the file stays as it was. See [Adding an MCP server](https://moontors.com/docs/configuration/#adding-an-mcp-server). - MCP servers that need a sign-in now sign in from Moontors with all four agents, as Claude Code, Gemini CLI and Grok Build join Codex. A server that needs it shows **Sign in**, or `/mcp login ` in the composer starts it: its page opens in your browser, the button says "Finish in your browser", and the server connects once you've signed in. With Gemini CLI, a server that asks is off for the run until you sign in, which starts the agent again. A server you add from Moontors signs in too, but not for Gemini CLI, which has no way to be asked for one: the form says to put its token in **Headers**. A Claude Code sign-in you refuse or leave in the browser fails only after five minutes. See [`/mcp`](https://moontors.com/docs/configuration/#mcp). - A folder is trusted right in Moontors, with no trip to an agent's own terminal. On your computer, **Create session** and **Add project** end with **Trust this folder**, on by default, saying why and naming some of what the folder's config runs, and **Edit project** shows it when you move a project to another folder. On, Moontors records the folder as trusted for all four agents and the toggle doesn't show again; there's no way to untrust a folder in the app, and **Remove Moontors' Data…** clears the record. In a git repository it covers the repository from that folder down and its worktrees, but no repository inside it, and elsewhere that folder alone. Your home folder and those above it can't be trusted. Off, the session starts untrusted, skipping the folder's own instructions, settings, MCP servers and hooks, and the toggle shows again next time. In an open session on your computer, **Trust this folder** is on the `/status` screen and beside each MCP server and hook trust keeps off, taking effect in every session in the folder from its next turn, or once its background tasks end. Folders you'd already used in Moontors go on as they did until you answer, and Moontors never writes your agents' own trust files. Codex's warning to edit its `config.toml` no longer shows. The toggle and the button are on your computer only. See [A folder's trust](https://moontors.com/docs/configuration/#a-folders-trust). - A session you sent to work that's finished and you haven't looked at is told in blue, on your computer and in the Android app: **Done** in blue on its card, and a glowing blue pill among the header's tags, such as 2 done, which shows you the next one. It goes back to grey once you've seen it. Your own messages and commands count, from either device, not a message from another session or a turn the agent starts by itself, and no session finished before this version lights up. See [Done, not seen yet](https://moontors.com/docs/sessions-notifications/#done-not-seen-yet). - On your computer, Up and Down in the composer bring back what you've sent in this session: Up with the caret at the very start of the text brings the message before, and Down at the very end brings the next one, then what you were writing. It takes messages and commands sent from your computer or your phone, rewound ones too, and every other press of an arrow stays as it was. See [Your sent messages](https://moontors.com/docs/sessions-composer/#your-sent-messages). - On your computer, what you're writing in a session's composer, with its files and the row it replies to, stays there while Moontors runs: open another session, come back, and it's all there, the caret after your words. Quitting, closing the window or restarting to update asks first about the unsent words in every session, naming them. Archiving or deleting the session lets them go. - A hook that goes wrong explains itself, on your computer and in the Android app: a row in the transcript says which event's hook it was, which plugin it came from or what it ran, and what it said, as far as each agent says, with **Open Hooks** beside it on your computer. Codex says only the exit code of one that fails. A hook that blocks your prompt gets a row with its reason, though Gemini CLI doesn't report one, and so does one that blocks a command with Codex, as nothing else says it happened. Claude Code's line sending you to ctrl+o is gone. Gemini CLI's `BeforeTool`, `AfterTool`, `Notification` and `SessionStart` hooks, which it doesn't run in a client like Moontors, show off in `/hooks`, marked **Doesn't run in Moontors**, so one meant to guard a command doesn't guard it here. While a Gemini CLI session runs, Gemini CLI keeps a debug log in Moontors' own folder, readable only by you, of which Moontors reads only the hooks' lines, and which it removes when Gemini CLI stops. See [`/skills`, `/plugins`, `/hooks`, `/agents`](https://moontors.com/docs/configuration/#skills-plugins-hooks-agents). - With Claude Code 2.1.318 and a Claude subscription, **Profile**'s **Providers** and the Android app's **Accounts** say when its sign-in ends, and ask you to sign in again before then. A permission question a hook made Claude Code ask says under it which hook asked and why, such as `PreToolUse hook asks · formatter: …`. With a claude.ai organization that offers Life Sciences use cases, the one you chose with `/use-case` in Claude Code's own terminal applies in Moontors from each session's next start. See [Providers](https://moontors.com/docs/sign-in/#providers). - With Gemini CLI, **Sign in in your browser** now says beside it that it's for organizations with a Gemini Code Assist subscription: personal accounts, Google AI Pro and Ultra included, sign in with an API key, as Google has ended that sign-in for them. Where your shell's environment keeps Gemini CLI from opening a browser, the dialog says which setting does. Gemini CLI in Moontors signs in only the way you choose there, never with an API key your own Gemini CLI saved. See [Gemini CLI](https://moontors.com/docs/sign-in/#gemini-cli). - A project is now a shortcut for quickly opening sessions in a folder, and you can remove it at any time, sessions open or not, with **Remove project…** in its right-click menu. Only the shortcut goes: the folder, its files, git, its worktrees and its branches stay, sessions stay as they are, open ones still running, and you can add the folder again. Terminals in its folder end unless an open session works there, and the dialog names them first. **Edit project…** is now in the right-click menu alone. See [Projects](https://moontors.com/docs/projects/). - **Archived**, **Settings** and **Profile** now cover the board and the panel, as Files and Git do, at any width of the window. What's under them stays as you left it, and comes back once you close them. See [The layout](https://moontors.com/docs/window/#the-layout). - Whatever takes you to a session now shows it: a notification, a state tag, a link to a session in a transcript or the Git view, and reopening one from **Archived** each close what covers the board first, keeping what it held. In the Android app, tapping a notification closes a sheet left open on the board. - **Profile**'s **Providers** stand in even columns with no gap under a short card, the agents a session can start on first, and a long email or organization wraps inside its card. The Android app's **Accounts** lists the agents you can start first too. See [Providers](https://moontors.com/docs/sign-in/#providers). - While a compaction runs, the transcript's live line says "Compacting the conversation…" with its time, where it said "Working…", on your computer and in the Android app. - The notice about usage numbers and error reports is gone: the line 0.8.1's notes described, with its **Turn off**, no longer shows under the desktop's header or in the Android app. Sharing stays on unless you turn it off, and the switch stays where it was: **Settings**' **Privacy** tab, where `DO_NOT_TRACK=1` still holds it off, and in the Android app **Accounts** and the pairing screen. See [Privacy](https://moontors.com/docs/settings/#privacy). - In the Android app, every message a long press works on lights its border while your finger is on it: the agent's in any turn, your own, and an answered question's or permission's card. A press no longer shrinks what it holds, such as a held card or a question's choice. - Your messages and the agent's now sit on solid backgrounds, with nothing showing through, and the agent's is a little darker than the transcript behind it, so it stands out, on your computer and in the Android app. - The Git view's worktree menu has a line between the sessions it opens and the session it starts. - On moontors.com, the home page has a **Key features** card, and the guides have two new pages, [Done and notifications](https://moontors.com/docs/sessions-notifications/) and [Notes, footers and replies](https://moontors.com/docs/sessions-notes/). - Fixed: signing out of your Moontors account while **Profile** was still reading it leaves you signed out, here and in every window, where the read could undo the sign-out. The same goes for an agent you sign out of while Moontors reads its account, and a late answer for an account you've signed out of no longer touches the one you've signed in to since. A sign-in with a key still running when everything is signed out is cancelled, so it keeps no key, and a phone unpaired while its way to reach your computer from anywhere is being set up gets none. - Fixed: at the window's narrowest, its text larger too, nothing runs past its sides: where the first project and the icons don't fit beside **Create session**, the projects, the tags and the icons take a row of their own below it, and the board keeps within its room. - Fixed: a state tag's hover in the header fills its own box and goes no further, and a tag's press in the Android app does the same. - Fixed: in the Android app, holding a message no longer shows a fill's square corners past its rounded bubble, and a question's choice shows one fill when pressed, where it showed two. - Fixed: in the Android app, a message you sent just before leaving its session no longer comes back in its composer, the row you're replying to stays when you leave while the app runs, and a message you're writing that ends in @ no longer opens the file list as you come back to it. - Fixed: in the file lists, a `.gp` file is no longer drawn as audio, and a `.tosd` file is drawn as TOML. This version updates the Android app; the iPhone app isn't updated this time. The Windows and Linux builds still aren't signed, so Windows asks once before Moontors opens. The README's "First launch" and "Updates" sections say what to expect on each platform. Found a problem, or have an idea? Open an issue: https://github.com/moontors/moontors/issues/new/choose ## Downloads - macOS, Apple silicon: [Moontors-0.8.2-arm64.dmg](https://github.com/moontors/moontors/releases/download/v0.8.2/Moontors-0.8.2-arm64.dmg) - macOS, Intel: [Moontors-0.8.2.dmg](https://github.com/moontors/moontors/releases/download/v0.8.2/Moontors-0.8.2.dmg) - Windows: [Moontors-Setup-0.8.2.exe](https://github.com/moontors/moontors/releases/download/v0.8.2/Moontors-Setup-0.8.2.exe) - Linux: [Moontors-x86_64.AppImage](https://github.com/moontors/moontors/releases/download/v0.8.2/Moontors-x86_64.AppImage) - Ubuntu and Debian: [moontors_0.8.2_amd64.deb](https://github.com/moontors/moontors/releases/download/v0.8.2/moontors_0.8.2_amd64.deb) See [First launch](https://github.com/moontors/moontors#first-launch) and [Updates](https://github.com/moontors/moontors#updates).