Mooring 0.13.1
Two things that were failing silently are fixed — Coxswain refusing to start on some Macs, and cards with a long discussion never getting a summary. Both work now, and when Coxswain can't start it tells you why.
Fixes
In 0.13.1 we've fixed two things that were failing silently: Coxswain refusing to start on some Macs, and cards with a long discussion never getting a summary. Both work now, and when Coxswain can't start it tells you why.
Coxswain starts on every Mac
- Some Claude Code installs rejected the way Mooring launched them, so Coxswain could never start there at all — while terminal sessions on the same Mac worked fine. If Coxswain has never worked for you on a particular Mac, try it again.
- Updating Claude Code wouldn't have helped: two machines on the same version behaved differently.
- When something does go wrong you now get the reason in Claude Code's own words, rather than "Coxswain stopped unexpectedly." If it isn't signed in, for instance, it says so — which is both the diagnosis and the fix.
Long cards get their summary back
- A busy card's Summary sat on "No summary yet" however often you pressed ↻. The whole card was being sent to the on-device model, which reads about 4,000 tokens at a time and refused outright. It affected the cards with the most discussion — the ones where a summary is worth most.
- Long cards are now summarised from the title, description, acceptance criteria and the most recent comments. A card that genuinely can't be summarised now says so.
A card's Coxswain no longer restarts itself every 30 seconds
- A card window left open quietly killed and restarted its Coxswain session twice a minute. Asking a question after an idle pause failed too, until you closed and reopened the card. Both fixed.