Parameter reference
The GodBrowser flags you drive personas, automation, captcha, egress and capture with — by category. The browser is a patched Chromium with a parallel BotBrowser CLI surface — everything keys off a single --bot-profile seed; without it, the binary is plain Chromium.
17 flags · GodBrowser 151 · drawn from the switch-coverage harness run of date unavailable.
The installer adds
GodBrowser to your PATH. Replace reserved
example.com targets with a URL you own or are authorized to test.
Full-path fallback: /Applications/GodBrowser.app/Contents/MacOS/GodBrowser
(macOS) or C:\godbrowser\chrome.exe (Windows).Open a configured browser with gb://arriving in the next build
A gb:// link carries the same launch
options as the flags on this page, so a portal button, a runbook or a teammate's message can
open the browser on the right saved session, the right device, the right locale and the right
egress country, on the right page. profile= implies persist —
“open my saved session” means restore it, and the restore brings back that
session's device, locale and egress
country, not just its cookies.
gb://open?profile=my-shop&os=ios&browser=safari&locale=en-GB&proxy_country=US&url=https%3A%2F%2Fshop.example.com%2Fsearch%3Fq%3Da%26page%3D2%26sort%3DnewAccepted keys. profile · seed ·
os · browser · locale · proxy_provider ·
proxy_country · url · persist ·
headed|headless · account. A switch you type on the real
command line always wins over the same key in a link.
Percent-encode url=. A landing page nearly always
carries its own ?a=1&b=2, and a raw & ends the
gb:// parameter — the browser would open a truncated page, and it would look like
the site misbehaving rather than the link. Encode it, as in the example above.
Quote it in a terminal. An unquoted &
backgrounds the command and runs a truncated link:
open 'gb://open?profile=my-shop&proxy_country=US'From an AI client, godbrowser_link builds these for you and does
the encoding in code rather than by hand; action:"open" also dispatches
the link on the local machine.
What a gb:// link refuses.
These are the contract, not footnotes:
proxy=<uri>is refused outright. A credential in a URL reaches shell history, browser history and referrer headers. Nameproxy_provider/proxy_countryand let the credential stay where credentials already live.- A non-
http(s)url=is refused — afile://orchrome://landing page is a local-read primitive wearing a link's clothes. - An unknown key is ignored with a warning; an unknown action refuses the whole
URL (so a future
gb://exportcan never be half-executed by an older build); an over-long or implausible value is rejected rather than passed through. - A link naming an
accountthis machine is not signed in to is refused, rather than applied on trust. - The link is read from the OS scheme dispatch only, never from in-page
navigation. A web page that emits a
gb://link still goes through the operating system's own “open in GodBrowser?” prompt — that prompt is the confirmation step, and it is why a site cannot silently reconfigure your browser.
Where it stands today. Registration, parsing and every refusal above are verified. Delivery from a real click on macOS is not working yet (the system hands a custom scheme to the app as an Apple Event rather than on the command line), and Windows registration is still pending — so treat this as documentation of what arrives in the next build, not of what the currently published binary does.
No flag matches that search. Try the flag name (--bot-profile), a surface
(canvas, webgl, proxy) or a value.
Persona & identity
1 flagsThe core selectors + config overrides + host-coherence that derive a whole coherent identity from a single seed — the same seed reproduces the same fingerprint on any machine. Without a profile, the binary is plain Chromium.
--bot-persona-class
Declares the launch persona class, which unlocks persona-appropriate features. default = a standard persona that looks like real Chrome (no extra behavior). adblock-desktop = declares an adblocker-user desktop persona and enables --bot-block-trackers. trusted-scrape = declares trusted, non-adversarial automation and enables --bot-block-trackers.
GodBrowser --bot-persona-class=adblock-desktop --bot-block-trackers=on https://example.com/Locale, language & time
0 flagsLanguage, locale, timezone and geography — kept coherent with each other and with the persona's OS.
Screen & display
1 flagsViewport, screen metrics, orientation and colour scheme.
--bot-disable-screenxy-farble
Opts out of the per-profile screenX/Y+screenLeft/Top [0,50]px offset (hashed from CanvasNoiseSeed(); headless reports 0/0 which anti-bot detectors flag). Presence-only; default absent → offset applied.
GodBrowser --bot-disable-screenxy-farble https://example.com/Graphics, media & WebRTC
2 flagsThe rendered-surface identity — WebGL / WebGPU renderer, codecs, WebRTC SDP, speech voices, WebAuthn and the V8 stack profile.
--bot-disable-webgl-getparameter-cloak
Bisect (Wave R3.2): disables the W1.5b getParameter cloaks (anisotropy cap, MAX_TEXTURE caps, bit-depth, aliased line/point ranges). Presence-only; default absent → cloaks active.
GodBrowser --bot-disable-webgl-getparameter-cloak https://example.com/--bot-disable-webgl-vendor-spoof
Bisect: disables the WebGL vendor/renderer spoof, returning the host GPU identity (short-circuits getParameter UNMASKED_VENDOR/RENDERER + GL_VENDOR/RENDERER). Presence-only; default absent → spoofed.
GodBrowser --bot-disable-webgl-vendor-spoof https://example.com/Noise & farble seeds
0 flagsDeterministic per-seed farble applied to canvas, audio, WebGL, client-rects and text-rects — plus the scale of each.
Granular spoof toggles
5 flagsPer-surface spoof on/off toggles (JS-injection + C++-binding). Every spoof is on by default for a coherent persona; disable one only to isolate a surface during testing.
--bot-disable-netinfo-spoof
all [RF], presence-only, default absent → active.
GodBrowser --bot-disable-netinfo-spoof https://example.com/--bot-disable-permissions-spoof
all [RF], presence-only, default absent → the named JS-injection spoof block is active. Launch with --bot-profile=X + one flag to isolate an offending channel against a detector.
GodBrowser --bot-disable-permissions-spoof https://example.com/--bot-disable-plugins-spoof
all [RF], presence-only, default absent → active.
GodBrowser --bot-disable-plugins-spoof https://example.com/--bot-disable-ua-spoof
all [RF], presence-only, default absent → active.
GodBrowser --bot-disable-ua-spoof https://example.com/--bot-disable-window-chrome-spoof
all [RF], presence-only, default absent → the named JS-injection spoof block is active. Launch with --bot-profile=X + one flag to isolate an offending channel against a detector.
GodBrowser --bot-disable-window-chrome-spoof https://example.com/Misc persona & UI
0 flagsMiscellaneous persona and window / UI details.
Freshness-tell mitigations
0 flagsMitigations for freshness tells — the small signals a brand-new profile would otherwise leak.
Behavior & humanization
1 flagsHuman-looking timing, pointer motion and tab activity — the behavioural layer above the static fingerprint.
--bot-click-indicator
Shows you where your clicks land. With this on, every click the browser makes leaves a small circle at the exact spot it was delivered, fading out after about a second - so when you are watching a run, you can see the landing point instead of guessing it from how the page reacts. Clicks are aimed slightly off-centre on purpose (it is what a real hand does), so the mark is often not the pixel the script asked for - the mark is the truth. The circle is drawn by the browser itself, outside the page: a site cannot see it, and it never blocks a click. Off unless you ask for it, and it does nothing in headless mode.
GodBrowser --bot-click-indicator https://example.com/Proxy, network & TLS
3 flagsDeterministic per-profile proxy assignment, egress-country pinning, resource control and the uTLS / JA4 persona for Safari and Firefox.
--bot-block-trackers
Opt-in speed mode — blocks known ad/tracker requests before the network stack starts them, so pages load faster and use less bandwidth. Default off; a blocked request completes as an empty response (the page keeps working, no load errors).
GodBrowser --bot-block-trackers=on https://example.com/--bot-direct-resources
⛔ WITHDRAWN AND INERT (T-1599, patch 1007, 2026-09-05) — Nothing, from patch 1007 on. It still parses, so an existing invocation keeps launching, but no resource is ever direct-routed. ⚠ On a build BEFORE patch 1007 the bypass is still ACTIVE and publishes this machine's real IP to third-party origins beside the proxy exit — do not pass it on any build. ShouldBypassProxyForRequest() returns false unconditionally. Same for the $GODBROWSER_RESOURCE_DIRECT env fallback. Passing it logs one WARNING — which, measured, is only visible under --enable-logging=stderr, because nothing the network-service process logs reaches stderr at default verbosity.
--bot-tls-mimic
Declares the intended TLS-mimicry mode. STUB — parsed/stored, no rewriting yet.
GodBrowser --bot-tls-mimic=firefox https://example.com/Session & state
4 flagsCross-machine logged-in state, session persistence and account-secrets — plus pre-seeded cookies, bookmarks, history and headers.
--bot-account-key
Inline form of --bot-account-key-file — pass the account key (gbk_…) directly. Prefer the key file or the GB_ACCOUNT_KEY env form on shared hosts. Activation only: the metered account services read a key FILE, so an inline key does not unlock them on its own. The spoof is unaffected either way.
GodBrowser --bot-account-key=gbk_xxxxx https://example.com/--bot-account-key-file
Activate this device: a 0600 file whose first line is your account key (gbk_… from the portal dashboard). This is the ACTIVATION check. The metered account services (OTP, cookie fetch, Cortex dispatch, captcha) read --bot-account-secrets-key-file — point BOTH at the same key file, or put the key at ~/.godbrowser/account.key and pass neither. The anti-fingerprint spoof runs with or without a key.
GodBrowser --bot-account-key-file=~/.godbrowser/gb_account.key https://example.com/--bot-account-validate-url
Override the account-validation endpoint (self-host / staging). Defaults to the GodBrowser service; you rarely need this.
GodBrowser --bot-account-validate-url=https://gb.example.com/functions/v1/gb-validate https://example.com/--bot-no-account
Run with no account at all — fully anti-fingerprint, no account check, metered services off. Use it for a pure private browse or when you don't want any account association.
GodBrowser --bot-no-account https://example.com/AI flows (register / login)
0 flagsNative register / login flows driven by the browser itself — the AI fills forms, completes steps and banks the account.
Captcha integration
0 flagsOptional captcha-service integration — provider, types, timeout and escalation.
BusyMate capture
0 flagsOptional native traffic capture that streams GodBrowser's own plaintext requests to BusyMate. Fully dormant unless turned on.
Disk hygiene / autoclean
0 flagsBackground per-profile reclaim of regenerable cache — dormant by default; preserves everything --persist saves.
Debug, self-test & lifecycle
0 flagsDebug, self-test and lifecycle flags for verifying a build.
Provenance tags
0 flagsRun / node provenance tags stamped onto a session.