Mooring 0.4.0

Claude can now drive Mooring from inside a terminal, and the app stays calm under heavy git and file-system activity — two CPU "storms" that could pin a core are gone.

Claude can drive Mooring (built-in MCP server)

• Mooring ships a built-in Model Context Protocol server, so Claude running in a Mooring terminal can drive Mooring directly — capture the window, read and create backlog items, and list or create git worktrees with a seeded agent.
• Screenshots work from inside a terminal session because Mooring takes them itself: grant Screen Recording to Mooring once (previously tmux silently swallowed the permission).
• Off or read-only by default, all gated in Settings ▸ MCP — separate opt-in toggles for screen capture, backlog writes, and workspace actions (creating worktrees / spawning agents).
• Backlog items an agent creates are tagged mcp, so you can find and bulk-remove them.

Calmer under load

• The git pane no longer pins a CPU core during active development. Background file churn in ignored folders (build output, DerivedData, nested worktrees) — written constantly by builds and agents — was retriggering a full working-tree diff on every write. The pane now reacts only to real edits and git state changes.
• Expanding a large folder in the file tree no longer pins a CPU core. The tree renders as one flat, virtualized list, so a file-system change that doesn't alter the visible files redraws nothing instead of re-laying-out the whole expanded directory.
• Each open repository now drives a single shared file-system watcher feeding both the file tree and the git pane, instead of two — one fewer kernel watch per open repo.

As always, Mooring updates itself — you'll get this automatically. Please report anything odd.