Pi Daytona Chat
A coding agent where every conversation gets its own isolated Daytona sandbox, and every tool call is persisted and shown as a timeline.
What it is
Pi Daytona Chat is a systems-design implementation of a coding agent whose execution never touches the application server.
It separates a control plane (React and Convex: queries, mutations, queues and streaming subscriptions) from an execution plane in which every conversation thread is provisioned its own isolated Daytona workspace. Convex never runs user shell or filesystem work; it provisions sandboxes, streams turns in, and persists structured events back out.
01
Two-plane architecture
Control plane and execution plane are fully separated; the app server never executes agent work.
02
Full tool observability
Every tool call is stored with name, input, output, status and order, and surfaced in the UI as a work timeline.
03
Filesystem as artifact stream
The workspace is diffed before and after each turn; new or changed files attach to the message that produced them.
04
Allowlisted tools
Eight tools (bash, read, write, edit, grep, glob, webfetch, websearch) are exposed to the agent runtime.