---
title: "What's new in cc-moss · Changelog"
description: "Every cc-moss release in plain words, newest first: what each version lets you do, from the first release to today."
canonical: "https://cc-moss.larrykoo.com/changelog/"
last-updated: "2026-11-14"
lang: "en"
---

Changelog

# What’s new, version by version.

What each version lets you do, in plain words. For every last change, the full technical notes are in [CHANGELOG on GitHub](https://github.com/larrykoo711/cc-moss/blob/main/CHANGELOG.md).

## 0.3.12 · Restoring a session from the picker opens it even when tmux was slow to answer, and after a rename the terminal tab shows the new name first.

November 14, 2026 Latest

-   When a starting session couldn’t tell which tmux session it was in, it used to wipe out what cc-moss already knew, so the picker had nothing to open after a restore. What’s known about the same window is now kept.
-   After you rename a session, the terminal tab switches to the new name first, so the two never briefly disagree.
-   A few automatic checks that failed now and then are fixed, so new versions go out steadier and sooner.

## 0.3.11 · After you update cc-moss, its daemon and the menubar app reliably start again, and the checkup finds Claude Code where it’s usually installed.

November 14, 2026

-   An update could leave the daemon off when the old one hadn’t quite finished shutting down, while install said it was updated, so Moss went quiet until you started the daemon yourself. Now install waits for the old one to go and says it’s done only once the new one is running.
-   Right after an update, macOS sometimes refused to open the menubar app, so it stayed closed while install said it had restarted it. Install now tries again for a few seconds and tells you plainly if it still can’t.
-   The checkup (cc-moss doctor) no longer says Claude Code is missing when it’s installed: it now looks for it the same way sessions are started.

## 0.3.10 · Moss no longer waits on Claude Code’s questions, what you say to it goes first, and your session list stays tidy.

November 11, 2026

-   Moss could sit on a Claude Code warning or the “trust this folder” question for days while your messages showed Sending…. Now it gets past them, and when it really can’t, the Moss page says what it’s waiting on and offers a button to open its window.
-   When session updates pile up, what you say to Moss goes first. Older updates are merged, stale ones are skipped, and each one says how long ago it happened.
-   A session Claude Code forks in the background gets its own name (with -2) instead of the original’s, and a session that closed without a word from you is no longer listed as stopped.
-   A session Claude Code compacted while it sat idle no longer looks busy, so a queued restart goes ahead, and a session you pick up after restarting your Mac isn’t mistaken for a stopped one.

## 0.3.9 · Finding sessions by what was said works while the index is first built, and it keeps less and masks more.

November 6, 2026

-   While the index was first being built, a search used to fail and the panel showed nothing. Now it shows what’s indexed so far and says the search didn’t finish.
-   Commands you run with ! in a session, and what they print, are no longer kept in the index. It’s built again once after the update, which clears what was kept before.
-   More kinds of keys, tokens and passwords are masked before anything is stored, and a deleted session’s words are overwritten in the index file.
-   Turning “Let Moss search conversations” on and straight back off now really leaves it off.

## 0.3.8 · Can’t remember a session’s name? Search for something said in it and find it.

November 6, 2026

-   When nothing in a name or note matches your search, the panel lists the sessions where it was said, under “In what was said”, each with a short piece of the conversation. Archived sessions count too. It all happens on your Mac, and keys are masked before anything is stored.
-   To have Moss find sessions this way, turn on “Let Moss search conversations” in Settings › Moss. It’s off unless you turn it on, since the bits Moss finds go to the model.
-   Settings › Moss now opens Moss for you and shows Moss’s folder in Finder. The first time, a small dot and a short tip tell you what Moss can do.
-   A session you just started can be restarted or restored right away, Moss hears about a session that was killed, and a question you just answered in the terminal no longer pops up again in the menu bar app.

## 0.3.7 · Sessions Claude Code runs in the background take one row, with the right status.

October 30, 2026

-   In newer Claude Code, opening another session with /resume hands both sessions to Claude Code to keep running in the background. cc-moss didn’t recognize them: one conversation showed up as two rows with mismatched names and status, and renaming one row renamed the other. Now each conversation takes one row, shows as running, and Open takes you into it.
-   While a conversation is still running anywhere, cc-moss won’t start a second copy of it, so two copies never write to the same conversation.
-   The daemon and the menu bar app no longer read Chinese session names as underscores, so the checkup stops reporting names as out of sync.

## 0.3.6 · Sessions you started before Claude Code updated itself can still be ended and archived.

October 25, 2026

-   After Claude Code updated itself, sessions still running the previous version couldn’t be ended and archived, restarted in place or moved into tmux. cc-moss now recognizes Claude Code’s own earlier versions, with every other check kept.
-   A session waiting to be brought back no longer shows the default ~/.claude under its name, which looked like the session’s folder. Only a settings folder you set yourself is shown, labeled “Settings: …”.
-   The website’s search endpoint for AI assistants now turns away oversized requests, and the site stops deploying if a dependency has a known vulnerability. The cc-moss program itself is not affected.

## 0.3.5 · Restore exactly the session you picked, and never start one in a system folder.

October 23, 2026

-   Bringing back, restarting or moving a session into tmux keeps its original settings source. If it is still there it is used directly; you only choose when it is missing or broken. Older sessions with no recorded source ask whether to use the default settings or a folder you pick, without changing your global settings.
-   The app, the picker and Restore all bring back the exact session you picked, one at a time, so another session with the same name is never restored instead. If a session changed in the meantime, you are told, and it doesn’t count as restored.
-   Sessions can no longer start in /, your home folder itself, system folders or configuration folders like ~/.claude; Documents, Desktop and Downloads still work. jarvis always starts a new session and adds a number when the name is taken, while claude runs as usual with a folder check first.
-   /status and /usage show their output in the Moss panel again, and the “Session restored” note goes away once you use the session.
-   Back up the session registry before upgrading: older versions can’t write the upgraded data, so reverting the app alone isn’t enough.

## 0.3.4 · Choose the new provider’s model and pick up where you left off.

October 21, 2026

-   Apply the model chosen in your provider settings and keep the same conversation, without sending your last task again. A busy session waits until its turn ends; you can cancel before the restart begins.
-   API problems, such as an unavailable model, get their own explanation instead of looking like a settings change. The panel won’t keep suggesting the same failing model or quietly try other models.
-   A restart waits for the old session to exit. If that can’t be confirmed, it stops instead of starting a second copy. Rebuilding a terminal pane needs your separate approval; older leftover sessions aren’t cleaned up automatically.
-   Bringing back or restarting a session shows one progress indicator and one result, with technical details tucked away. Sending the command no longer counts as confirmation that the session is back.

## 0.3.3 · Moving into tmux just works, and there's one cc-moss in the menu bar.

October 20, 2026

-   Sessions forked from another one, or that went through /clear, now move into tmux with one click too.
-   Compaction no longer swaps a session's folder for a temporary one, so bringing it back or moving it into tmux doesn't fail when that folder is gone.
-   An app you put in Applications is updated where it is; if there were two copies, the extra one goes to the Trash and the menu bar shows one cc-moss.

## 0.3.2 · When there's a new version, cc-moss tells you.

October 20, 2026

-   When a new version is out, a bar on top of the panel says so: See what's new shows what changed, and Update installs it. Mo mentions it too, once per version.
-   The first time you open the panel after an upgrade, it shows what the new version brings, just once.
-   Moss can now find archived sessions and ones closed in the last 30 days, not just today's.

## 0.3.1 · Old sessions put themselves away. New providers, same conversation.

October 20, 2026

-   Sessions that ended and sat untouched for 30 days are archived on their own. Bring one back with a click, or have Moss clean up: it asks first, and the conversations go to the Trash.
-   Switch API providers with a tool like cc-switch and most sessions, Moss included, use the new one from your next message. The few that need a restart are marked, and restart in place, same conversation.
-   A live Waiting on you card on the Moss page: answer every session that's waiting, all in one place.
-   When bringing back, restarting or archiving doesn't work, the panel says why in plain words, and Ask Moss to Fix It is one click away.
-   Typing with a Chinese input method, Return picks the word instead of sending half a sentence.

## 0.3.0 · Sessions get on with it, and Moss moves in.

October 19, 2026

-   New sessions get to work without stopping for your OK at every step. Want them to ask? Flip one switch.
-   When a session asks you to pick an option or wants your OK, answer from the panel or Mo. No terminal needed.
-   Meet Moss, a Claude Code that cc-moss keeps running in the background. Chat with it, and it keeps your sessions in order.
-   A daily checkup: Moss fixes what it can, and asks before it brings back or ends a session.
-   The panel gets a side rail: Sessions, To Do and Moss. Pin the sessions you care about; search understands abbreviations.

## 0.2.2 · Every session carries its own buttons. Permissions, on one page.

October 18, 2026

-   Point at a session: rename, send a message and open sit right at the end of its row.
-   A new Permissions page in Settings: what's missing, what it's for, and a button to allow it.
-   If an update turns Accessibility off, the panel tells you, instead of the shortcut going quiet.
-   Picking a folder for a new session is smoother, and leaving Shortcuts too quickly no longer closes the app.

## 0.2.1 · Sessions open as tabs. Every shortcut on one page.

October 17, 2026

-   Sessions open as tabs instead of a pile of windows, in Ghostty, iTerm2, WezTerm and more.
-   A new Shortcuts page: the key for the panel and the short names you type in a terminal, all in one place.
-   Settings look quieter.
-   The Accessibility step no longer gets stuck after an update.

## 0.2.0 · cc-moss moves into your menu bar.

October 17, 2026

-   A menu bar icon that changes with your sessions: busy, waiting for you, stopped.
-   Double-tap Control for the panel. Type to search, Return to open, one click to bring stopped sessions back.
-   When a session needs you, a notification or Mo tells you. Once, never both.
-   Mo: a little friend in the corner of your desktop. Quiet, everyday or lively, your pick.
-   A welcome sets everything up in about a minute.

## 0.1.1 · A tidier picker.

October 16, 2026

-   A session's menu and notes open right beside it, not at the bottom of a tall terminal.
-   Messages from other sessions show their words under Last message, not Claude Code's markup.
-   Slash commands too: just what you need to see.

## 0.1.0 · The first release: sessions that survive crashes and restarts.

October 16, 2026

-   Use Claude Code as usual. Every session is noted for you.
-   After a restart or a crash, one command brings every interrupted session back to its conversation.
-   Type t in a terminal to see every session. Return to jump in.
-   Leave a note on a session: what it's doing, where it stopped.
-   In Chinese and English, on macOS and Linux.

[Get the latest](https://cc-moss.larrykoo.com/#install) [Full technical notes on GitHub](https://github.com/larrykoo711/cc-moss/blob/main/CHANGELOG.md)
