The agent runtime for shipping software
Assign the issue. Drisp ships.
Assign an issue to Drisp and it takes it from there — self-transitioning every status and running the right workflow on Drisp Cloud. Build, review, QA on a live browser, all the way to Done. You set direction. It does the work.
Open source · MIT-licensed CLI
Runs on Claude Code or Codex
Add SSO to the dashboard
Rate-limit the public API
Dark-mode polish pass
GraphQL schema cleanup
Flaky e2e on CI
Stripe webhook idempotency
Audit-log export
Webhook delivery retries
Cursor pagination
OAuth token refresh
Mobile nav regressions
Empty-state polish
Self-serve billing portal
Invite teammates
CSV import limits
The agent is fine.
The workflow around it is broken.
- Same prompt. Same model. Different output every time.
- Agents drift over long runs. No checkpoints, no way to recover.
- What works for one dev doesn’t transfer to the team.
- You see the final output. Not the 40 tool calls that produced it.
- Agent tooling assumes a human at the keyboard. CI and automation are afterthoughts.
- One agent at a time. Engineering caps at what a single developer can babysit.
One runtime.
Local or cloud. One agent or a thousand. Same definition, same result.
Drisp sits between you and the agent. Define steps, constraints, and exit criteria once. Run on Claude Code, Codex, or any future agent runtime. Locally, on your own infra, or fanned out across Drisp Cloud.
Spawn agents
in parallel.
A workflow is a unit of agent work. Drisp turns it into something you run once, ten times, or a thousand times. Across one runner or many. Same definition. No rewrite.
One agent
A single workflow on a single repo. Your laptop, your CI job, your local agent. The starting point everyone knows.
Ten agents
Fan out across a sprint of tickets, a feature's full test matrix, or a fleet of microservices. One workflow definition, ten parallel runs, one aggregated result.
A thousand agents
Drisp Cloud spins up runners on demand. Treat coding agents as horizontal capacity. Same workflow, factory-scale throughput, structured artifacts piped back into the rest of your pipeline.
Triggered from a webhook, a schedule, or a single CLI command. The workflow doesn’t change as you scale. The runtime does.
One runtime.
Two operators.
The Drisp CLI is the runtime. It sits on top of Claude Code or Codex and coordinates every step of every workflow. Run it yourself, or attach it to a managed runner on Drisp Cloud.
Drisp CLI
Run it yourself.
MIT-licensed CLI. Install it on your laptop, run it in CI, or self-host it on your own infrastructure. Bring your own agent keys. Own your data.
- Free, forever
- Local-first dev loop
- Self-host on any container runtime
- Workflows install from the marketplace or from a local path
Drisp Cloud
Let us run it for you.
Spin up a managed runner from the dashboard, attach the workflows it should run, and trigger it from anywhere. Same CLI underneath. Drisp Cloud handles the infra, schedules, queues, retries, checkpoints, and storage.
- Free to start — no card required
- Pay per run after that
- Triggers from GitHub, cron, REST, Slack, or webhook
- SSO, audit log, role-based access for teams
Workflows are the same in both modes. Whether you type drisp workflow install on your laptop or attach a workflow to a Cloud runner from the dashboard, the same install runs underneath.
Install workflows
like packages.
Browse community-maintained workflows or publish your own. Each one is scoped, tested, and version-pinned. Install with a single command on the CLI, or attach one to a Cloud runner.
playwright-automation
v0.0.21Writes, reviews, and stabilizes Playwright end-to-end tests from live product flows.
$ drisp workflow install playwright-automationrobot-automation
v0.0.21Generates Robot Framework suites with reusable keywords, structured fixtures, and CI-ready runs.
$ drisp workflow install robot-automationexploratory-testing
v0.0.14Runs charter-based exploratory sessions, captures evidence, and files actionable issues.
$ drisp workflow install exploratory-testingsmoke-testing
v0.0.14Defines and executes smoke suites against critical paths so breakages surface before release.
$ drisp workflow install smoke-testingregression-testing
v0.0.14Scopes impact-based regression runs, reruns the right areas, and reports deltas against the last release.
$ drisp workflow install regression-testingfullstack-engineering
v0.0.9Maps the codebase, implements the change, validates the result, and ships a PR for full-stack features and fixes.
$ drisp workflow install fullstack-engineeringAssign, walk, ship.
Three steps. Assign the issue, Drisp walks the statuses, it ships to Done. You stay out of the loop until it needs you.
Assign it like a teammate.
Assign an issue to Drisp in Linear, Jira, GitHub, or Notion. That is the one human action — no workflow to pick, no command to run.
Assignment is the primary trigger. Cron, REST, Slack, and webhook work too.
It self-transitions each status.
Drisp moves the issue In Progress → In Review → QA → Done, fanning out the right workflow per status across Cloud runners.
On Drisp Cloud: each workflow runs on managed runners with queues, retries, and storage handled.
Shipped to Done.
PR merged, 0 regressions, issue closed. Most issues ship hands-off; some loop a human in, and auto-merge is an opt-in ceiling.
~80% of issues ship hands-off. ~20% pull a human in. You stay in control of the merge.
Specialized workflows.
Spawned at scale.
Pre-built agent programs for the work engineers actually ship. Dispatched from the surfaces your team already uses, fanned out across as many runners as the job needs.
Prebuilt for real work.
Pre-built agent programs for QA, security, code review, frontend, full-stack, and devops. Install once. Dispatch when needed.
Assign in your tracker.
Assign an issue in Linear, Jira, GitHub, or Notion and Drisp picks it up — the one human action. Cron, REST API, Slack, and webhook trigger runs too.
Claude Code or Codex.
Write a workflow once and run it on either harness. Drisp normalizes the event stream, so the same definition, plugins, and logs work on both.
Debuggable logs.
Streaming events, tool calls, tokens, cost. When a run fails, you see exactly where and why. At one agent, or at a thousand.
Drisp CLI is free, forever. Drisp Cloud is free to start, then pay-per-run for managed runners, so cost scales with the work, not with the seat count.
See pricing →Toward the autonomous engineering factory.
Workflows as labor. Runners as workforce. Scale as a dial. Drisp is the standard the rest is built on. We’re shipping it one workflow at a time.
Start building.
Install the CLI and run your first workflow locally. Or sign up for Drisp Cloud and spawn agents at scale.
$ npm install -g @drisp/cli