Skip to content
Moontors

Moontors 0.8.4

Released November 9, 2026.

Moontors, the agentic development environment (ADE) for Claude Code, Codex, Gemini CLI and Grok Build. This release brings Settings and Profile with their tabs down the side, and the Configuration dialog, on cards; Configure for each agent from Profile, with no session; a new Add MCP server; a composer that keeps to one row; Archived read beside its list; Grok Build’s context window; and an account switch that says what it waits for.

What’s new:

  • Settings and Profile have their tabs down the page’s left side, each with its icon, or in a row over the page where it’s narrow, and a tab slides in, from the right for one further along and from the left for one before it, or shows at once if you’ve asked your system for less motion. Each of Settings’ tabs opens with its name and an ⓘ that says what it sets and whether it syncs, then its settings on a card, and a change that’s refused says why under the tab’s name. New Session’s agents and quick actions stand in two cards, side by side where the page has room, each agent by its logo, and the one Create session starts on is marked Default. See Settings.
  • Profile’s tabs each say what they hold at a glance: Providers how many of your agents are signed in, and Account your account’s email, or Not signed in. Account stands on cards, each sign-in method by its provider’s logo, or an envelope for your email and password. On Providers, each agent’s state follows a dot: green signed in, grey checking at start, blue and glowing while it installs, red where its install failed, and hollow signed out or not installed, as in the Android app’s Accounts. See Your account and Providers.
  • The Configuration dialog is on cards, in two columns where it has room, each with an ⓘ that says what it is and when a change to it applies, and a card on the agent’s tab folds by its heading. A card’s list stands about five entries tall, and a longer one scrolls within the card, the entry it cuts off fading out; past its end, the wheel or trackpad goes on to scroll the dialog. Once the agent’s tab lists more than twelve entries in all, a Filter tops it, keeping the entries whose name, description, command, value or source holds what you type. Status marks the mode (default) where it’s the default, as it marked the model, and shows your account on a card of its own, and Current session sums up what the session’s agent works with: its added folders and rules, then its MCP servers, skills, plugins, hooks, apps, subagents, instruction files and its own lists, each with how many it holds or how many of them are on, a row opening its part. What the running agent says of itself is under Reported by and the agent’s name. See The Configuration dialog and /status.
  • On Profile’s Providers, each agent’s card has a cog, Configure, which opens that agent’s own setup with no session: your MCP servers, skills, plugins, hooks, subagents and instruction files, its own lists, and the servers you added for All projects, the same in every folder. A switch there reaches every session of that agent, a running one at once where it can, otherwise from its next turn, and a server you add there is for All projects. What a project’s own files add, and what a folder’s trust holds back, show only in a session’s Configuration. Grok Build lists your setup through its own command line, so where Moontors hasn’t installed it yet, Configure installs it first. See From Profile.
  • Add MCP server is laid out anew. The transport is three choices: HTTP, where a new server starts, then Local command, then SSE, the older protocol. Beside the form, where there’s room, a guide to the transport you chose gives common shapes of its command or URL. A field says what’s wrong with it under it once you’ve typed in it and moved on, or when you press Add server, and Cmd+Enter (Ctrl+Enter on Windows and Linux) adds the server. Paste a server’s settings anywhere in the form and it fills in, one server at a time, and a whole command line pasted into an empty Command splits into the command and its arguments. Once it’s added, the agent’s tab brings the new server into sight. See Adding an MCP server.
  • The composer’s toolbar stays on one row, on your computer and in the Android app. Where it has no room for every setting, the last ones move, from the end, into More settings (⋯), and come back as the composer widens; its menu has a line for each, with its icon, name and value, which opens the same choices as its button. The permission mode never moves: where even its words have no room, it shows as its icon alone. On your computer, they folded into one Settings menu before; in the Android app, fast mode, the output style and Daybreak each have their own button now, where they shared one. See The composer.
  • Archived reads beside its list: click a session to read its transcript beside the list where the window has room, the newest until you choose another. The arrow keys move from row to row, the transcript following, Enter moves into the transcript, and Escape goes back to the list, then out of Archived; in a narrow window, the transcript shows alone, with Back to the list. The list groups its sessions under Today, Yesterday, This week, This month and Older, each row by its agent’s logo, with a search over titles, projects and agents (never their transcripts’ words), All agents where the archive holds more than one, and a count. Reopen is on each row, and Delete in its ⋯ menu. In the Android app, the archive groups and searches the same way, Delete is under a row’s ⋯ or a long press, and where the screen holds two phone-wide sides, an archived session opens beside the list. See Archiving and deleting.
  • With Grok Build, Context window (/context-window) is a session setting where the session’s model lists more than one, as Grok 4.7 does on a grok.com sign-in: 256K or 500K tokens, on your computer and in the Android app. It starts at the model’s own window, marked (default), and Grok Build takes a change at once, even mid-turn, the context ring counting against it from then on. Grok Build lists no windows on an API key, so it isn’t offered there. See Session settings.
  • When a sign-in to another account waits to switch a session, its header, on your computer and in the Android app, and Configuration say all the while which account it switches to and what it waits for: the turn under way, its background tasks, by their count, or other work the agent still runs. Background tasks, such as a wait for CI, hold the switch too, and the session switches as soon as the last one ends. While they hold it, Switch now asks first, naming the tasks it stops: Keep waiting, or Stop and switch, which stops them and switches, never cutting a turn. Signing in again to the account the session still runs on, before it has switched, calls the switch off, its background tasks still running; signing in to a third account switches to that one, waiting the same way. See Providers.
  • Don’t wait for me is a switch in the mode picker, which stays open as you turn it, so you see it change, and while it’s on, the mode’s button shows a no-entry mark after the mode, on your computer and in the Android app. See Don’t wait for me.
  • A model change’s row in the transcript names the model and its effort, on your computer and in the Android app: one left at the model’s own names the default it ran at, as Moontors knew it then, and a model that takes no effort names none. See The model picker.
  • Once Moontors starts again, a Claude Code session’s fast mode and output style are asked once more and show an ellipsis meanwhile; if Claude Code can’t answer, they show what your Claude Code settings set, else fast mode off and the Default style, where a session restored or branched could show an ellipsis with nothing chosen. See The model picker.
  • A newer version you open while the one before still works in the background, as after you install it yourself, takes over once the work under way ends, and until then a line under the header says a newer Moontors is ready and what it’s waiting for. There’s nothing to do: it goes by itself once the newer version has taken over. See Updates.
  • On your computer, a transcript’s rows keep to their places as a long transcript first opens and as a reply streams in, where for a moment one could be drawn over the next.
  • On your computer, an agent’s code block draws its four rounded corners whole, and its focus ring when Shift+Tab reaches it.
  • A plugin your claude.ai account syncs to Claude Code is listed once in Configuration, where it could show twice.
  • A screen reader lists New Session’s Agents and Quick actions under the tab’s name in Settings, and an agent’s usage limits on Profile’s Providers under the agent’s name.
  • On moontors.com, the footer and the notices say the sign-in providers’ names and logos belong to their owners, as the agents’ and clouds’ do.

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

See First launch and Updates.

© 2026 Moontors. All rights reserved.

Moontors is an independent agentic development environment, not affiliated with or endorsed by Anthropic, OpenAI, Google, xAI, Amazon, Microsoft, Apple or GitHub, or the makers of Conductor, Emdash, Orca, Paradev (Superset), Vibe Kanban, opcode (Claudia), Google Antigravity, T3 Code, Herdr, Paseo, Cursor, VS Code, OpenCode or any other tool this site names.

Google Play and the Google Play logo are trademarks of Google LLC. Apple and the Apple logo are trademarks of Apple Inc., registered in the U.S. and other countries. App Store is a service mark of Apple Inc., registered in the U.S. and other countries. All other product and company names and logos, here and in Moontors' apps, belong to their respective owners.