What it is
Local Web runs the workbench from a LoneAct service on your computer; the browser is only the interface. Project folders, conversations, Agent teams, execution records, and Secrets all live on your computer and do not depend on the cloud to store business data.
Full workbench
Projects, Conversation, Team, Settings, checkpoints, and other capabilities all sit on the same page.
Local tools
Direct access to local files, the terminal, and the browser; the most natural entry point for development and operations tasks.
Local data
Project content and conversations are not uploaded to the cloud control plane by default; secrets stay in host secure storage.
Who it is for, what it needs
| Item | Notes |
|---|---|
| Best for | Local projects maintained over time, development tasks that need a terminal and file access, and teams that care about data locality |
| Operating system | Windows, macOS, or Linux |
| LoneAct service | The Local Web service or desktop app on this computer |
| Browser | Any modern browser |
| Account | Model services and a plan are required; how you connect depends on the deployment configuration |
Get started
Start the LoneAct service
Start Local Web as described in the installation guide, and confirm the health check passes and the page opens in a browser.
Sign in and confirm the account
After signing in, check the current plan, model services, and available model catalog.
Add one or more project folders
Choose a local project directory and confirm the path. You can add more projects; each folder becomes an independent Project Location and Agent file boundary.
Create work
Open the project overview or create a conversation directly, choose a model, and write the first goal.
What you can do
Multiple projects
Add multiple project folders on one device; Locations groups them by device and each project keeps its own conversations, team, memory, and settings.
Local and remote projects
With --remote-access-cloud-url, Local Web can mount both Direct local projects and Cloud Relay remote projects.
Long-running projects
One project can keep multiple Conversations, Agent Teams, Memory, Rules, and checkpoints.
Parallel conversations
Open different tasks side by side and move them forward in one window.
Real tool execution
File reads and writes, terminal commands, browser actions, and MCP tools all run on the device that owns the project.
Full security control
Repository allowlists, project budgets, Secrets, and remote grants are managed together in Settings.
See Projects and devices for the full model of multiple projects, same-account discovery, and cross-account Grants.
Boundaries and guidance
- After the browser page is closed, whether a running task continues depends on the local service and the task type; important results should be written back to the conversation.
- The Local Web terminal is a managed process session, not the same as a native terminal window; available tools depend on your computer.
- Local Web capabilities come from the LoneAct service on your computer; when it is offline, remote entry points cannot execute local tools in its place.
- A remote project needs its owning device to be online; remote access is optional, and Local Web stays local-only when no Cloud URL is configured.
- Do not use your entire home directory as a project folder; use a project root and keep the allowlist narrow.
Next: read Secrets and environment variables to give the project a safe execution environment.