Documentation
Proxies and bot identity
Choose a network route and site identity from the human window.
Use the window to configure proxies and bot identity for a space. Only the human can set them. settings(proxy) is not an agent permission to change the network.
Set the proxy before browsing
Review the proxy host, port and any credentials in the space’s network controls. Do not put proxy credentials into prompts. A saved space’s proxy configuration is sealed with the vault. Proxy errors must not expose passwords in logs.
A space’s proxy applies to browser pages and supported direct-fetch and map operations. If a proxy is required, resolve its failure before continuing. Do not silently change the route to avoid a site restriction.
An agent can inspect network status:
{"name":"space","arguments":{"action":"network"}}Bot identity
The window offers human-owned identity controls. Choose an identity that accurately describes your permitted use. Do not use it to impersonate someone else or evade a site’s rules. Identity settings and arbitrary headers are not writable through MCP.
Local addresses
Local-network access is a separate human choice. Agents and pages cannot reach Swarmtab’s own control or Chromium debugging ports. Do not expose those ports to a LAN. Read Real browser mode for the browser identity selected by the owner in this build.