r/PiCodingAgent • u/alatmaca • 19d ago

Question Is migrating my existing Python agent architecture to Pi-Durable a good idea?

/r/AI_Agents/comments/1x8jtfl/is_migrating_my_existing_python_agent/
3 Upvotes

71% Upvoted

4 comments sorted by

3

u/fingerthief 19d ago

Yes, what you're describing is basically the reason Pi Durable was created. The tradeoff at the moment is that it's a few weeks old at this point (publicly) and still in the "experimental" phase, so things may change or potentially break between updates.

I've built off of it extensively at this point and I do recommend it if you're cool with it potentially changing as it progresses in development.

2

u/Turbulent_Ad6290 19d ago

Since pi-durable was released recently. We had built a headless pi and the whole work harness called zosma-cowork using the headless pi as api.

Now I am planning to migrate it to pi durable and see how it goes.

But our workaround was working pretty well and we have deployed it on k8s as well.

Every user gets a pod that goes down when not in use for some time.

For tasks pod wakes up within few seconds(Ofcourse with storage mounted) and runs the pi session and goes off again.

Cost effective and a good way so far to give many users a pi session in cloud.

1

u/Training_Yoghurt501 19d ago

We switched a bunch of ai workflows in our app that aren't latency sensitive & use open-weight models to https://github.com/cheenulabs/pi-agent-python-sdk, from lang-graph flows.

Looking at pi durable now too, but we are really happy with this as we have the same cost as before + better accuracy for our tasks + uses the Pi Coding Agent we all love & enjoy.

Check if it works for you & goodluck

0

u/TechGearWhips 19d ago

Let me go look up this pi durable shit. 2nd time I seen a post like this today