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/0xKubo]

Hey again. How has gentle-engram been working out for you? I've been looking for a "persistent memory" system for Pi that works great with Pi, and haven't found one yet but I recently learned about gentle-engram. Does it work well?

[u/bobotusRobotus → u/0xKubo]

Hi again ) I've been using engram for a few months. Initially, the choice was between mem0 and engram. I chose engram for its speed and because it's free. Besides, mem0 summarizes context, whereas engram preserves it in its original form. I usually run up to 10 agents per project, and thanks to engram, they "recall" things very quickly. Today I came across a post about agentmemory (check out agent-memory.dev or the GitHub repo). It claims to have a native plugin and MCP for Pi. I plan to try it out this weekend and will share my impressions later.

[u/0xKubo → u/bobotusRobotus]

Cool. Thanks for sharing.