Mooring 0.12.0

Talk to your backlog. Coxswain is a new window where you manage cards by conversation — find duplicates, refine a vague requirement, split something too big — with the cards it mentions rendered as real cards you can click. Alongside it: Mooring installs with Homebrew now, terminal links became things you can act on, and a long run of backlog, worktree and session fixes — including a freeze that could lock the app for minutes, and an undo key that could empty your backlog.

Coxswain — manage your backlog by talking to Claude

• A new window for the work around the work. Coxswain (Window ▸ Coxswain) finds duplicates, refines requirements, splits cards that grew too big, and answers questions about what's in your backlog. There are five ways to open it, each scoped to whatever you were already looking at.
• Its questions are clickable, and the cards it mentions are real. When Coxswain ends on a question, the answers appear as buttons under the reply — and a card it's discussing renders as a card, not as a ticket key in prose.
• Suggestions are jobs, launched from a menu. Instead of a row of chips inside the window, pick a job from the backlog header and it opens in its own window, seeded with that work.
• Closing a window doesn't lose the conversation. Reopen a job and the conversation is back; Clear Session is there for when you actually want a clean slate.
• It can look at Ready and In Progress at once — the scope menu ticks rather than picks, and unticking the last one gives you All back.
• One AI menu for your cards. The sparkle menu and the Coxswain menu are now a single menu. Tagging that Mooring did for you is no longer recorded as something you did.
• A Coxswain window could freeze the whole app for minutes. It can't now. Dragging the resize corner, or scrolling the transcript, could leave Mooring unresponsive for several minutes — the window stuck mid-resize as though you were still holding the mouse button. It recovered on its own, nothing crashed, and nothing was logged, which is much of why it lasted so long.
• Close Session ends a conversation and closes its window. Closing the window only looked like finishing — Mooring remembered the session and brought it back next time. Clear Session ends one but immediately starts a replacement. Close Session stops, forgets, and gets out of the way: clear to keep working, close to walk away.
• Chat bubbles fit their text and the window. "do them all" used to be drawn as a 420pt slab with three words in the corner, the same size as a 2,000-word triage above it — it now measures 83pt. Long replies use 75% of the window and track it as you resize.

Your backlog can't vanish, and deleting a card asks first

• A card now knows which project it belongs to. Previously that link could be cut by the app's own undo — and every view found cards by following it, so the backlog appeared empty while every card was still there, untouched. Views now match on the card's own stored identity, so the link can be cut and nothing you can see changes.
• Deleting a card asks for confirmation, and can't be undone. ⌘⌫ used to delete immediately and silently, and ⌘Z didn't bring the card back — it detached hundreds of other cards instead. Undo of a delete is now absorbed, doing nothing, and the delete itself asks first, naming what goes with the card: its comments, its History, and its worktree link.
• A backup no longer leaves cards out. Export collected a project's cards through that same link, so a detached card was silently missing from the archive — the safety net failing in exactly the case it exists for. It now collects by identity.
• A ticket keeps its number. MOOR-42 used to be recomputed by following the link, so a detached card quietly stopped having a ticket key at all. It's now stored on the card.
• Deleting a card now takes its attached files off disk straight away. A deleted card used to leave a readable copy of every file attached to it — its own and its comments' — in Mooring's Application Support folder, unreachable from the app but still on disk until the next time you quit and reopened, which could be days. Delete now means delete for the copies on disk too.
• Restoring a backup could quit Mooring instantly. Replace could close the app the moment it began writing — no error, no crash report, the window simply gone and the import half-applied — in four different ways, including a plain Merge with "remove stale projects" ticked. All four complete normally now.
• Renaming a project's ticket prefix updates its existing cards, and ticket numbers can no longer be handed out twice.

⌘Z does what it says

• ⌘Z can no longer undo things you never did. Pressing it a few times after deleting something could empty a project — not the cards, the project, and every card lives in one, so the whole backlog vanished from view at once. What it had reached was Mooring setting itself up at launch. Undo now skips anything you didn't do, and your own edits — status, priority, tags, marks — are unchanged.
• ⌘Z works again in a card window. Once you had typed a comment, the comment box kept the keystroke: thirteen presses in a row, measured, never reached the card. Posting a comment now hands ⌘Z back.
• Deleting a comment asks first, and can't be undone. Undo used to bring the comment back into the database but not onto the card, leaving it unreachable — so it is now absorbed and does nothing, and Mooring asks before removing a comment.

Mooring installs with Homebrew

• brew install --cask mooring-sh/tap/mooring installs the current release, and updates with brew upgrade. The cask checks the machine can actually run Mooring before installing it.

Terminal links you can act on

• ⌘-click a link to open it; right-click for its actions. Files, folders and URLs in any terminal tab are live. ⌘ on its own no longer opens the action menu — it was doing two jobs and they got in each other's way.
• The action menu waits to be asked for. Hovering a link no longer makes a menu appear by itself, and only links Mooring can actually resolve light up.
• Links at the end of a line stay put. A URL or path that wrapped no longer silently joins with the line below and offers to open somewhere you never saw.

The backlog

• Filter by several states at once. Click Ready, then In Progress, and see both. The state chips now behave like the tag chips beside them.
• Sort the card list by date, not just priority — created, last updated, or done — from a new sort control in the pane.
• A card you create is selected and waiting, instead of vanishing into the list; a filter that would have hidden it stands down.
• A selected card takes the keyboard. Card shortcuts no longer just beep after you've been typing in the search field — while prose keeps the caret, so Mooring won't pull focus out of a note you're writing.
• ⌘Z now undoes a card's tags, including the tag you just typed.

Sessions, and not losing them

• Quitting with sessions running asks first. ⌘Q shows what's still running instead of taking them down with the app, and File ▸ Close All Sessions… is a new, deliberate kill switch.
• Undo after closing a tab could end every session in the project. It can't any more — that was the worst bug in this release.
• Restarting Mooring no longer breaks MCP in running sessions. Your open Claude sessions keep their Mooring tools across an app restart.

Worktrees and marks

• A mark you set stays where you put it, and a card no longer closes itself because the merge check was comparing against the wrong branch.
• Start a worktree already marked — tick Auto against a custom state in Settings ▸ Worktrees, and the new-worktree dialog offers your states.
• Building in a worktree no longer makes Mooring burn CPU, and files an agent creates show up in the file tree straight away, even in a brand-new folder.
• The Mark As submenu stops vanishing while you reach for it.

For agents

• Agents can correct and remove comments on a card — manage_item gains edit_comment and delete_comment, so a wrong comment can be fixed rather than followed by a correction.
• list_backlog filters by tag, search and version, and now agrees with the backlog pane on what counts as visible.

Smaller fixes

• ⌘, opens Settings and ⌥⌘I shows the backlog — both shortcuts had silently done nothing, because the terminal engine was eating them.
• Coxswain works in a Mooring you opened from the Dock, not just one started from a terminal, and no longer offers to launch itself into a plain tab.
• A suggestion saved before this version could stop Mooring starting; it can't now.
• Labels on selected buttons are readable again — text on an accent-filled control is worked out from the accent.
• A card's History shows mark names instead of raw ids, including in rows recorded earlier.
• A worktree's recent questions no longer lag a command behind.
• Changing the terminal font size no longer leaves a link underline behind at the old character size.
• A reopened Tickets window no longer claims MCP isn't running, and restarting a conversation can't leave a stray Claude behind.
• The first-run "Choose Folder…" screen could come back after your projects were already set up — it read a setting the multi-root migration deletes. It now reads the projects themselves.
• VoiceOver says which tab you are in. A selected tab was drawn with a lighter ground and a slight lift, both purely visual, so every tab sounded the same; tabs now publish the standard selected trait, as Finder's and Safari's do.