Browsentic is four processes cooperating over loopback: a browser extension, a local daemon, one stdio MCP server per client, and — when the side panel is driving — a headless agent CLI.
Read in order, these pages follow a request through all of them:
| 1. Overview | The four processes, and why a Manifest V3 extension forces a daemon |
| 2. Transport | Ports, the Origin gate, the mutual pairing handshake, protocol versioning |
| 3. The action registry | One definition compiled into two bundles; names, drift detection, reserved actions |
| 4. Request path | Path A — an MCP client's tool call reaching the page |
| 5. Inside the extension | Background vs content script, self-healing injection, tab scoping |
| 6. Agent runs | Path B — the intent funnel, the spawned CLI, prompt assembly, skill routing |
| 7. Guardrails | The declarative policy, run scope, result fencing, spawn containment |
| 8. Subsystems | Monitors, recordings, site maps, files, screenshots |
| 9. State on disk | Every file Browsentic writes, and why it is where it is |
| 10. Contributing | Build topology, the checks, and adding a capability |
Looking for an error code? reference/errors.md.
Looking for a tool's parameters? reference/tools.md.