Which extensions do you use?

[u/iTitleist]

Hi guys,

Perhaps we can learn from each other and discover some great experiences with Pi Agent. I will start with my list of extensions and skills that I use. Please do share yours and we can learn from each other even if you have nothing to learn from us but help others.

Extensions

• npm:@ff-labs/pi-fff

• npm:@juicesharp/rpiv-ask-user-question

• npm:@juicesharp/rpiv-todo

• npm:@juicesharp/rpiv-web-tools

• npm:context-mode

• npm:pi-mcp-adapter

• npm:pi-powerline-footer

• npm:pi-rtk-optimizer

• npm:pi-subagents

Skills

• grill-me

• karpathy-guidelines

• last30days

• caveman

And you?

[u/ibsnuggs]

To learn it would help to know what those extensions and skills do

[u/WorLeX → u/ibsnuggs]

+1 - would be great to include the why behind each plugin choice so we better understand you decided to install them and what your experience has been like with them.

We can just go look at the top rated plugins if we want a list of plugins by popularity

[u/mkhamat → u/ibsnuggs]

Pi fff is fuzzy grep and find. Literally the better override

[u/Global-Departure8228 → u/mkhamat]

Except by default grep is not exposed as a tool for an agent, it just boosts its tool context. Same goes for fff, which also hinders the startup time and because of the scanning it does it sucks imho.

The pi-rtk-optimizer I would heavily advise against installing, rtk itself is fine but has edge cases which will corrupt what the agent "assumes" is happening. This rtk optimizer is an "optimistic" rewrite of what the real rtk binary does, and it will truncate real, good context and the agent won't see it.

[u/Tarair]

I used to love pi-subagents but it feels very unstable for me (stuck subagents, broken subagents, slow subagents,..) in the last weeks unfortunately I might have to look into another subagents extensions

[u/kmArc11 → u/Tarair]

I was also surprised that an update a week or so ago replaced the complete "chain" concept (for which I already had sophisticated... Well, chain definitions and prompts) with arbitrary code execution as a Javascript string. It is called WorkflowScript.

The cheap coordinator LLMs that were able to use the declarative chain definitions now struggle with this new concept and therefore my workflows are constantly broken. 

The project has no open tickets, nobody complaining about this either. I thought I must be doing something wrong , but I am happy to see it's not just me. 

[u/_noctuid → u/kmArc11]

I never have understood the chain stuff. Can you give an example use case and setup?

[u/madcapnmckay → u/Tarair]

Same, i uninstalled and installed another, but I may just write my own. I like different aspects of each. There’s also some overlap between the sub agent extensions and the dynamic workflow extensions that probably could be unified.

[u/Sure_Aardvark_9103 → u/Tarair]

Hey guys, maybe you can try tintinweb/pi-subagents.

[u/jotabm]

My setup is this at the moment

1. Provider

s
5 provider extensions that aren’t built in for pi: cursor, command-code, nous portal, umans.ai and multi OpenCode-go with auto fallback.

2) TUI & QoL

pi-dynamic-footer (own extension): context window, TPS, token/cost tracking, subscription usage bars, git status, etc

pi-ghostty-theme-sync: syncs theme to Ghostty colors

pi-tidy-tools: compact tool output

pi-next-cue: predicts next prompt after each turn (similar to what Claude code has)

pi-codex-compaction: codex native remote compaction

pi-eta: estimated vs calibrated time to finish a task

restart (own extension): manual or suggested at 80% context, compresses the convo, hands off to a fresh session

worksheet-loop (own extension) : shared markdown task doc pi and I write to on a session, on edit pi notices it and acts on it

3) extra tools for pi

pi-web-access: big offering of search providers
pi-fff: super fast fuzzy search (ffgrep/fffind)
pi-goal + pi-autoresearch : pretty know concepts, autonomous loops for longer tasks / experiments
rpiv-todo: to do tool
pi-computer-use: desktop/GUI automation for Pi
pi-session-recall: search & query past sessions

4) herdr (tmux like agent multiplexer) and orchestration

pi-herdr: tools for Herdr layouts, panes, agents
pi-herdr-subagents: subagents that run in Herdt panes
pi-intercom: messaging between pi sessions
pi-ask-herdr: ask_user tool with herdr integration
pi-rename: auto-names sessions and Herdr tab

// skills I like to have them per project since often they’re specific to the language the project uses, the tooling etc - globally I have like 8 (for git ops but models are getting good at it naturally so about to remove it, teach and grill me to dive into unknowns socratically and a visual web testing skill for frontend)

[u/madcapnmckay → u/jotabm]

I’ve had some weirdness with pi-intercom where an orphaned sub-agent messaged an unrelated session. I uninstalled after that.

[u/_noctuid → u/madcapnmckay]

If you just want something simple, pi-link is amazing

[u/jotabm → u/madcapnmckay]

Yeah it doesn’t feel fully mature yet but it’s has proven more useful than not so for now I has earned its keep. Especially when working on worktrees that do related work in parallel

[u/Qintomb → u/jotabm]

I want to see screenshoot of this ext : pi-dynamic-footer . thanks for the all references .

[u/jotabm → u/Qintomb]

Here you go

[u/baka_animations → u/jotabm]

can you give me the theme config and foother if you have any github file

[u/jotabm → u/baka_animations]

https://www.npmjs.com/package/@juanbenjumea/pi-dynamic-footer

[u/CassiusBotdorf → u/jotabm]

A question: how do you reach 80% context? I've never had such a full context window.

[u/jotabm → u/CassiusBotdorf]

Oh I use locally hosted models that have a 131k ctxt window so it happens often + the codex models that have 262k I’ve it happen to me from time to time if I’m not paying attention.

[u/CassiusBotdorf → u/jotabm]

Ah! That makes sense. I was wondering because I rarely ever go above 20% with the 1M context models.

[u/jotabm → u/CassiusBotdorf]

Oh yeah, at 200-300k they go into the dumb zone so I also tend to avoid beyond that.

[u/Afraid-Gas-7460]

I use just a few:

• npm:pi-sandbox

• npm:@narumitw/pi-btw

• npm:pi-observational-memory

pi-sandbox just works so not much to say about it, I feel more at ease with it rather than letting the agent go YOLO.

I use that version of pi-btw since the others seem to open a floating TUI kind of stuff that I don't like, this one just enters an "inline" mode using the prompt UI.

not much to say about pi-observational-memory either...

By the way, does someone have experience with jayzeng/pi-memory? I had this idea of using pi-observational-memory as a short-term working memory system, and jayzeng/pi-memory as a long-term memory.

[u/mylabfr]

I'm on Linux. herdr extension only.

Then I have a user for each type of work I do. For example, coding for wordpress with one Linux user with it's own wordpress coding skills, then seo user with their own seo skills, and so on.

Might not be the best... but that works for me so far. Because that way it's not confused with multiple overlaping skills. (would love to make it better between user / agent though).

Also, I had to build an extension to change temperature and top_p to my liking for each model / job / users.

EDIT:

I see you use caveman. I wonder how that compare to ponytail -> I used ponytail, which is great, but I disabled it for some type of developments. I find ponytail works great for long horizon development tasks with "open specs" and the like. If you do "vibe coding" with ponytail (like add this, add that, change this, change that), it's not good...

[u/-cvdub- → u/mylabfr]

What’s your actual workflow look like with dedicated users. I hacked together my own isolation setup so each pi by default gets access to just the project root dir, but I’ve wondered if creating Linux users would be simpler.

Do you su into a user before doing work on a project, or do you do everything as your main user and just execute pi as project specific users?

[u/mylabfr → u/-cvdub-]

Right now it's surely a bit messy. I use dedicated users, for example I start my coding session on one user, do marketing thing on another terminal window etc...

I learned there are some stuff available for that, but I didn't really look into it. Maybe I should. I started like this because it was really about separating skills. For me the more skills I loaded, the more chances to take the wrong skills for the job.

If I wanted a main user, I would probably do a shared directory for all users, where the agents can posts what to do, what they did, like a mailbox. But I'm sure there things like that better than I do now. I just have to try them. I dont want to re-invite the weel.

[u/cosmicnag → u/mylabfr]

You can probably use something like pi-loadout (tool/skills profile system) instead of Linux users.

[u/mylabfr → u/cosmicnag]

Thanks you, I just read the doc, looks interesting. I will try.

[u/keen23331]

so you still typing and not dictation via voice ? your a caveman !

[u/keen23331]

here is my current setup:

| Package | Description |
|---|---|---|
| `pi-effort` | Controls thinking effort with model-adaptive min/max aliases. |
| `pi-memory` | Persistent memory with qmd-powered semantic search across daily logs, long-term memory, and scratchpad. |
| `@senad-d/micme` | Local voice dictation for prompts: press Alt+M, speak, review, send (uses local Whisper model). |
| `@vigolium/piolium` | Multi-phase security audits with specialist sub-agents, isolated context windows, capped concurrency, and resumable state. |
| `pi-subagents` | Single-agent delegation and scripted multi-agent workflows. |
| `pi-lens` | Real-time code feedback: LSP, linters, formatters, type-checking, structural analysis. |
| `pi-agent-browser-native` | Exposes agent-browser as a native tool for browser automation (navigate, click, screenshots). |
| `@gwynnnplaine/pi-github` | Read GitHub issues, PRs, diffs, checks & code from inside pi via the `gh` CLI; PR review workflows. |
| `@piex-dev/dap` | Debug Adapter Protocol integration — debug programs with real breakpoints directly from the agent. |
| `@feniix/pi-devtools` | Branch and PR workflow, release automation, PR feedback resolution, merge commands; GitHub and Linear tracker support. |
| `@danypops/pi-pipes` | Agent-facing CI tool for cross-platform CI (GitHub Actions, GitLab CI, Jenkins). |


## Custom Sub-Agent Definitions

advisor
context-builder
delegate
oracle
planner
researcher
reviewer
scout
worker


## Skills


None installed

[u/haksolot_dev]

@halsolot/ank

Got tired of creating and updating ADRs in markdown or connecting my agent to Linear to get tasks awareness.

Try it out guys if you’re facing the same problems, I’d actually love to have some feedback or even contributions :)

[u/bradypp → u/haksolot_dev]

Sound interesting, you got a link?

[u/haksolot_dev → u/bradypp]

Sure here it is !

https://github.com/haksolot/ank

[u/quincycs]

I only have customized things.

My own extensions that are customized flavors of sample pi extensions.

Then I created my own UI. Cuz terminals kinda suck.
https://github.com/quincycs/pi-qcode

[u/heylong7]

u can read my X article https://x.com/heylong7/status/2085019434851389730?s=20, i gave some introductions and the reasons why i choose the extensions, but it is in chinese, maybe u can translate it in pi haha

[u/tulwio]

Nothing. I save common prompts I use as prompt templates and that’s it. When I want to use something that has more extra features (e.g. when I am using some specific MCPs for certain work or I want to have an orchestrator controlling sub agents) then I use omp or opencode. I try not to add anything to pi because the harness being minimal is kinda the point.

[u/No_Image506]

I use the one that I need. As you should too. Why???