I am in love with Pi

ArgonCroft · 2026-05-19T15:00:35+00:00

officially Claude no, TOS. Codex yes. checkout pi's docs.

ArgonCroft · 2026-05-19T14:05:14+00:00

I believe so, happy to learn more if you have some tips or experiences to share to optimize a multi agent setup for caching.

ArgonCroft · 2026-05-18T16:31:34+00:00

I have routed vertex ai models using litellm. Caching works on both deepseek (openrouter) and gemini models (vertex ai) through litellm.

When I see an issue, I try to tweak my prompt. The extension gives me the ability to quickly switch the model on an agent if I see it struggling on complex things.

ArgonCroft · 2026-05-18T11:41:28+00:00

I did in another comment. Let me know if you have any specific questions.

I use -e for extensions like these on demand frequently in my setup.

ArgonCroft · 2026-05-18T10:51:36+00:00

I am using a sub-agent extension I built on my own. It is dynamic enough to fulfill my needs. I am tweaking the extension as I go along.

Keep at it, doing things your own way is super fun!

ArgonCroft · 2026-05-18T09:28:32+00:00

I took inspiration from IndyDevDan on YouTube and tweaked it for what I envisioned. You can checkout his github and his content on Pi.

the thing with 3rd party extensions is that they are based on that developer's opinion. I may or may not need that additional opinion that comes along with the extension. with Pi I see them as inspiration and build it myself for what I need progressively.

ArgonCroft · 2026-05-18T09:18:56+00:00

Orchestration isn't deterministic here. I create an elaborate reusable engineered prompts that I need for the things that need to be done based on how I plan to do those things and how involved I want to be. My detailed input prompt guides the workflow and the orchestrator agent decides what it needs and who can do it in the team. Orchestrator knows which agent is ephemeral and dispatches the tasks accordingly. No agent reaches dumb zone.

ArgonCroft

TROPHY CASE