Mooring 0.10.0

When your organization blocks Mooring's MCP tools, Mooring now tells you why — and what to do about it — instead of sending you into a restart loop that could never work. Plus: the terminal link menu points where you're actually pointing.

Know when it's an organization policy, not a dropped connection

• On a Claude for Teams or Enterprise account, an admin policy can block Mooring's MCP server — and until now Mooring couldn't tell that apart from an ordinary dropped connection, so it told you to "restart the session to reconnect." Restarting can never clear a policy block, so affected users were stuck in a loop with nothing to act on.
• Mooring now works out which of the four blocking rules applies — a denylist entry, an allowlist that doesn't cover Mooring, a fixed managed server set that omits it, or a policy that rejects the flag Mooring registers with — and says so. The window status-bar advisory names policy as the cause and hides the Restart Session button, because restarting cannot help.
• Settings ▸ MCP gained an "Organization policy" section that names the rule and, where a configuration change would actually fix it, shows the exact entry to send your administrator with a Copy button. For a denylist there's nothing to copy, so it tells you the entry has to be removed instead.
• Mooring only diagnoses — it asks Claude Code itself which rule applies rather than second-guessing, and it never edits your Claude configuration to work around your organization's policy. When it can't determine whether policy is involved, it says so rather than guessing.

Terminal polish

• The link menu points at the character you're pointing at. Hovering a link used to pop its action menu up at the middle of the link — on a long path, that could land it a long way from your pointer. It now anchors to the cell under the cursor, for hover-and-wait, ⌘-hover, and right-click alike. The link's underline still spans the whole link.