The control planefor agents.

Trigger from Slack, Linear, GitHub, or your own webhook. Ryven spins up an isolated sandbox, runs Claude Code, opens a CI-green PR, and reports back where you started.

Get started Read the docs

A control plane, not another chatbot. Ryven sits between your team’s tools, your repos, and your sandboxes. Triggers come from wherever you already work — Ryven owns the boring middle and ships a reviewable PR back to you.

Trigger from anywhere

Slack today; Linear, GitHub issues, webhooks and a REST API next. One control plane — every signal lands in the same queue.

Run many in parallel

Every task gets its own ephemeral Docker sandbox — no shared filesystem, no cross-contamination, no babysitting.

CI is part of the loop

Ryven watches your PR’s checks, reads the failing logs, fixes them and pushes again — up to three retries before pinging you.

Runbook

From any trigger to a green PR.

One operational loop, five steps. Every task Ryven runs goes through exactly this pipeline — nothing hidden, nothing magic.

Trigger from anywhere

Mention @ryvenin a Slack thread today. Linear assignments, GitHub issue mentions, webhooks and a REST API are next — every channel lands in the same queue.

Spin up an isolated sandbox

Each task gets a fresh node:24-bookworm container. No shared filesystem, no leaked secrets, destroyed on completion. Setup commands, system prompt and scoped env vars come from a checked-in ryven.json.

$ docker run --rm -it node:24-bookworm
$ git clone github.com/acme/api
$ pnpm install && pnpm db:migrate
$ claude-code --system "$RYVEN_PROMPT"

Stream every tool call to the dashboard

Every read_file, edit, and shell command Claude Code makes inside the sandbox streams over SSE to a task page you can open in any browser. No polling, no “is it done yet” — you watch it work in real time.

Fix expired token handling in auth middleware

acme/api · 8a2f1c4d

running

trigger slackstarted 09:42:11ci attempts 0esc to close

[09:42:11] sandbox booted · node:24-bookworm

Reading repository structure to locate the auth middleware

toolread_filemiddleware/auth.go

toolread_filemiddleware/auth_test.go

toolread_fileinternal/auth/clerk.go

Found root cause: expired tokens bypass the error handler at middleware/auth.go:54

tooledit_filemiddleware/auth.go (+9 -2)

tooledit_filemiddleware/auth_test.go (+24 -0)

toolrun_commandgo test ./...

[09:43:47] tests passed · 12/12

Open a PR, fix CI until it’s green

Ryven pushes a branch, opens a draft PR, and watches the checks. Failing logs get parsed, fed back to Claude Code, and re-pushed as a new commit — up to three retries before it pings you.