Dogfooding pxpipe: findings, improvements, and upstreaming ideas

[alteixeira20]

Hi @teamchong, I've been heavily using pxpipe and maintaining a fork while fixing issues I hit in real coding-agent workflows.

Main pain → solution areas so far:

• Compression could reduce coding quality → added a conservative coding-safe path that keeps instructions, tools, live code/results, and recent history as text, with fail-open behavior and repeated-read protection.
• Provider routing/capabilities were brittle → moved toward provider-neutral routing, capability handling, caching, and safer fallbacks.
• AGY could work while bypassing pxpipe → added proper Antigravity routing so supported inference traffic goes through pxpipe while auth/discovery/control-plane traffic remains untouched.
• Quota/auth failures could trigger repeated wasted calls → added failure classification, cooldowns/circuit breaking, model discovery, and doctor diagnostics.
• Dashboard state could be misleading → separated configured models from models currently allowed by the safety profile and added clearer bypass/compression reasons.
• Dense image rendering can lose exact information → working on lossless Unicode handling, better preservation of identifiers/values, and adaptive rendering instead of relying on one density profile.

I'm still stabilizing and testing the fork, so I'm not looking to open a large PR.

Once it's ready, my plan is to compare everything against current main and split useful changes into small, independent one-root-cause PRs.

Does this direction make sense to you, and how would you prefer I upstream the work — small PRs directly, discussions/issues first for larger changes, or another approach?

[teamchong]

Thanks a ton for all of this work!
My time and resources are pretty limited right now, so I'd like to keep process to an absolute minimum.

Don't waste extra effort painstakingly slicing up PRs, just open them directly in whatever logical chunks are easiest for you.
Feel free to skip discussions and issues entirely if you don't think they're necessary.

Really appreciate you driving all of these improvements

[alteixeira20]

Okay, that sounds great and will benefit progress of the project a lot, thanks for the feedback, once I got a stable version I'll open the respective PRs and try to keep information has dense as possible!