Why
The first version of AgentOS showed that we need a simple and reliable way to define subagents. The next version must put this at the center so we can stop building one-off agents and instead build a system that works for many different tasks.
What
Build a basic MVP of AgentOS that can handle two clear workflows, using one shared subagent system:
- Product engineering: plan, build, and deploy a Next.js app to Vercel, and ask follow-up questions when needed.
- Email outreach: understand the user’s context, pick who to contact, write emails, show drafts if needed, send them, and summarize replies.
Success
- User says: “Build a roadmap tool.” → AgentOS builds and deploys the app.
- User says: “Message 30 people who might be interested in Ryo.” → AgentOS picks the right contacts, writes messages, sends them, and reports back.
- Both workflows run on the same subagent setup, showing the system works for many tasks, not just one.
Scope
- A simple website with a waitlist signup
- Full working version of the VM + subagent system, all running inside our folder structure, using an agent CLI (e.g., Claude Code)
- Feedback loop so tasks can update or correct themselves
- A single, clear .yml format for defining all subagents