v0.1.45

Highlights

• 🔌 Connections: MCP servers ready to use. Tools → Connections lists a catalog of servers that are already configured: Blender (build and edit 3D scenes), Playwright (a real browser for pages that need JavaScript) and Documents (web pages, PDFs and Office files as Markdown). "View" shows what each one needs on your computer, the exact command it is started with and what every tool does; "Install" adds it, and you give it to an agent in Agents → Tools. A connection is configuration, not code: the server's version is pinned and only changes when you press "Update".
• 🏷️ Each MCP tool says what it does. A server's configuration can now classify its tools (toolRisk: looks up, reads outside content, changes something). Tools that only read run freely, and only the ones that act wait for your approval once the task has read third-party content; before, the second call to any unknown server was held. The catalog's connections come classified, and the card tells you when a server publishes a tool nobody classified.
• 🔁 MCP servers recover on their own. They start connecting when the app opens instead of on the first task, one that failed (the application was closed, docker was still starting) is retried on the next task, and one that lost its link is restarted. No more editing the configuration to wake a server up.
• ⚙️ Each worker starts only the servers its agents were given, and changing one server no longer restarts the others.

What's Changed

• mcp: a server's config says what each tool does (toolRisk), servers warm up at start, failed ones are retried and lost ones restarted by @TraX22 in #106
• connections: a catalog of ready-made MCP servers (presets) in Tools; workers start only the servers their agents use by @TraX22 in #107

Full Changelog: v0.1.44...v0.1.45