Agents & the control plane
Behind the loop is a small team of agents and the control plane that coordinates them. You interact with the team by typing; this page explains who’s actually doing the work.
The product-manager agent
Section titled “The product-manager agent”The PM agent is always on. Its job is to stand between your intent and the builders:
- It turns your plain-language ideas into concrete, scoped tickets.
- It watches the state of your project and proposes sensible next steps.
- It keeps the work coherent — so the project grows as a product, not a pile of disconnected changes.
The PM proposes; it never ships on its own. Every proposal waits at the approval gate.
The builder agents
Section titled “The builder agents”When you approve a ticket, builder agents implement it. They:
- write the code for the feature,
- provision the Cloudflare resources it needs (databases, Durable Objects, scheduled triggers),
- commit the source to your GitHub repository,
- and deploy the result to a live URL.
The control plane
Section titled “The control plane”The control plane is the part Typillar owns and runs: the orchestration that routes your request to the PM, holds the approval gate, dispatches builders, and records what happened. It coordinates the work but does not host your product or store your data — those live in your accounts. See What you own.
Think of the control plane as the office and the agents as the staff. The office schedules and supervises; the actual product is built and kept at your address.
Where inference happens
Section titled “Where inference happens”The agents reason and write code using a model — and that model runs on your side: Cloudflare Workers AI or your own provider key. The control plane decides what to do; your infrastructure provides the thinking and the running. See Models & API keys and Zero inference on our servers.
The part Typillar uniquely owns
Section titled “The part Typillar uniquely owns”Plenty of tools cover one slice — a tracker for tickets, an assistant for code, a platform for hosting. Typillar owns the hand-offs between them: intent becomes a ticket becomes reviewed code becomes a deployment becomes history, without you stitching the tools together. Owning the whole loop is what lets a single sentence end at a live URL.