Skip to content

Documentation

Other clients

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

Bento has two clients: the Web UI (apps/web) and the terminal (apps/tui). The TUI is now available. Both clients use the same API and can run the complete card workflow.

Terminal

apps/tui provides a terminal board and scriptable commands. It can run the full server locally or connect to a remote server as a thin client or local agent runner. See the TUI guide for installation, run modes, setup, and shortcuts.

Card navigation: j/k to select; the pane below tails the newest run transcript; h for card history; a approve, R reject; r re-check; x stop; c continue with instructions.

Setup and configuration:

bento setup
bento repos add ../api --project Checkout --setup "npm ci" --test "npm test"
bento agents edit Reviewer --model claude-sonnet-5
bento agents export team-agents.yaml
bento pipeline export team-pipeline.yaml

Feature coverage

TaskWeb UITerminal
Create a projectYesYes
Create one spanning several repositoriesYesOne, then add
Connect and remove repositoriesYesYes
Set a repository's setup and test commandsYesbento repos set
Export and import a pipeline as YAMLYesbento pipeline
Export and import agents as YAMLYesbento agents export / import
Add a cardYesYes
Add, edit and remove agentsYesYes
Assign an agent to a stageYesYes
Add, remove and rename stagesYesYes
Reorder stagesDrag, or arrow keysMove stage earlier / later
Switch a stage between manual and automaticYesYes
Edit stage requirements, judge agent includedYesYes
Turn a stage's pull request on or offYesYes
Approve or reject a cardYesYes
Move a card between stagesDrag it between lanesa and b keys, one step
Start, stop, and continue an agentYesYes
Save and remove provider API keysYesYes
Invite and remove members, network accessYesYes
Share a model key with the teamYesNo

Team management and stored credentials require multi mode. Local mode has one user and no organization.

Server and agent placement

The terminal separates where the board runs from where agents run:

bento                                                     # server and agents on this machine
bento --server https://app.usebento.ai                       # board on server; agents on server
bento --server https://app.usebento.ai --run-agents local    # board on server; agents on this machine

With --run-agents local, the shared server holds board state and transcripts. Agents run against local checkouts on the member's machine. Runs queue when that machine is offline. The server does not push to GitHub because it cannot access local worktrees.