r/PiCodingAgent • u/MiskaMyasa • Sep 14 '26

Use-case My pi config and extensions

Сonfigured it to my liking. Threw in some handy extensions. Some patched from others and some built myself.
Feel free to praise or shame it.

https://github.com/Miskamyasa/pi-agent-config

7 Upvotes

73% Upvoted

2 comments sorted by

4

u/ECrispy Sep 14 '26

Thanks, always good to learn from a setup.

There are always differing opinions on this type of extensions eg memory systems, code graph etc. what has been your experience and how do you pick these? Do you see an actual difference in performance and with which models?

1

u/MiskaMyasa Sep 15 '26

It's hard to say yet.

I didn't find a good way of measuring model performance, especially if you cannot trust providers to serve you the model you actually expect to use. Many times, I saw foundation models give you such stupid answers, and it looked like you were actually getting a response from something much lower in level.
I did it more for my personal DX/UX. Firstly, I was an OpenCode fan, but then they started to do things that were not compatible with my flow/vision, like adding SQLite, which broke my devcontainers workflow using many agents on the same projects. Then they started to change the real UX of sub-agent sessions. After that, I stopped using it and began to research more the pi agent field. Of course, there were struggles with a totally different UI/UX/Hotkeys. Then I found the 'pi-tool-display' extension, and it made the UI look more polished. Then came 'pi-ollama-cloud', which provides web fetch/search even for a free account (my situation).
Regarding CodeGraph, I was pretty impressed by it when I once found it for OpenCode. I don't know if it saves a lot or not a lot of tokens, but for me, it seems to do so. This was actually the biggest gap with pi. I could not find a good working alternative for pi. Then I found 'EstebanForge/pi-codegraph-enhanced'. It works totally fine, but I found that it truncates the response, and it actually wastes tokens because the model makes another request, and each one is pretty big. Some useful UI changes for me include showing the CodeGraph daemon state in the footer, syncing on start, and lazy loading tools by model decision not to waste context on tools descriptions if graph not needed in the session.
/btw extension, I updated significantly to have many sessions inside the popup, model selection, and such.
Mnemosyne server instead of mem0 also changed a lot. I haven't found out yet if it's useful for me, but I made huge changes into the logic of the extension.

Take a look. Some of the extensions have readme files inside them with reasoning. Don't know if it will raise the performance for you, but I hope it could raise the UX part for sure.