v0.18.0

See where your tokens go.

0.18 helps you keep track: how many tokens your agents use and what that would cost, which terminals and servers are still running, and which files you've already reviewed.

📖 Full changelog: Mains 0.18: See where your tokens go

See where your tokens go

• A dashboard built around consumption. Settings → Dashboard's CLI tab reads the Claude Code and Codex history on your computer, so it covers sessions you ran in the terminal as well as in Mains. Pick a week, a month, or a year, and narrow it to one provider.
• Tokens and cost over time. A trend chart switches between tokens and estimated cost.
• Model by model. A table breaks usage down by provider and model — uncached input, output, cache reads and writes, and the API cost.
• Cache savings. See how much reading from cache saved compared with paying the full input price.
• What the numbers are. Costs are API-equivalent estimates based on LiteLLM's model prices, not your subscription bill; Sources & pricing shows which history folders were read and how prices were applied. Only token counts go into the report — your prompts and replies stay out of it.
• The Mains tab covers work done inside Mains: a daily token calendar, the tools your agents use most, the hours you're busiest, and how many sessions ended successfully.
• Claude usage limits. Settings → Claude shows how much of each usage limit you have left and when it resets, refreshed every minute.

Terminals that keep running

• Several terminals per workspace, each in its own tab. They keep running when you switch tabs or workspaces, so the dev server you started is still there when you come back.
• See what's running. When a terminal is serving on a port, Running servers in the session panel lists it with its process, port, and workspace. Click a row to jump to its terminal, or stop it right there.
• Hide without losing work. Hide terminal tucks the panel away and closes idle shells, while anything still running — a server, a build, a background job — keeps going.

Steer Claude mid-turn

• Queue and steer, now with Claude. Keep typing while Claude works and your message waits until the turn is done, or click Steer to send it into the turn that's already running.
• Nothing lost, nothing doubled. If Claude can't confirm it received a message, the message stays in the queue.

Mark files as reviewed

• Check Reviewed on a file in Review to collapse it and move on.
• Remembered. Your checkmarks, and which files you left open or closed, survive chats and restarts. If a file changes after you reviewed it, it opens again unchecked.

Also in 0.18

• Pick Codex's speed. Codex chats offer Standard, Fast, and Ultrafast, depending on what the selected model supports.
• A better document viewer. Open documents sit in tabs, with a toolbar for zoom and Save a copy. Markdown previews render embedded HTML safely, show images with relative paths, and follow footnote links.
• Approvals that stay explicit. When Claude marks a tool request as needing your answer, Mains asks even in bypass mode or for tools you've allowed before. The dialog starts on decline, can't be approved from a notification, and hides "always allow" when Claude rules it out.
• On your iPhone. Each chat's model, effort, permissions, speed, Plan, and Goal stay in sync between your phone and your Mac. Long messages and tool outputs load on demand, and the app has a new icon with light, dark, and tinted looks.

Smaller things

• Skill chips in messages you've already sent open the skill, just like in the composer.
• A turn's output files come from the agent's final reply, so files it only mentioned along the way don't show up.
• Subagents show the model and effort they started with, and a background task that stops without finishing reads Idle instead of looking done.
• When you steer Claude during a web search or fetch, the call completes with its real result instead of looking finished early.
• When part of an MCP tool's result is left out for size, the chat says so and keeps the readable text.
• No duplicate images in Atlas: the same image from several chats or uploads shows up once, and browser annotation screenshots stay with their chat.
• A page you move to Trash isn't saved again by a pending autosave, and unsaved edits are kept if you open it later.
• Context you add in the floating chat while a message is sending stays attached for the next one.
• Chat, browser, document, and Atlas tabs share the same header row.