The web UI

The web UI shows the same board and agents as the TUI, in a browser. It adds a conversation view for agents, a side panel for what they show you, and pages for plans, reviews, workflows and reports. Use it on a second screen, on a laptop away from your desk, or on your phone.

To start the web server, see Web server. To run it with the TUI, set web.enabled: true. To reach it from a phone or another computer, see Devices. You can also install the web UI as an app (a PWA) from the browser.

Getting around

On a wide screen, a rail on the left holds every page. A count beside a page says how many things there wait on you, or how many agents are at work. At the foot are Settings, the server switcher when you use more than one Legato, and the connection state (sync, or a red offline).

On a phone, a tab bar along the bottom holds Attention, Board, Agents, Review and More. More opens the other pages, the server in use, and a few settings.

Page	What it is for
Attention	Everything that needs you, in one list. See Attention and approvals.
Agents	The agent list and one agent’s conversation or terminal.
Ensemble	Every running agent at once, as tiles.
Board	The kanban board. See Board and tasks.
Review	Review tours of what agents changed. See Reviews.
Plans	Plans agents proposed, waiting for your decision. See Plans.
Flows	Workflow runs and the workflows you can run. See Workflows.
Learning	The Legato Learn ledger. See Legato Learn.
Reports	Where agent time went. See Reports.
Remote	Clones Legato made for agents.
Audit	The credential audit log. See The credential broker.
Settings	Repositories, resources, security, integrations, handoff, connection, appearance and updates.

When the connection drops, the UI first says “Reconnecting…” and keeps the page as it is. After 10 seconds without a connection, a Connection Lost dialog offers Retry and a way to switch servers.

Board

The board works as it does in the TUI, with the same keys: h/j/k/l to move, n to create, m to move, / to search, ? for the key list. You can also drag a card to another column, or within its column to reorder it; it lands where you let it go. The phone layout has no drag: Move in a card’s menu moves it to another column, at the end, and a column cannot be reordered there. Press enter or double-click a card to open its detail. From 1280 pixels of width, a panel beside the board describes the selected card, with buttons for its agent, its details and its ticket or pull request.

Import in the header searches your ticket providers and imports a ticket, as i does; see Board. Sync providers in the header syncs Jira and GitHub now, and pulls every worker this Legato hands tasks to.

Once this Legato is paired with a worker instance, a card’s menu and its panel offer Hand off…, a card dragged onto the Away lane opens the same form, and the lane, after the columns, lists the tasks away on each worker. On a phone they are in an Away section above the columns. See Hand off tasks to a worker.

A card’s detail has the task’s notes, reviews, plans and workflow runs in tabs. When the task’s agents built a stack of branches with Staccato, a Stacks tab shows it, with Download stack once every branch is pushed; see Staccato.

On a phone, the board shows one column at a time. Swipe sideways, or tap a column’s chip, to change column. A new card starts in the column you are looking at. Press and hold a card for its actions.

Agents

The Agents page lists your running agents on the left, by state, as the TUI does. Open one to see it on the right.

Groups

Once any agent is in a group, the list shows agents by group: the groups in groups.defaults, then the other groups in use by name, then Ungrouped. Inside a group, agents keep the order by state, so one that needs you comes first. The Reeve stays pinned above the groups. A group belongs to the agent’s task, so the TUI and the web UI show the same groups, and a change in either shows in the other.

• Move an agent: drag it onto a group, or onto Ungrouped to take it out of its group. Or pick Move to group… in its right-click menu or the More actions menu in its header, which also has New group…. On a phone, use the header’s menu.
• Collapse a group: click its header. A collapsed group shows how many agents it holds and, in amber, how many of them need you. Your browser remembers which groups are collapsed.
• Manage groups: New group under the list makes an empty group to drag agents into; your browser keeps it until you delete it. A group’s ⋯ menu has Rename group, Delete group (its agents become ungrouped) and Collapse all others. A group in groups.defaults keeps its header after you delete or rename it; take it out of that setting to remove it.
• List by state: the button beside Ensemble switches between the list by group and the list by state. Your browser remembers the choice.

On a phone, the agent picker lists the same groups, and a tap on a group’s header collapses it.

An agent shows in one of two ways:

• Native panel. Claude Code, Codex and Chimera, when Legato talks to them through its bridge, show as a conversation: your messages, the agent’s replies, its tool calls as compact rows, and its thinking when the tool shares it. What the Reeve said out loud is a bubble marked ◈ Said, never folded with the tool calls. Permission requests and questions appear as cards you answer in place. A model menu and a settings dialog change the model and effort for this session; see Model settings. You can queue a message while the agent works.

Each message you send is listed above the message box until the conversation shows it: sending, then sent once the agent has it. The agent reads a sent message at its next step, or as its next prompt when the turn ends first. If a message cannot be delivered, it shows as not sent with the reason: Edit puts it back in the box to send again. When the page has lost its connection to Legato, a message you send stays in the box and the panel says so.

• Terminal. Any other agent, or one you switched with Downgrade to tmux, shows its terminal. A switched agent stays on its terminal when Legato restarts. A prompt bar below it sends text and keys. Upgrade to native panel switches a terminal agent back when its tool supports it.

When a native agent starts subagents, a Sub-agents switch appears in its header beside Related and Artifacts. Inline shows each subagent as a card in the conversation. Tiles keeps the conversation in the left half and gives each subagent a tile in the right half: what it is doing, its newest steps, how long it has run and how many tools it called. Running subagents share the space; finished ones move to a list underneath, newest first. The list shows the newest three: Show more lists the rest, and its Finished heading folds it away. Click a tile, or the subagent’s line in the conversation, to open it in full with the prompt it was given; All tiles or Esc goes back. On a phone or a narrow window, the tiles are a strip under the header: tap one to open it as a sheet, and swipe or use the arrows to move between subagents. The browser remembers your choice. Tiles show Claude Code and Chimera subagents; Codex subagents are not shown yet.

Type / in a native agent’s message box to list its commands and skills. As you type, the best matches come first: the exact name, then names that start with what you typed, then names with a word that starts with it (/review finds plugin:review). Use ↑ and ↓ to move, and Tab or Enter to complete the highlighted one: it goes into the box and you keep typing, for example the skill’s arguments. Nothing is sent until you press Enter again. A command that stands for a prompt puts that prompt in the box. Esc closes the list; type again to reopen it.

When a native agent’s terminal shows a numbered menu (an update notice, a trust question), the panel draws it as a card with a button for each choice.

The More actions menu in the agent’s header holds Rename, Refresh from snapshot, notifications, Reload agent, Reload without sandbox (or Reload in sandbox, for an agent you started outside it), Disconnect and Kill agent. The sandbox entry is there only while Legato’s sandbox is on; see Sandbox. Right-click an agent in the sidebar for the same actions. For an agent you have not opened, the actions that act on the open terminal (refreshing it, prompt detection) are left out. Rename renames the agent’s task, so it works for local tasks; a task from a provider keeps its title. Asking before Kill agent, Reload agent and similar actions uses a small dialog in the app, not the browser’s. See Agents for reloading and stopping.

To switch agents from the keyboard, hold the switch key and press 1 to 9. The key is Control on Linux and Alt on a Mac unless you change it in Settings › Agents. Press M for the agent’s macros. A draft you type for one agent is kept when you switch to another.

Terminal mode

An agent that runs in tmux opens on the Agents page as a real terminal on its tmux session, set in a frame. Type straight into it (menus, arrow keys, Ctrl keys), scroll with the wheel or a drag to read tmux’s own history; it resizes with the window. The strip along the top of the frame names the session. If the connection drops, it says Reconnecting and when it will try again, and Retry now tries at once. Refresh terminal in the agent’s menu reconnects it too. Agents with a native panel keep their panel.

On a computer there is no message box: the terminal is where you type, and the agent’s menu is in the header. A phone keeps the message box, with a row of the keys its keyboard lacks: Esc, ⇧Tab, ↑ and ↓, and Ctrl, which sends the next character you type, in the box or the terminal, with Ctrl. When the agent asks something, such as a yes-or-no menu, its answers appear as buttons above the box.

The terminal’s colours are set in Settings › Appearance › Terminal theme, for this browser: Legato (the default, Legato’s own colours), Night (the same on black), Solarized Dark or Classic.

While a terminal is open in the web UI, the session has mouse mode on and no tmux status line, which a desktop tmux attach sees too. Hold Shift to select text with the mouse there.

Artifacts and cards

An agent can show you things through its MCP tools:

• A card appears in the conversation where the agent made it, in place of text: a chart, a table, a status.
• An artifact opens in the Artifacts panel beside the conversation (a full-screen sheet on a narrow screen). The panel keeps each artifact as a tab, with its revisions, Copy source and Download.

HTML an agent wrote runs in a closed frame that cannot reach the network beyond the hosts in agents.mcp.resource_domains. A card can offer text for your message box, but it never sends anything for you.

The Related switch beside Artifacts shows the task’s card, its pull request, and its plans, reviews and workflow runs.

Review briefings on the branch

If the agent’s branch carries a review briefing (HTML pages under .review/ that the branch adds or changes), the Artifacts panel shows each page as a tab before the pull request exists. Legato checks for changes every 15 seconds.

Images

When an agent reads an image file, its row in the conversation opens to show the image. Click the image to see it full size.

To give an agent an image, paste it into the message box, drop an image file on the box, or press Attach image (the picture icon under the box) and choose one. On a phone, Attach image opens your photos. Legato stores the image in a temporary folder and puts the file’s path in your message, where the agent can read it. A thumbnail above the box stands for each image. Legato keeps a task’s newest 20 images, up to 10 MiB each, in PNG, JPEG, GIF, WebP or BMP.

If you copied text with the image, the text is pasted too. A task that is away on a worker takes images only from the worker’s own page, where its agent runs.

Context fill

For a native agent, a meter in the agent list and on each ensemble tile shows how full its context window is. Legato pushes the reading as it changes. A terminal agent has no meter.

Swarms

Select any agent of a swarm and the page shows the swarm as one unit: the conductor, and every worker in a stack beside it. Click a worker to open it next to the conductor. A Swarm events panel lists what the workers reported.

Ensemble

Ensemble shows every running agent as a tile, the ones that need you first. A tile shows the agent’s state and time, its task and tool, the end of its conversation or terminal, its recent activity and its context fill. Type in a tile’s box and press Enter to message that agent; Open takes you to it. Press e on the Agents page to switch between the list and the ensemble.

Attention, plans, reviews and workflows

• Attention groups what needs you under Needs intervention, Ready for review and Merge blockers. See Attention and approvals.
• Plans is the queue of plans waiting for your decision; open one to read it, comment, answer its questions and approve it. See Plans.
• Review is the queue of review tours; open one to step through the changes and ask the agent about them. See Reviews.
• Flows shows workflow runs, those that need you first, and the workflows you can run. See Workflows.

Requests from agents that wait for you (permissions, questions, credentials) appear in a tray at the bottom right of every page. See Approvals.

Reports, learning and audit

• Reports shows agent time by day, week or month. See Reports.
• Learning lists and searches the learning ledger, and holds its decisions. See Legato Learn.
• Audit lists which agent asked for, was given, was refused or used which credential, and the grants you made that still stand, each with Revoke.

Remote

Remote lists the clones Legato made for agents (with repository_cache.enabled): each clone’s repository, branch, path, tasks, whether an agent works in it, and when Legato will remove it. Remove deletes a clone’s whole folder, changed and untracked files included, after you confirm. You cannot remove a clone while an agent works in it.

Settings

Settings has seven groups:

• Agents: repositories, a link to Remote, resources, Engram bindings (the engrams bound to each repository or folder, with Make default, Unbind and Clear the default, and whether engram was found), the engram settings, prompt detection and the agent switch key.
• Security: browser notifications for approvals, the devices that can sign approvals, and credentials.
• Integrations: Argus and integration tokens.
• Handoff: Workers, the Legatos this one hands tasks to, with Add a worker (with none paired yet, it explains handing off); and Main instances, the Legatos that hand tasks to this one, with Pair a main instance and Unpair. See Main and worker instances and Hand off tasks to a worker.
• Connection: servers, Pair a phone, and the TLS certificate.
• Appearance: the tint, the terminal theme, the glitch effect, and the moving light round a working agent.
• Where a setting comes from. Settings that can be kept on the server show where their value comes from: default, config.yaml with a lock (change it in the file), or set here with Reset, which goes back to the default. One marked applies at restart waits for Legato to restart.
• Export and import settings (in Lists): download the settings kept on the server as a file shaped like config.yaml, secrets as names; or import such a file, which becomes one change set for you to approve.
• Lists: workspaces, macros, agent tools, credentials and the other lists kept on the server. Entries from config.yaml are locked; add, edit or remove the others.
• Updates: this server’s version, the latest release, and the update mode, and Restart Legato, which restarts every Legato process of this server. See Updates.

A setting kept in this browser only is marked this browser.

Tint

To tell your Legatos apart at a glance, give each a tint in Settings › Appearance › Tint: red, orange, yellow, green, teal, blue, purple or pink. The tint is saved on the server, so every browser and phone that uses it shows it: a band across the top of the window, a wash on the rail, and a dot beside the server in the switcher.

Updates

When a new release is out and the update mode is ask, a bar across the top says so, with Update and restart and Later. See Updates.