How to Run Social Browser from Source Code — 2026.10.01 Developer Guide

Updated for Social Browser 2026.10.01. The browser source code is maintained on GitHub at github.com/social-browser/browser. This guide reflects the current development scripts and build flow.

Clone the current repository

git clone https://github.com/social-browser/browser.git
cd browser

Install dependencies

Install the project dependencies using the package manager and lockfile included in the repository. Native Electron dependencies may require platform build tools.

npm install

Build the preload separately

The current development workflow intentionally keeps preload compilation separate from normal application startup. Run:

npm run preload

After the preload output is prepared, start the Electron application with:

npm start

Important: npm start now runs electron .. It does not implicitly rebuild the preload bundle.

Run smoke tests

The repository includes a broad smoke-test suite. A useful first check is:

npm run test:smoke

Before release work, the project also exposes a production release gate:

npm run test:production-release-gate

Build Windows and Linux packages

The current production scripts include platform-specific release preparation:

npm run production:win
npm run production:linux

There are also lower-level packaging scripts such as npm run win, npm run linux, npm run pack and npm run dist. For release work, prefer the production scripts because they are designed around the current release pipeline and validation gates.

Architecture notes

• Social Browser is an Electron/Chromium desktop application.
• Browser Profiles are isolated browser workspaces with separate state.
• Profile/browser work is coordinated through dedicated processes and browser-management layers.
• Automation Studio, User Scripts, extensions, Browser API and MCP are separate integration surfaces for different kinds of automation and customization.
• The current 2026.10.01 release line includes ongoing work around Profile portability, Site Data handling and runtime stability.

Useful development commands

• npm run preload — build the preload output.
• npm start — start Electron using the already prepared preload output.
• npm run test:smoke — run the main smoke suite.
• npm run test:production-release-gate — run release-gate checks.
• npm run production:win — prepare/build the Windows release path.
• npm run production:linux — prepare/build the Linux release path.

Contributing and testing

Before proposing a code change, reproduce the issue, identify the root cause, implement the smallest safe fix, and run the related regression tests. Changes that affect browser lifecycle, Profiles, automation, IPC, preload, extensions or native modules should be tested against related areas rather than only the direct symptom.

Source repository: https://github.com/social-browser/browser

Ready build: Download Social Browser