Every Oz project runs through the same four core
surfaces. They work in sequence and they work in
parallel.
Plans
Describe what you want to build in plain language.
The Plans agent asks the right follow-up
questions, distills your input into structured
project documents (overview, data schema,
features list, environment variables), and hands
the plan to the rest of the agents to execute
against. No specs to write. No tickets to file.
Code Files
The workspace where the actual code lives. Every
agent operating on your project reads from and
writes to the same file system. Full context is
shared through an append-only log so no agent
operates blind. You can watch the code as it
gets written, edit anything by hand, or delegate
the next change back to an agent.
Deploy
Push what you built to production. Vercel,
Fly.io, your own infrastructure, or wherever
your project needs to live. Deployment is one
action. Environment variables, build
configuration, and post-deploy verification are
handled inside the platform.
Repair
When something breaks, agents self-diagnose and
repair. The platform monitors deployments,
catches runtime errors, and dispatches a repair
agent with full context of what changed. You do
not need to debug what the agents built. The
platform does.