Skip to content
Bento
GitHubSign up

Documentation

Bento documentation

Bento is an agent pipeline: coding agents move each feature through your stages, behind human gates and inside their own sandboxes. Start with why an agent pipeline, then how cards move through stages, then agents, pull requests, and setup.

If coding-agent sessions lose context or skip the process you already have, start with why an agent pipeline.

  • Why an agent pipeline?

    Why coding agents lose your context between chats, stages, and laptops.

  • How it works

    How a card moves through stages: one branch, one sandbox, context in committed files.

  • Pipelines

    Stages, human gates and their requirements, judge agents, and pipeline YAML.

  • Coding agents

    Claude Code, Codex, Cursor, opencode, pi, Poolside, DeepSeek, Antigravity.

  • Security

    How model keys and MCP credentials stay with Bento, and what a sandbox can reach.

  • Pull requests

    Publishing agent work as GitHub pull requests, attribution, and GitHub connections.

  • Swarms

    A planner and many workers on one goal: access, following a swarm, and publishing its pull requests.

  • Web UI

    Run the Web UI from source or Docker, local and multi mode, sandbox drivers, log export.

  • TUI

    Install the TUI, choose where agents run, and configure projects, agents, and pipelines.

  • Other clients

    Compare the Web UI and terminal client, including features and agent placement.