Comment by taw1285
3 hours ago
It looks like this product uses pi-agent directly (https://github.com/cloudflare/cloudflare-os/blob/main/plans/...). How come Cloudflare is not using their homegrown Agents SDK / Think / Flue harness for this? I am asking genuinely as I am evaluating a harness to build my agent platform.
Flue is actually also built on Pi. We are big Pi fans at Cloudflare.
Cloudflare OS uses pi-agent-core, but not pi-coding-agent. pi-agent-core, at least the way CFOS uses it right now, is more of an LLM API compatibility layer than a full harness. All the tools and things like compaction are implemented by CFOS itself.
The code was actually using ai-sdk (from Vercel) up until a few days ago, when I switched it over to pi-agent-core.
Why doesn't it use Think? Mostly because Think actually didn't exist yet when I started writing this, and the designs diverged in a way that made retrofitting hard. The CFOS harness does a few unusual things, like tracking the entire state of the filesystem as the conversation progresses using Yjs (a CRDT), so we can actually rewind the state to see what the agent saw at any particular point in time.
I would actually like to delegate more to Pi, because I don't think CFOS should be in the business of thinking about how to implement compaction or to optimize editor tools for each agent. But I'm not really sure if it'll be possible without giving up some cool things about the CFOS harness, so we'll see.