Start here

The web UI

lampson --web

opens http://127.0.0.1:8080 on the project of the current folder. Same agent, same settings and sessions as the terminal — pick whichever you prefer, or use both.

The screen§

• Header — the project name, the permission mode (ask / yolo / strict), the plugins pill (how many are on), the provider · model pill (click to change), ⚙ settings, >_ terminal, and the sun/moon theme toggle.
• Left panel — sessions (with ≡ for the trace of each), the file tree, project memory, MCP and LSP servers, API (the keys for your apps and agents), Channels (Telegram, Chatwoot…), scheduled tasks and pending approvals.
• Center — the chat: every tool step as a line with its result, diffs for edits, and a composer where you can paste or drop images.
• Right panel — the servers the agent started (live logs), sub-agents, the todo list of the session, ports in use.
• File tree — click a file to open it in the editor: colours by file type (JS/TS, CSS, HTML, Python, Rust, Go, shell, SQL, YAML, Synsema…), Ctrl+S saves. If the agent changed the file on disk meanwhile you are asked whether to overwrite or reload instead of losing anything, and when you have no local edits it refreshes by itself. Right-click a file, a folder or the empty area for the usual menu: new file or folder, rename, duplicate, copy / cut / paste, copy the relative or absolute path, insert the path in the chat, delete. Drag a file or folder onto a folder to move it (hold Ctrl to copy instead). On the selected row F2 renames, Delete asks before deleting, Ctrl+C / Ctrl+X / Ctrl+V copy, cut and paste. Nothing ever overwrites an existing file: a duplicate becomes name copy.ext.

Approving§

When the agent wants to do something risky the message gets two buttons, allow and deny. Nothing runs until you click one.

API and Channels§

• API — create a key (which agents it may use, how many requests per minute, which URLs it may send callbacks to) and you see it only once, with the API and MCP URLs ready to copy; revoke the ones you no longer use. → HTTP API
• Channels — every installed channel: turn it on or off, which agent answers, the mode (webhook or no public URL), the webhook URL, configure and the latest events. → Channels

Teams and objectives§

On the home page (http://127.0.0.1:8080/), each project shows its teams and what's waiting for you, and equipos opens the view of all your projects (/equipos). Inside a project, the equipos button in the header opens a separate, full-screen view: your objectives (with their board, report and result) and your teams as a live graph — who reports to whom, who's working, which message is passing — with their board, their record and an editor to build them.

What's waiting for you — your agents' questions and what they ask to approve, including merges into main with what goes in — is in the inbox: the ⚑ button in the header, on every screen, with everything from all your projects. You answer right there, from your phone too.

Terminals in the browser§

>_ terminal opens a real shell in the center pane, in your project folder — up to four tabs with + nueva terminal. They survive a page reload (the shell keeps running; the page reattaches and replays the last output) and they die with Lampson.

The workspaces screen§

http://127.0.0.1:8080 with no project shows every project you have opened with Lampson. Open one, create one from a folder picker, turn them on and off. See Workspaces.

Local only§

The web API answers only your own computer. Any other address gets 401. To let a script in from elsewhere, set LAMPSON_WEB_TOKEN in .env and send Authorization: Bearer <token>. To reach Lampson from your phone for approvals, see Scheduled tasks — that goes through one-time links, never by exposing the API.