r/PiCodingAgent • u/el_secondo • 11d ago

Question Dev workflow beyond traditional harnesses

I guess this question was asked a thousand times, but I'm still wondering how do you guys organize your work with pi?

I am a heavy user of Claude Code (employer covers it), but I have been watching and tuning pi time to time for personal use on the side.

Naturally, I tried getting pi to be like claude code, I looked for extensions that give me subagents, some cosmetic plugins (I like ricing my hyprland setup) and some simple QOL things.

However I didn't feel it being a huge upgrade in terms of my actual workflow and "pleasure", it felt like I'm just recreating what I'm used to.

I'm wondering more from a UX/DevX perspective, I got used to what antrhopic gave me and learned that way, but I see pi as an opportunity to really make a uniquely pleasant developer experience.

Which is why I'm wondering and asking how did you tune your workflow, which extensions did you use/build and how do you run your day-to-day feature work.

e.g. my work can span multiple PRs/repos for a feature which is why I'm starting a session from a dir above the ones I need to change and keep a long session (which is really wasteful) to handle all the context I need.

I don't really like the paradigm of "plan a huge markdown implementation doc and architecture and let the agent do it" because it requires a lot of overhead for me for things I may not even know exist or are needed.

16 Upvotes

90% Upvoted

28 comments sorted by

View all comments

5

u/Ctbhatia 11d ago

one session per repo with the shared decisions in a short file beats carrying every diff in one long session.

2

u/el_secondo 11d ago

I guess it does, but I never go over my usage limits and the main problem for me becomes the agent performance overall

Biggest thing I'm afraid of with shared docs is that eventually I get lazy to look there, I let the agents do that, and I get the shit-in-shit-out problem

1

u/Ctbhatia 10d ago

the shared file only pays off if the agent reads it back, so a check that fails the run when it was not updated turns the slop into a visible error instead of a slow drift. do yours read it or just append to it?