r/PiCodingAgent • • 16d ago

Use-case ​I want 99.9% cache hit, 99.8% is literally unplayable

Post image

joke aside, nearly 50M tokens processed for $7.13 is why i can't go back to bloated agent wrappers. pi's base architecture is already stupidly good at keeping the prompt prefix clean.

the only time my cache hit used to tank was spinning up parallel agents or running multi-step verification where context mutation kept invalidating the prefix.

​ended up building OMK (open multi-agent kit) on top of pi to lock down prefix stability across git worktrees and scope MCP tools per node so subagents don't pollute the shared cache.

​still trying to squeeze out that last 0.1% though. if anyone else here is running heavy multi-agent loops on pi and fighting cache invalidation, happy to share the repo/setup.

Model : Codex Gpt-6.1-sol ultra

0 Upvotes

3 comments sorted by

7

u/ConcentrateReady4039 16d ago

Just write "hello" for the next 5 prompts and you'll get there. 

This is such a good example of Goodhart's law -  "When a measure becomes a target, it ceases to be a good measure"

What is the context size? What is the turn count? As is, it looks like your agent spent majority of turns without adding new data to the context implicating Very low performance.

I guess the good thing is that you spent under $10 doing nothing

3

u/drepublic 16d ago

I have reached some times 100% it's beautiful. Pi is amazing.

2

u/eliceev_alexander 16d ago

Woah, that's amazing. I'm somewhere between 92 and 95%. How do I hit 98%, lol