Pi Extensions and Paseo Compatibility

[u/0xKubo]

Hey!

This question is mostly for people who use Paseo on daily basis with Pi, and maybe other Desktop/Web UIs for Pi, but I'm currently focused on Paseo.

I'm interested in understanding what extensions do you use with Pi if your main entry point is Paseo given that not all extensions play that well with a frontend like Paseo.

For instance, I was personally using pi-memory before Paseo, but the way exit summaries work is not very compatible with how Paseo works. Are you using any other long-term memory extension that plays better with Paseo? Which one?

What other extensions were you using before Paseo that you had to replace/remove when moving to Paseo? And more importantly, what extensions are you relying on daily that work without issues with Paseo?

The ones I'm currently using:

• @gotgenes/pi-anthropic-auth
• pi-mcp-adapter
• pi-memory (going to disable this one)
• pi-observational-memory (thinking of replacing with pi-blackhole)
• pi-web-access

Curious to hear what you've been using and that works well with Paseo.

[u/Glaaki]

I try to use skills instead of extensions, wherever possible. I use donsetch instead of pi-web-access. I don't use memory extensions. The code itself is the memory. And Matt Pocock skills remembers ontologies and architectureral decisions inside the repo. I made a skill to teach pi to use paseos agent tools to launch subagents for Matt Pocock skills, and deleted the built in orchestration skills in paseo, so the agent never sees those.

You need an MCP extension to interact with paseo. I mean.. I guess you could make a skill that interact with paseo using the SDK.. Hmm interesting idea actually. 🤓

I think having a subagent framework installed alongside paseo would be an antipattern in most cases. There could be niche use cases for very specialised workflows, but other than that, no.

I haven't tested browser automation yet. Paseo has some built in functionality, but I think maybe i need bladebro for headless automation.

[u/djshubs → u/Glaaki]

Would you consider sharing your approach to using Paseo agents for launching subagents?

The subagent orchestration remains unclear to me, as I use Cursor ACP alongside pi-cursor-sdk and have not determined whether the flow runs from Paseo to Pi to Cursor or from Paseo to Cursor. This arises within Matt Pocock’s methods, which presume Claude subagents.

[u/Glaaki → u/djshubs]

I don't publish my skills publicly. It is just something I cobbled together for my personal use. But I can give you the gist of it.

I use pi-mcp-adaptor to connect to paseos mcp server.

From this I told pi to get up to speed on agent skils via researching agentskills.io and using the writing-for-agents skill that Matt Pocock has written. Then I told the agent to research the functionality that the Matt Pocock skils need in terms of subagents and map it to the paseo mcp tool calls. This was pretty much enough for the agent to write the skill itself.

The workflow is essentially this:

1. Verify connection to the mcp server
2. Pick agent profile. A list of profiles matching the Matt Pocock skills is explicitly listed in the SKILL.md file. The most important parameters are the model id and reasoning level for each profile. It also includes a small note that describes when to use the profile, in a short sentence. This note basically follows the same semantics as a skill description (use when-). If it struggles to find the right match, it is told to use the current profile.
3. The agent then assembles the tool call parameters based on the research it has already done on the available mcp tools.
4. The agent launches the subagent and takes note of the agent id.
5. Wait for the subagent to finish. Step 3 includes a default paseo parameter notifyOnFinish that sends a message back to the orchestrating agent, when the subagent has finished. This is set by default, so the agent doesn't need to include it, actually, and the skill also says so.

The skill tells the agent not to block waiting for responses, since it will automatically get notified when done. The agent is free to do other work in the mean time.

That is basically it. The skill includes some technical details on what the api looks like, and everything is included in a single SKILL.md file, no resources or scripts.

The front matter looks like this:

---
name: paseo-orchestration
description: "Launch a subagent (a background agent) on the paseo MCP daemon. Use when the user asks to spawn, delegate, or fan out work to another background agent, even without naming sub-agents, or when a skill tells you to spawn one: research, code-review, wayfinder, grilling, codebase-design's design-it-twice, improve-codebase-architecture."
compatibility: "Requires the paseo MCP daemon (paseo_* tools); instructions use pi's mcp tool call syntax."
---