lattices.dev valid

Action

Observe and control apps, browsers, and recordings.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-27T09:55:30.729Z. Cached copy · Source on lattices.dev

# Action

> Observe and control apps, browsers, and recordings.

Documentation: https://lattices.dev/action/docs

**First check**

Action owns native observe, resolve, act, and record, private agent layers, and Action-owned browsers. Window tiling and workspaces are Lattices.

Agent guide: [Connect Action to your agent](https://lattices.dev/action/docs/agent-setup.md).

First check (read-only): `lats action status`
Expect: Install, runtime, and agent state. Over MCP, read `capabilities` and `tools/list` and report the native/runtime match before you take control.

## Current documentation

- [Overview](https://lattices.dev/action/docs/overview.md): What Action is, what it installs, and how it relates to Lattices
- [Getting started](https://lattices.dev/action/docs/getting-started.md): Install Action.app, grant permissions, and check the local agent
- [Concepts](https://lattices.dev/action/docs/concepts.md): Action's processes, ports, command routes, sessions, leases, and capture lifecycle
- [Connect Action to your agent](https://lattices.dev/action/docs/agent-setup.md): Read Action's capabilities and available tools. Report the connected host, native/runtime match, and any setup requirements before taking control.
- [Browser](https://lattices.dev/action/docs/browser.md): The three browser surfaces an agent can drive with Action, and which tools reach each one
- [Browser profiles](https://lattices.dev/action/docs/browser-profiles.md): Regular Chrome, Action browsers, and identities seeded from your Chrome profiles
- [Agent layer](https://lattices.dev/action/docs/agent-layer.md): Work an app or Action-owned browser on a prepared private virtual display
- [Recording](https://lattices.dev/action/docs/recording.md): How Action records a window or region and signals completion
- [Stage](https://lattices.dev/action/docs/stage.md): Present listed windows on a flat backdrop for a clean take
- [API](https://lattices.dev/action/docs/api.md): The Action agent WebSocket protocol over authenticated private action.sock
- [Native runtime](https://lattices.dev/action/docs/native-runtime.md): How Action.app and the Action agent split native responsibilities
- [Action with a remote Linux host](https://lattices.dev/action/docs/remote-engine.md): Action can observe and act on a Linux desktop running lattices-host. Runs, traces and artifacts stay on the controller; the remote host performs the work.
- [Skills](https://lattices.dev/action/docs/skill.md): Review patterns an AI agent follows when changing Action

## Retrieval

- [Public agent instructions](https://lattices.dev/action/docs/AGENTS.md)
- [Full context](https://lattices.dev/action/docs/llms-full.txt)
- [Structured documentation](https://lattices.dev/action/docs/agent-docs.json)
- [All products](https://lattices.dev/llms.txt)

Related sites

Explore similar publishers →

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

Machine-readable: GET /v1/resolve?q=lattices.dev · GET /v1/domain/lattices.dev · 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 lattices.dev:
1. POST https://agentwebmap.com/v1/sites/lattices.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://lattices.dev/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/lattices.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/lattices.dev).
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.