Settings
Settings is a mode, not a page. Toggling the Settings cell in the title bar (or pressing ⌘,) swaps the stage’s occupant for the settings takeover — the roster and doors bar stay live around it, and toggling again returns you to whatever was on stage. Nothing opens in a dialog.
The takeover is a 196px section rail on the left and the active section’s body on the right. Rows use a small, fixed control set — toggle, select, tag, button — and changes apply in place; there is no save button.
The sections
Section titled “The sections”The rail lists nineteen sections in a fixed order. Models comes first because it governs what can run at all; Worktrees second because it governs how work lands; Permissions third because, with several agents running unattended, it is the highest-stakes screen in the product.
| Section | What it governs |
|---|---|
| Models | Which models the roster may run. Choosing one for a session happens in the command bar. |
| Worktrees | How an agent’s work lands — isolated checkouts and where they merge back. |
| Permissions | What an unattended agent may do outside its own worktree. |
| Project | This project’s own state — artifact publishing and removal. |
| Plugins | First-party integrations, one-time imports, and the registry. |
| Team | Seats, the invite code, and who is here right now. |
| Account | The signed-in account and its plan. |
| Integrations | Per-plugin settings for plugins that registered one — GitHub, Slack, and the registry live in Plugins. |
| Keyboard | Global shortcuts — bindings are read-only for now. See Keyboard Shortcuts. |
| Terminal | Which terminal app opens, and how session output reads. |
| Context | What gets injected into Claude Code sessions. |
| General | Application behavior and the first-run walkthrough. |
| CLAUDE.md | The behavioral contract Claude reads in every session. |
| Git sharing | Cloud team visibility for this project, plus the legacy git-mirror toggle. |
| Agents | Specialist subagents Claude can delegate work to — bundled, project, and personal. |
| Skills | Installed skills and the catalog of skills you can add. |
| MCP | Per-project MCP servers — enable, disable, and add new ones. |
| Guide | Workflow overview and the command reference. |
| What’s new | Latest releases and changes. |
A few worth calling out:
- Permissions is where you decide what an unattended agent may touch beyond its own isolated checkout — read it before running agents overnight.
- Git sharing: cloud team visibility is the standard sharing lane for
.mm/data. A legacy git-mirror toggle exists and defaults to off. - Plugins vs. Integrations: Plugins is where things get installed and connected; Integrations holds the per-plugin settings schemas for plugins that registered one.
- Account is where sign-in lives — and it is optional. Signed out, the app runs fully local (“Local only — team sharing off”).
Subviews, not modals
Section titled “Subviews, not modals”Flows that need more room than a row open as subviews inside the takeover body, never as dialogs: license entry, the upgrade flow, the account switcher, managing the artifact store, the skill catalog, and editing an agent. The one modal in the app is the confirmation for removing a project.
Next steps
Section titled “Next steps”- Keyboard Shortcuts — the shipped bindings.
- The Floor — the five-row shell settings takes over.