Skip to content

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

docs: config set cannot write browser.proxy.username or password in any order, so name the config patch pair the reference already promises works (PIN-178)

Luigi Agosticbf7755bbb17
diff --git a/docs/reference/config.md b/docs/reference/config.md
index 6b88a880..ff945389 100644
--- a/docs/reference/config.md
+++ b/docs/reference/config.md
@@ -442,6 +442,14 @@ them take effect — and PinchTab reports the incomplete block on each config re
or write until a server is set. Clearing `browser.proxy.server` turns the proxy
off and leaves the other values on disk for the next server.
+`browser.proxy.username` and `password` are the exception, and it is not about
+the server: each requires the other, so `config set` aborts on either one alone
+whichever order you try. Send the pair in one write instead:
+
+```bash
+pinchtab config patch '{"browser":{"proxy":{"username":"bob","password":"s3cret"}}}'
+```
+
`browser.proxy.geo` is a CloakBrowser fingerprint-alignment hint. When a proxy
server and geo block are configured for a CloakBrowser target, PinchTab maps the
geo values into native CloakBrowser fingerprint flags unless the target already