The situation
You have the product idea, but the first prototype still needs task state, progress, approval, schedules, files, and recovery.
← All reference builds
First-party Reference App
Awaken Pilot
Give Pilot a Mission. Keep the work in one Session.
Pilot keeps the product surface thin: a Mission becomes an Awaken Session and a Project chooses the Deployment. Users see the plan, progress, files, approvals, and result without a second task engine underneath.
Best for: Agent product teams that want the shortest path from product UX to durable execution.
Local reference build · public source pending
First useful result
Run one bounded Mission in Plan or Execute mode, then review its progress and result in the same Session.
Product shape
Create a thin Agent application
Your application keeps
Product copy, Mission interaction flow, acceptance criteria, and UI projections.
Awaken provides
Agent, Deployment, Session, Run, events, files, tools, policy, Worker, Sandbox, and recovery.
Try this path
Build the smallest useful version first.
- 01Start with one Mission and one visible acceptance criterion
- 02Interrupt or approve it once, then confirm the same Session continues
- 03Keep only the product projections your users need
What is available today
Check the status before you invest more.
The build is currently local. An external team cannot reproduce it independently until a pinned public revision is available.
Read the implementation decisions and failure modes →- Tested
Execute and Plan paths share one Session log.
Where to check: Pilot web and API test suites
- Tested
Approvals, budgets, Skills, MCP, subagents, artifacts, and schedules use Awaken-owned contracts.
Where to check: pnpm check
- Live gate pending
The real-stack acceptance protocol includes interruption and recovery; its live result is not published yet.
Where to check: docs/real-stack-acceptance.md