Skip to main content

Settings: System

System settings describe what the app may access, which trusted owner devices may connect, and how it runs on your machine. This is where you adjust Remote Access, workspace boundaries, shell behavior, browser automation, opt-in native Computer Use, tunnels, and diagnostics.

Settings: System in Row-Bot.
The System tab contains local runtime choices, workspace access, Remote Access, tunnels, and diagnostic controls.
Remote Access controls in Row-Bot System settings.
Remote Access keeps private reachability, one-time owner invitations, connected devices, and explicit LAN access in one owner-only section.

Where To Find It​

Open Settings, then choose System from the left tab list.

Controls​

  • Workspace and filesystem controls define where Row-Bot may read or write when tools need local files.
  • Shell and command controls affect whether command-running tools are available and how approvals apply.
  • Browser controls select a supported installed Chrome or Edge channel or Row-Bot's exact managed Playwright Chromium revision. Install and Repair are explicit actions; normal startup only checks readiness and never downloads a browser.
  • Computer Use controls keep native application automation separate, off by default, and gated by platform readiness, telemetry disclosure, and a verified optional runtime.
  • Remote Access creates one-time desktop or compact owner invitations, checks or configures an owned Tailscale Serve route, explicitly enables LAN listening, and revokes devices or sessions.
  • Window mode chooses whether Row-Bot opens in its own app window, the system browser, or asks at launch.
  • Tunnel settings are for external callback use cases such as channels that need a public webhook URL.
  • Log and diagnostic controls help support troubleshooting without changing your model setup.

Common Workflow​

  1. Keep workspace access narrow for everyday use.
  2. Enable shell or browser automation only when you intend to use those tools.
  3. Enable Computer Use only on an interactive Windows or macOS desktop after reviewing its separate setup and safety guide.
  4. Use Remote Access only after choosing the narrowest connection route and the presentation layout for the invited owner device.
  5. Use tunnels only for channels or integrations that explicitly require inbound webhooks.
  6. Collect logs from this tab when troubleshooting startup or provider issues.

What Is Saved​

System settings are global for the active Row-Bot data directory. Remote Access stores hashed invitation and session secrets plus revocable owner-device records in the shared access database. Workspace files are not uploaded to Row-Bot; external providers may still receive content when a model or tool request sends it.

Privacy And Safety​

Remote reachability never grants access on its own. Every non-local browser needs a Row-Bot session. Treat unused invitation links as passwords, prefer Tailscale or HTTPS over remote LAN HTTP, and revoke lost or retired devices. Every authenticated browser is the same owner; compact and desktop layouts do not change authority. Review credential, account, channel, provider, or tool settings before enabling features that can contact outside services.

Control-Level Reference​

The generated Settings Controls reference lists the visible controls found in the current application source, including defaults, allowed values when they are declared inline, dependencies, restart notes, security notes, and source locations.

Troubleshooting​

  • If Row-Bot cannot read a file, check whether it is inside the allowed workspace.
  • If Browser reports a missing or mismatched managed runtime, use Install browser runtime or Repair. Do not copy another Playwright cache into Row-Bot's managed location.
  • If Computer Use is unavailable, open its setup card and follow the reported runtime or operating-system permission recovery step.
  • If a remote URL shows a JSON access error, use the Remote Access troubleshooting table instead of broadly trusting proxy headers or disabling the access gate.
  • If a tunnel URL is unavailable, check the tunnel provider credentials and whether the tunnel is running.
  • If the app opens in the wrong place, change Window mode and restart Row-Bot.