Docs
Build an agent harness from the parts.
Start with a saved setup or the TypeScript SDK. Choose runtime and compute, edit instructions, configure tools, and inspect real execution. The source and guides show where each part connects and where support differs.
- 1. inspect a template or the SDK source
- 2. choose runtime, model, and compute
- 3. edit persona, instructions, and context
- 4. configure tools and scoped service keys
- 5. run, inspect output, and refine your setup
Choose your path
Configure in the app. Extend in code.
Start
Inspect a curated setup, save your own configuration, or import createMux from the SDK.
Customize
Choose a compatible runtime, model, and provider. Edit memory documents and configure the tools your task needs.
Reuse
Keep configurations in your account, copy or export memory as Markdown, and adapt the MIT-licensed source. Full harness export and public sharing are not implemented.
Next step
Open the part you need.
Edit instructions
Write the role, rules, and context your agent needs.
Connect tools
Review entries, installation commands, and service requirements.
Connect providers
Supply your own model and compute credentials before launch.
Dashboard actions require an account. Provider capabilities, credentials, and charges still apply.
The Worker system
Keep the Worker.
Swap the machinery.
Give your Worker a job. Its identity, memory, files, and schedules stay with it as you change the runtime, model, tools, or cloud provider.
Your Worker is more than a chat session.
Reduced motion
Scroll to explore the engine. Every layer connects to your Worker.
The durable coreYour WorkerSame identity. Saved context.
Agent runtime
Sandbox provider
Models & routing
Tools & skills
Agent runtime
Choose how it works.
- Claude Code
- Codex
- Hermes
- OpenClaw
Sandbox provider
Choose where it runs.
- Daytona
- E2B
- Sprites
- Vercel
Models & routing
Connect the intelligence.
- Anthropic
- OpenAI
- Routers
- Custom API
Tools & skills
Give it the right abilities.
- Skills
- MCP servers
- CLI tools
- Connections
The Worker keeps its saved state; each provider supplies its own capabilities. Migration transfers files and restarts managed work—not live process memory.
Give it a responsibility.
Set the job, connect its tools, and define its permissions.
Run it on your terms.
Choose a runtime and provider without rebuilding the Worker.
Come back to its work.
Review saved files, logs, and results from the dashboard.