1.3.6
Your tools come with you
The MCP servers you rely on locally now work in every workspace. Import the ones you already have — plugins included — and the agent can reach them wherever it runs.
New
- DesktopDeclare an MCP server once in Settings → Connections and every workspace you open has it. Until now the tools that make you effective on your own machine were simply missing in the place the work happens.
- DesktopImport from this machine takes the servers you already use, including the ones your plugins provide, so you do not retype a single command. It copies the setup only — no key or token is ever read off your machine.
- DesktopServers that need a browser sign-in get one. You sign in once and it works on every device you use, phone included.
- DesktopA key you set is encrypted before it is stored and is delivered only to the machine running your workspace. Nothing can show it again — not Padar, and not you.
- EngineA project can ship its own servers in its .berth/actions.toml, so a repo brings its tools with it and nobody sets them up twice. Your own servers still win where they overlap.
Improved
- DesktopA control beside the composer says which servers the agent reached and which it could not, with the reason. A server that failed to start used to be missing with nothing said about it.
Fixed
- DesktopThe agent carries on the same conversation after it restarts. It was quietly beginning a new one, so it forgot what you had been working on.