local-operator.com valid

Local Operator Docs

Guides for the Local Operator agent runtime: the terminal UI, the desktop app, workflow automations, remote access, and building on top of it.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-25T14:55:38.676Z. Cached copy · Source on local-operator.com

# Local Operator Docs

> Guides for the Local Operator agent runtime: the terminal UI, the desktop app, workflow automations, remote access, and building on top of it.

## Get started

- [What is Local Operator?](https://docs.local-operator.com/getting-started/what-is-local-operator): Local Operator is an agent runtime that runs on your machine — one runtime every surface, from the terminal to your phone.
- [Install & first run](https://docs.local-operator.com/getting-started/install): Install the Local Operator runtime with pip, pipx, or uv, grab the desktop app, or run it with Docker or Nix — then verify the install.
- [Quickstart](https://docs.local-operator.com/getting-started/quickstart): Sign in to a provider, launch the terminal UI, run your first task, and approve a tool call — the five-minute first-run path.
- [Choose your surface](https://docs.local-operator.com/getting-started/choose-your-surface): TUI, desktop app, mobile relay, browser extension, exec mode, or the Python SDK — which surface to pick, and when.
- [Updating Local Operator](https://docs.local-operator.com/getting-started/updating): Update the runtime with lop update or /update, upgrade an install by hand, and find release notes.

## Surfaces

- [The terminal UI](https://docs.local-operator.com/tui/quickstart): Launch, read, and drive the terminal UI — the transcript, the keys worth knowing, and the slash commands that matter.
- [Desktop app](https://docs.local-operator.com/surfaces/desktop): Install the desktop app, sign in, and learn the window — chat with run details, the tool trace, projects, schedules, themes, and the Agent hub inside the app.
- [Mobile relay](https://docs.local-operator.com/surfaces/mobile-relay): Check on, steer, and start sessions from your phone — how the relay reaches your computer, how to set it up, and what the phone can do.
- [Mobile app](https://docs.local-operator.com/surfaces/mobile-app): The open-source native iOS and Android client for Local Operator — follow, steer and approve your computer's sessions from a phone.
- [Browser extension](https://docs.local-operator.com/surfaces/browser-extension): Give the agent the browser you are already signed into — install from the Chrome Web Store, pair the bridge, and know exactly what it can and cannot do.

## Capabilities

- [Workflow automations](https://docs.local-operator.com/capabilities/workflow-automations): Schedule future turns, watch for changes, and run work in the background — the wake, monitor and job primitives, plus machine-readable output.
- [Always-on & proactive agents](https://docs.local-operator.com/capabilities/always-on): Sessions that start their own turns — scheduled wakes that fire with every terminal closed, the supervisor that runs them, and Aida, the built-in chief of staff.
- [Agent Mesh](https://docs.local-operator.com/capabilities/agent-mesh): Pair your machines into one network so sessions can reach agents on other devices — roles, grants, onboarding, and incident
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=local-operator.com · GET /v1/domain/local-operator.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for local-operator.com:
1. POST https://agentwebmap.com/v1/sites/local-operator.com/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://local-operator.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/local-operator.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/local-operator.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.