Skip to content

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

docs: simplify titles - Remote Chrome via CDP_URL => Remote Chrome, Chrome Lifecycle & Orchestration => Orchestration

Mario8d501aaec353
diff --git a/docs/architecture/chrome-lifecycle-and-orchestration.md b/docs/architecture/chrome-lifecycle-and-orchestration.md
index e2fd6c1e..c389d5a7 100644
--- a/docs/architecture/chrome-lifecycle-and-orchestration.md
+++ b/docs/architecture/chrome-lifecycle-and-orchestration.md
@@ -1,4 +1,4 @@
-# Chrome Lifecycle & Orchestration
+# Orchestration
Pinchtab is a Go-based bridge and orchestrator for Chrome. It doesn't just "run" a browser; it manages a fleet of "sanitized" Chrome instances, hardened against detection and optimized for automation.
diff --git a/docs/guides/cdp-url-shared-chrome.md b/docs/guides/cdp-url-shared-chrome.md
index c903ed3a..a0a4ccb7 100644
--- a/docs/guides/cdp-url-shared-chrome.md
+++ b/docs/guides/cdp-url-shared-chrome.md
@@ -1,4 +1,4 @@
-# Remote Chrome via CDP_URL
+# Remote Chrome
By default, Pinchtab launches its own isolated Chrome instance. But sometimes you want to **connect to an existing Chrome** instead — to share one browser across multiple agents, save memory in container environments, or integrate with external Chrome setups.
@@ -323,7 +323,7 @@ spec:
- name: chrome
ports:
- containerPort: 9222 # No hostPort = not exposed to outside
-
+
- name: pinchtab
env:
- name: CDP_URL