Bento

Dispatch structured agents systematically. Through GitHub webhooks, Linear issue events, cron schedules, or via a CLI. Declare your workflows as pipelines in YAML, versioned inline with code, and let the daemon handle the rest.

What is Bento?

Bento is a harness-as-code tool for running coding agents. You describe how an agent runs — its trigger, runtime, skill, sandbox, and guardrails — as a version-controlled pipeline, and the daemon provisions an isolated workspace and runs it on every matching event.

Connection surfaces

Bento receives work from the tools around a repository and returns results to the declared destination. Open a surface to configure it.

TriggerGitHubPull requests, issues, reviews, and repository events TriggerLinearIssue events delivered through workspace webhooks TriggerWebhooksNamed HTTP endpoints for events from other systems TriggerSchedulesRecurring runs declared with UTC cron expressions ControlCLI & MCPFire pipelines on demand or expose them to agents OutputSlackPost completed pipeline output through a named bot

A concrete example

A pull request opens on GitHub

GitHub sends a webhook to the daemon.

The daemon matches it to a pipeline

A pr-review pipeline fires: the daemon retrieves the diff and injects relevant context from the knowledge base.

An agent is dispatched to a sandbox

The pr-review agent executes in an ephemeral sandbox with the repository checked out.

Findings are posted back

The agent's output lands as a PR comment.

Stop prompting and hoping for the best. Engineer your agent workflows with confidence, knowing they'll run reliably and consistently in production.

Next steps

Installation — install the daemon and configure your first pipeline
Concepts — pipelines, agents, skills, workloads, and sandboxes explained