Skip to content

High-performance browser automation bridge and multi-instance orchestrator with advanced stealth injection and real-time dashboard.

fix: docs cookies endpoints

Luigi Agosti56f2b2b2f1fc
diff --git a/docs/architecture/autosolver.md b/docs/architecture/autosolver.md
index a4bd9bb0..1315d5e0 100644
--- a/docs/architecture/autosolver.md
+++ b/docs/architecture/autosolver.md
@@ -2,7 +2,7 @@
## Overview
-The AutoSolver system provides modular, semantic-first browser automation for Pinchtab. It evolves the existing `internal/solver` framework (PR #395) into a general-purpose automation agent capable of handling CAPTCHAs, login flows, signup flows, multi-step navigation, and onboarding sequences.
+The AutoSolver system provides modular, semantic-first browser automation for PinchTab. It evolves the existing `internal/solver` framework (PR #395) into a general-purpose automation agent capable of handling CAPTCHAs, login flows, signup flows, multi-step navigation, and onboarding sequences.
### Design Principles
@@ -211,7 +211,7 @@ as := autosolver.New(cfg, semanticEngine, nil)
as.Registry().Register(&solvers.MySolver{})
```
-### Using with Pinchtab Bridge
+### Using with PinchTab Bridge
```go
// Create Page + Executor from a bridge tab
@@ -229,7 +229,7 @@ if result.Solved {
## Comparison with browser-use
-| Aspect | browser-use | Pinchtab AutoSolver |
+| Aspect | browser-use | PinchTab AutoSolver |
|--------|-------------|-------------------|
| Decision engine | LLM per step | Semantic first, LLM fallback |
| DOM handling | Full DOM/screenshot each step | Trimmed HTML, a11y tree |
diff --git a/docs/architecture/mcp.md b/docs/architecture/mcp.md
index 469780d9..afbe9e78 100644
--- a/docs/architecture/mcp.md
+++ b/docs/architecture/mcp.md
@@ -115,6 +115,7 @@ URL validation lives in `handleNavigate` (`handlers_navigation.go`), which calls
## Security Considerations
- **`pinchtab_eval`** calls `/evaluate`, which requires `security.allowEvaluate: true` in the PinchTab config. It returns HTTP 403 by default. This is intentional — arbitrary JS execution is a separate opt-in from browser control.
+- **`pinchtab_cookies`** calls `/cookies`, which requires `security.allowCookies: true` for read access. Cookie values can expose session credentials, so reads are disabled by default.
- **URL validation** — `pinchtab_navigate` rejects non-HTTP/HTTPS URLs to prevent SSRF via `file://`, `javascript:`, or custom schemes.
- **Token forwarding** — the MCP client forwards the configured bearer token to PinchTab, so access control at the PinchTab layer applies to all tool calls.
- **Wait caps** — `pinchtab_wait` and `pinchtab_wait_for_selector` enforce a 30-second maximum to prevent agent runaway.
diff --git a/docs/endpoints.md b/docs/endpoints.md
index bfc7cd15..fbad6e0c 100644
--- a/docs/endpoints.md
+++ b/docs/endpoints.md
@@ -291,8 +291,10 @@ POST /upload
POST /tabs/{id}/upload
GET /cookies
POST /cookies
+DELETE /cookies
GET /tabs/{id}/cookies
POST /tabs/{id}/cookies
+DELETE /tabs/{id}/cookies
GET /clipboard/read
POST /clipboard/write
POST /clipboard/copy
@@ -304,7 +306,7 @@ GET /cache/status
Notes:
- download and upload endpoints are gated by `security.allowDownload` and `security.allowUpload`
-- cookie read/write endpoints (`GET/POST /cookies`, plus tab-scoped variants) are gated by `security.allowCookies`; cookie clearing remains available so operators can remove session state
+- cookie read/write endpoints (`GET/POST /cookies`, plus tab-scoped variants) are gated by `security.allowCookies`; `DELETE /cookies` and `DELETE /tabs/{id}/cookies` remain available so operators can remove session state
- download automatically decompresses `.gz` files and returns the decompressed content
- `security.downloadAllowedDomains` can whitelist specific domains (bypasses SSRF checks for those domains). Setting `["*"]` matches every host and disables all private-IP protection on the download endpoint.
- clipboard endpoints are gated by `security.allowClipboard`
diff --git a/docs/implementations/managed-bridge-vs-managed-direct-cdp.md b/docs/implementations/managed-bridge-vs-managed-direct-cdp.md
index d4d1f9c5..6af60a03 100644
--- a/docs/implementations/managed-bridge-vs-managed-direct-cdp.md
+++ b/docs/implementations/managed-bridge-vs-managed-direct-cdp.md
@@ -1,11 +1,11 @@
# Bridge vs Direct-CDP
-This page compares two ways Pinchtab can manage a browser instance:
+This page compares two ways PinchTab can manage a browser instance:
- `managed + bridge`
- `managed + direct-cdp`
-Both are **managed** because Pinchtab owns the instance lifecycle.
+Both are **managed** because PinchTab owns the instance lifecycle.
The difference is where the browser control logic lives and how the server reaches Chrome.
## Short Version
@@ -25,13 +25,13 @@ The direct-CDP model removes that hop and keeps control in the main server.
```text
Managed + bridge
- Pinchtab server
- └─ Pinchtab bridge child
+ PinchTab server
+ └─ PinchTab bridge child
└─ Chrome
└─ Tabs
Managed + direct-cdp
- Pinchtab server
+ PinchTab server
└─ Chrome
└─ Tabs
```
@@ -40,7 +40,7 @@ Managed + direct-cdp
### What it is
-Pinchtab starts a child `pinchtab bridge` process for each managed instance.
+PinchTab starts a child `pinchtab bridge` process for each managed instance.
That bridge owns one browser and exposes a single-instance HTTP API.
The main server routes instance and tab requests to that child.
@@ -77,7 +77,7 @@ agent -> server -> bridge -> Chrome
### What it is
-Pinchtab starts Chrome itself and keeps the CDP session inside the main server process.
+PinchTab starts Chrome itself and keeps the CDP session inside the main server process.
There is no bridge child and no extra per-instance HTTP server.
### Communication Path
@@ -154,7 +154,7 @@ direct-cdp = better efficiency
Today, the intended architecture is:
-- `managed + bridge` for Pinchtab-launched instances
+- `managed + bridge` for PinchTab-launched instances
- `attached + direct-cdp` for externally managed browsers
`managed + direct-cdp` is a useful future model, but it is primarily an architectural option, not the default implementation.
diff --git a/docs/reference/sessions.md b/docs/reference/sessions.md
index 58af8440..7a3a9058 100644
--- a/docs/reference/sessions.md
+++ b/docs/reference/sessions.md
@@ -60,6 +60,8 @@ When a session record contains explicit `grants`, PinchTab enforces them in midd
The built-in grant groups are: `browse`, `network`, `media`, `cookies`, `clipboard`, `evaluate`, `storage`, `console`, `solve`, `tasks`, and `activity`.
+The `cookies` grant only authorizes session access to cookie routes; cookie reads and writes still require the server-level `security.allowCookies` gate.
+
That default is a convenience for trusted automation, not a sandbox. If you need hard isolation between agents or tenants, use separate PinchTab instances.
## CLI Usage