Practical overview
When it fits
Use Warren when coding-agent runs need to continue unattended, repeat on a schedule, survive failures or be visible beyond the person who started them.
Who it is for
- Individual coding-agent operators moving work off a terminal.
- Small, trusted engineering teams sharing one deployment.
- Operators retaining control of code, credentials, compute and run history.
Documented uses
- Run coding-agent workloads in isolated workspaces.
- Start, monitor, steer, cancel, recover and clean up agent runs.
- Track spend, token use, events and outcomes.
- Push agent changes through Git and optionally create pull requests.
- Operate coding-agent workloads on self-hosted infrastructure.
Requirements & limits
Warren is self-hosted software, not a hosted SaaS. The repository is public and licensed under MIT. The documented quickstart uses macOS or Linux and installs Bun and the Warren CLI when missing.
- Warren is built for operator-controlled compute rather than terminal-only sessions.
- The core delivery guarantee is a pushed workspace branch; pull-request creation is configurable.
- The current distribution includes Pi and Claude Code adapters.
- The current boundary is one deployment for one operator or trusted team, with one bearer credential and no named users, RBAC or per-user attribution.
- Kubernetes deployment is likely compatible, but the supplied material does not include manifests or a tested installation path.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Install Warren and start the control plane
Reach a running Warren installation on a fresh macOS or Linux machine.
Before you start
- A fresh macOS or Linux machine.
- A browser for the setup flow.
- One credential requested by
warren up.
Steps
Run the command below.
curl -fsSL https://warren.run/install | shRun
warren up.Let Warren detect the machine’s sandbox runtime, request the remaining credential and boot the server.
Use the browser UI to connect GitHub, choose a repository and dispatch the prefilled starter run.
Expected outcome
A running Warren server with the browser UI opened and a starter run ready to dispatch.
Guide limitations
- The documented quickstart covers installation and startup, but does not specify the full runtime topology or all later configuration options.
Compare options for AI coding assistance
These projects document a common task and share a project role. This is a source-based comparison, not an execution benchmark or a guarantee of interchangeability.
| Project | Documented purpose | Platform | Access and requirements |
|---|---|---|---|
| Warren | Run coding-agent workloads in isolated workspaces. | Cloud, Docker, Self-hosted, Server | Warren is self-hosted software, not a hosted SaaS. The repository is public and licensed under MIT. The documented quickstart uses macOS or Linux and installs Bun and the Warren CLI when missing. |
| Nasiko | Detect supported coding-agent CLIs and inspect their versions and configuration locations. | CLI | The documented discovery command requires no account. Reporting and routing require an active control plane and valid login. The Docker Compose path requires Docker Engine with Compose V2; the CLI requires Rust 1.85 or later. |
| Paritok | Route coding-agent requests through a local proxy. | Self-hosted, Server | The project is public and licensed under Apache-2.0. The documented self-hosted quick start uses Python 3.11 or later and Ollama. |
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 30 September 2026
- Original website title
- jayminwest/warren · Official homepage title · retained in its source language