What a Kubernetes warm pool cannot prewarm for a stateful AI agent
A stateful AI agent warm pool should prewarm runtimes, then bind the existing disk, tenant identity, and final credentials atomically at claim time.
Blog
Notes from building a cloud AI agent.
Engineering writeups from running plori: agents that each get a persistent computer, a real disk over FUSE, and a bill that stops when they sleep. Measured numbers and production incidents, not launch announcements. For what the product does, see the docs.
The workflow engine said OK after a failed step
An RPC acknowledgement can be OK while a workflow step fails. The durable terminal record, not the transport ACK, must define the execution result.
Why we put a server between our AI agents and JuiceFS
JuiceFS CE enforces --subdir, quotas, and ACLs in the client. Our clients are untrusted AI agents, so isolation lives in a server in front.
443 dead FUSE mounts wedged kubelet: a production postmortem
How 443 dead FUSE mounts wedged kubelet teardown and starved a node, plus the 60-second janitor that fixed it. With the nsenter and /proc/mounts traps.
We moved JuiceFS metadata from Postgres to Redis and file ops got 7x faster
A production JuiceFS migration: metadata moved from Postgres to Redis, create+rename 22ms to 3.2ms (~7x). Durability config, RAM ceiling, dump/load steps.
Every post is also available as plain Markdown: request it with an Accept: text/markdown header, or append .md to the URL. Agents can start from llms.txt.