agent-orchestrator/website/content/docs/plugins/runtimes/index.mdx

24 lines
1.1 KiB
Plaintext

---
title: Runtimes overview
description: Where the agent process runs — tmux on macOS/Linux, plain child process everywhere.
---
The runtime is where your agent's terminal actually lives. Two options ship:
| Plugin | Best for | Binary needed |
|---|---|---|
| [tmux](/docs/plugins/runtimes/tmux) | macOS / Linux default. You can attach interactively. | `tmux` |
| [process](/docs/plugins/runtimes/process) | Windows, Docker, CI-like environments | — |
<PluginGrid>
<PluginCard name="tmux" logo="tmux" href="/docs/plugins/runtimes/tmux" description="Each agent gets its own tmux window; attach with `ao session attach`." />
<PluginCard name="process" logo="windows" href="/docs/plugins/runtimes/process" description="Cross-platform child process. Required on Windows." />
</PluginGrid>
## Choosing
- If you can install `tmux` and you want to occasionally drop into a live session, use `runtime: tmux`.
- If you're on Windows, in a container, or just want fewer moving parts, use `runtime: process`.
Both runtimes expose the agent's terminal to the dashboard's xterm.js session — attaching via tmux is a *bonus*, not a requirement.