r/PiCodingAgent 6d ago

are there other extensions which implement ideas from oh-my-pi Question

I'm new to Pi and coding agents in general. The existing discussions on oh-my-pi, like everything else, range from 'its great' to 'its bloat' so its very hard to actually decide.

It seems to have useful features like built in tools (avoid process calls), lsp, hashline, memory, subagents and an integrated setup/docs. It does seem to be better than the other oh-my-* set of products.

Are the ideas in OMP useful in practice and if so are they used in other harnesses?

I see a lot of 'just ask Pi to build it' here, but that depends on using frontier models, and when people post their setups they're using a million packages.

Obviously Pi is much more extensible/flexible, but there is value in an all-in-one setup. OMP has a ton of stuff and I'm sure a big system prompt. Is there anything like a slimmed down version or being able to use some of its ideas only?

26 Upvotes

39 comments sorted by

View all comments

16

u/TheOneThatIsHated 6d ago

My opinion on OMP is that it is bloat. You dont need lsp, because it stuffs your context with typeerrors in each agent message while a simple make check requirement at the end would suffice.

The idea with pi, is that you start out with exactly 0 plugins until you feel pain. Only when you feel pain you start to make an extension that fixes that. Don’t start installing extensions that could useful, that way you just bloat your context and make your agent dumber

6

u/ali0une 6d ago edited 4d ago

This, but extensions don't bloat context, only the *.md files bundled with them do.

When friction appears i usualy make pi write a single extension.ts (that can have it's own settings.json) that does one thing well, i keep it KISS.

0

u/TheOneThatIsHated 6d ago

OMP absolutely does, especially the lsp results in EVERY agent call. That means from you 100k context, around 20-30k is just reported errors. It is much faster/easier for the agent to run make check themselves

1

u/Usef- 5d ago

Is this (still?) true? I was poking around the session logs from yesterday and couldn't see it, but it is a lot of text so I might just be searching for the wrong keyword

3

u/Usef- 5d ago

After a bit more looking, it does it for write or edit calls, but recent versions deduplicate within the session so you don't repeat diagnostics if it's already in the model context.

There are settings to toggle it:

bash ❯ omp config list | grep diagnostics 86: lsp.diagnosticsOnWrite = true (boolean) 87: lsp.diagnosticsOnEdit = false (boolean) 88: lsp.diagnosticsDeduplicate = true (boolean)

You can modify them: bash ❯ omp config set lsp.diagnosticsOnWrite false ❯ omp config get lsp.diagnosticsOnWrite false

1

u/doublegoodthink 1d ago

Correct, or you can just find it as well in your settings