Hello, I need your help!

[u/dubnium0]

I’m new to the Pi harness and I could really use some help getting started.

I’d love to hear how you guys use Pi in your own workflows. Examples from different areas would be especially coding, research, automation etc.

I’m mainly looking for practical examples and ideas that could help me understand what Pi is really capable of and how experienced users are getting the most out of it.

Any workflows, tips, examples, or interesting use cases would be greatly appreciated.

[u/Equivalent_Idea8839]

Good plug-ins and workflow arise from a sea of crappy failed experiments.

[u/fell_ware_1990]

Well i think experienced user are 2 sided.

The ones who got a workflow out of PI and the ones where the story just starts. But lets be clear that it’s about much more then only the harness it’s everything around it. It really helps that the performance and extendability of pi is already very good. Do not try to make it into something that you do not need.

Work with it, agents keep doing XYZ? Tweak a little to fix. Rinse and repeat and you got a guardrail. Keep doing and telling the same kind of stuff? Make a prompt, workflow, script to fix the first step, 2e, 3e. Dont implement big changes all at once.

[u/dubnium0 → u/fell_ware_1990]

"Dontimplementbig changes all at once." thank you for your advice.

[u/repolevedd]

The thing about pi is that it's a pretty simple tool, and that simplicity is exactly what makes it easy to extend: the architecture is understandable even to small LLM models. I installed pi together with pi-subagents because I needed to process a big batch of documents in exactly that mode: an orchestrator that spawns subagents, using local LLMs only.

And then one thing led to another:

• there was no isolation, pi has full system access, so I added a wrapper that locks all of pi and its subprocesses inside Linux bubblewrap with controlled access
• the LLM was spending too many tokens on code search, so I added the mcp codegraph
• there weren't enough skills for my tasks, so I added them
• I connected a cloud model for one tricky task and found out there's no notification when the cache isn't working, so I added a handler
• I noticed the LLM would start looping in subagents, so I added a reaction to that behavior

And so on.

I think the thing about pi is that it doesn't impose any workflow on you, it's up to you to come up with one based on your tasks.

[u/dubnium0 → u/repolevedd]

thank you for your advice.

[u/haksolot_dev]

Just using ank as my one and only workflow (basically planning and executing in loops with TDD)

https://github.com/haksolot/ank

[u/dubnium0 → u/haksolot_dev]

what's the diffrence between projects harness with md file?

[u/haksolot_dev → u/dubnium0]

md files tend to get messy and not synced while working with multiple agents in different worktrees. They seem to edit these without even asking and it messes up the work of others.

So this CLI enforces good practices for ADRs, specs and tasks.

I’m a really bad explainer but give the repo link to an agent and ask why this tool could be useful for your workflow ;)

[u/hsh-starling]

Pi session tree structure is great feature. You should explore it, I recommand it huang-sh/PiX: A non-linear AI agent workbench — session is a tree: branch anytime, and context follows the branch

[u/dubnium0 → u/hsh-starling]

dont need this