Toren documentation
Toren is an open-source durable agent runtime: long-running agents in your own cloud.
The docs follow Diátaxis: learn by doing → solve a task → look something up → understand why.
Start here
| I want to… | Go to |
|---|---|
| See it work in 10 minutes | Quickstart |
| Define my own agent, tools, subagents | Defining agents |
| Orchestrate parallel work and iteration | Workflows & waves |
| Gate dangerous actions behind a human | Approvals |
| Run agents on a cron schedule | Scheduling |
| Trigger runs over HTTP from anywhere | HTTP API |
| Deploy into my AWS account | Deploy to AWS |
| Trace and monitor runs | Observability |
| Look up a command or config key | CLI · agent.yaml · Workflow API · Event catalog |
| Understand how durability actually works | Durability & replay |
| Understand the system's shape | Architecture |
The design rationale behind these guarantees is summarized in Durability & replay and Architecture.
Honest status of these docs
| Area | Status |
|---|---|
| Quickstart, guides, concepts, CLI/config reference | ✅ written, matches shipped code |
TypeScript host API (@toren-run/core as a library) | ✅ written; full typedoc still to come |
| HTTP intake API (runs, status, events, approvals) | ✅ shipped, see the guide; sessions and SSE streaming shipped too |
| Troubleshooting / FAQ | ❌ gap, collect from first external users |
| Versioning & compatibility policy | ✅ shipped |
| Hosted tier and BYOC (a control plane for teams that want the ops handled) | 🗓 planned; the open-source runtime stays complete and nothing moves behind them |
| Examples gallery beyond research-crew | ❌ gap |
Client SDK (@toren-run/client), env declarations, environment profiles | ✅ shipped |