LINUX SERVER & HEADLESS OPERATIONS
Run on a server. Understand the headless difference.
Linux server operation is possible with a virtual display, even when no physical monitor is connected. This is not the same as a certified native headless runtime. This guide separates proven operation from capabilities still being validated.
Windows & LinuxBrowser API / CDPPersistent ProfilesMCP AI
Deployment and capability status
| Operating mode | Current status | What it means |
|---|---|---|
| Desktop graphical session | Available | Standard Windows or Linux desktop installation. |
| Linux server with Xvfb | Observed on a running server | Electron runs using a virtual X display, without a physical monitor; an active browser process is still required. |
| Native no-display headless mode | Not yet certified | Do not assume all Profiles, extensions, automation and session behavior work identically until a dedicated test suite passes. |
Technical accuracy matters
Virtual-display server operation is not a guarantee of unattended restart recovery, unlimited concurrency or native headless support. Verify against your exact build and workload.
Example: virtual-display launch
The command below illustrates the Linux Xvfb wrapper. Replace the placeholder with the launcher from your installed build; it is not a universal installer command.
xvfb-run -a -s "-screen 0 1920x1080x24" \
/path/to/your-social-browser-launcherBefore running production workloads
- Verify the installed release, desktop dependencies and Xvfb packages.
- Use a dedicated service account and persistent, backed-up Profile storage.
- Keep API/CDP endpoints bound to localhost or behind authenticated, encrypted access.
- Test restart recovery, multi-Profile concurrency, cookies, proxies and target discovery.
- Monitor process health and memory, and verify jobs after display/session disconnection.