The docs are in three parts: the user guide, the internals and the reference.
Using it
For running Browsentic on your own machine.
| Install | One line sets up Browsentic Bridge, then the extension comes from your browser's store |
| Pair | Connecting a browser to Browsentic Bridge with a single-use code |
| First run | A tour of the side panel and your first instruction |
| Features | One page per capability: what it does and when to use it |
| Choosing an agent | The eight agent CLIs the side panel can run on |
| MCP clients | Optional: drive the same browser from Claude Code, Cursor, Zed or Gemini CLI |
| Configuration | Every key in ~/.browsentic/config.json |
| Approvals | Which actions wait for your approval, and how to change that |
| Limits | Where Browsentic does not fit; read it before you rely on it |
| Troubleshooting | Symptom → cause → fix |
| Maintenance | Updating and uninstalling |
Building on it
How the parts work, for contributors and integrators.
| Overview | Four processes, and why there is a daemon at all |
| Transport | Ports, the origin gate, the pairing handshake |
| The action registry | One definition, two bundles, and drift detection |
| Request path | A tool call from an optional MCP client, end to end |
| Inside the extension | Background vs content script, tab scoping |
| Agent runs | The intent funnel, runners, prompt assembly |
| Guardrails | The policy, run scope, fencing, spawn containment |
| Subsystems | Monitors, recordings, site maps, files, screenshots |
| State on disk | What is written where, and at what mode |
| Contributing | Build topology, checks, adding a capability |
| Store listings | Store IDs, submitting an update, what the dashboards ask for |
Looking something up
| Tools | All 52 page tools with their parameters, plus the resources |
| CLI | Every browsentic command |
| Errors | Every error code, what caused it, what to do |
To get started: Install → Pair → First run.
The project README is the short version.