# Moontors 0.4.0

Released October 10, 2026.

Moontors, the agentic development environment (ADE) for Claude Code, Codex and Gemini CLI, now lets you answer what an agent asks, right where it asks, and read a plan as a document before you approve it.

What's new:

- When an agent asks you a question, it shows as a card in the transcript: one or more questions as tabs, each option with its description, and a preview where the agent gives one, your own answer under Other, and notes. Claude Code's questions and Codex's questions in Plan mode both use it.
- A plan offered for approval comes with Accept this plan?: approve it into the mode to go on in, or keep planning with your feedback. Claude Code, Codex and Gemini CLI plans all work this way.
- Plans open in their own Plan view, beside Files and Diff, and stay there for the rest of the session. Select any passage to comment on it; your comments go back to the agent as feedback. A red dot on the Plan button says a plan is waiting.
- An MCP server's own forms, and pages it asks you to open, now show and are answered in place, with Claude Code and Codex, instead of being refused.
- Typing a new message while a plan waits sets the plan aside and sends your message.
- With Gemini CLI, an MCP server that asks to sign in no longer leaves the session stuck: it's turned off for the session, with a notice, and the session goes on without it.
- The context used is a small ring beside Send: hover it for the figures, click it to compact where the agent can. Cards show the same ring.
- The turn's time shows when you hover its reply, and a button there copies the reply.
- Replies and your messages use the transcript's full width.
- Files opens with its top folder already open.
- Skills synced to your claude.ai account run as your own, and Claude Code's /deep-research and /plugin-authoring now say what Moontors does with them: the first runs where your account offers it, the second stays in Claude Code's own terminal.
- Claude Code's status messages (thinking, long-running commands, hooks, command list changes) no longer show as "unrecognized events", in new sessions and old ones alike; a hook that fails says so.
- A board card scrolled away and back shows the same lines as before.
- A switch you changed in an agent's configuration (Gemini CLI's tools, Claude Code's sandbox, Codex's memories and experimental features) now stays as you set it after Moontors restarts or updates.
- Moontors' Claude Code keeps its skill syncing inside Moontors' own folders, never in your own skills folder.

The macOS and Windows builds still aren't signed, so each asks once before it opens, and macOS updates through its download page for now. 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.4.0-arm64.dmg](https://github.com/moontors/moontors/releases/download/v0.4.0/Moontors-0.4.0-arm64.dmg)
- macOS, Intel: [Moontors-0.4.0.dmg](https://github.com/moontors/moontors/releases/download/v0.4.0/Moontors-0.4.0.dmg)
- Windows: [Moontors-Setup-0.4.0.exe](https://github.com/moontors/moontors/releases/download/v0.4.0/Moontors-Setup-0.4.0.exe)
- Linux: [Moontors-x86_64.AppImage](https://github.com/moontors/moontors/releases/download/v0.4.0/Moontors-x86_64.AppImage)
- Ubuntu and Debian: [moontors_0.4.0_amd64.deb](https://github.com/moontors/moontors/releases/download/v0.4.0/moontors_0.4.0_amd64.deb)

See [First launch](https://github.com/moontors/moontors#first-launch) and [Updates](https://github.com/moontors/moontors#updates).