All stories
Paseo Ecosystem Community reports

Paseo 0.14 gives individual coding agents their own plugin tools

Plugins can target tools to selected agents and contribute MCP servers when sessions open, without recreating the conversation.

Sources (4)

Why now The October 29 version 0.14.0 release ships per-agent tools and session-open MCP contributions, a concrete change beyond the repository's latest activity timestamp.
Paseo's author-published desktop and phone interface showing coding-agent sessions, a conversation and a code diff.
Project-published interface mockup linked from Paseo's English 0.14.0 README. It illustrates the app layout, not a reproduction of the new per-agent plugin tools or an AITrending test session. Source: Paseo / getpaseo

A coding agent can now receive a plugin tool because of its role, rather than every agent receiving the same toolbox. Paseo’s October 29 version 0.14.0 release adds tools targeted to individual agents and lets plugins contribute Model Context Protocol servers when an agent session opens.

Paseo is the development environment around the agents. Its local daemon manages sessions, while desktop, mobile, web and CLI clients connect to that daemon. The tagged README lists Claude Code, Codex, Copilot, OpenCode, Pi, Antigravity and Muse Code providers; users still need their chosen agent CLI installed and configured with its credentials.

Tools follow the agent

The merged implementation describes plugin authors defining a tool with a validated input schema and a callback running in the plugin process. A session-open hook can select recipients by labels, provider, workspace, title or agent ID. Its example gives a note tool to a labeled agent while leaving an unlabeled agent without it.

Installing, stopping or reloading a plugin makes relevant sessions stale. According to the implementation notes, an idle session reopens before its next prompt; a busy agent finishes its current turn before applying the change at the next idle prompt. An explicit SDK reload can interrupt a running turn, so these are different operations.

The companion MCP change contributes servers at launch without saving them into the agent’s persistent configuration. Name collisions fail the session open, and providers without MCP support remain unsupported. The maintainers describe Linux integration tests with deterministic provider adapters; those tests did not exercise every external provider binary or client platform.

A useful extension point with host access

The README offers desktop downloads or the @getpaseo/cli npm package for a server installation. Plugins can be installed from the registry with paseo plugin add owner/slug, or from Git or a local directory. They run with access to the daemon machine and connected clients, making plugin trust a practical requirement.

Paseo is Apache-2.0 licensed. That does not include the costs of an underlying model subscription, API provider or speech service. The release also adds collapsible completed turns and local speech-model downloads, with voice mode now opt-in. AITrending reviewed the release and implementation descriptions without independently testing the workflow.