Install Friday and start your first session

Updated 28 October 2026

Friday is free and open source (MIT). It runs on your own computer with no account. Install it, sign in to a coding tool, and start a session in your repository.

Before you install

Install and sign in to at least one coding tool first. Friday finds every one on your computer and can sign the rest in from its setup screen. Each tool signs in the way it always does:

ToolSign in with
Claude Codeclaude auth login
Codexcodex login
Cursorcursor-agent login
GitHub Copilotcopilot login
OpenCodeopencode auth login
Gemini CLIRun gemini once and sign in

Install the desktop app

ComputerDownload
Mac, Apple siliconFriday-arm64.dmg
Mac, IntelFriday-x64.dmg
WindowsFriday-Setup.exe
LinuxFriday-x86_64.AppImage (make it executable with chmod +x, then run it)

The Mac app is signed and notarized by Apple, so it opens like any other. The Windows installer is not signed yet, so Windows asks before running it the first time: choose More info, then Run anyway.

On a Mac, Homebrew installs it too:

brew tap splashxmoon/friday https://github.com/splashxmoon/friday
brew trust splashxmoon/friday
brew install --cask friday

Every version is on the releases page. The app is Friday in a window of its own, with the same server inside it, on 127.0.0.1 only.

Or run it from a terminal

With Node.js 22 or newer and Git:

npx github:splashxmoon/friday

Friday opens in your browser at http://127.0.0.1:4321. To keep a copy:

git clone https://github.com/splashxmoon/friday
cd friday
npm install
npm start
SettingDefaultWhat it does
PORT4321Where Friday listens, on this computer only
FRIDAY_HOME~/.fridayWhere it keeps your sessions and settings
--no-openStart without opening the browser

Start your first session

  1. Open Friday. It lists the coding tools it found on your computer and whether each is signed in.
  2. Start a session in your repository with one of them.
  3. Add a second tool from the session’s agent bar. Each tool can work in its own copy of the repository, so they do not overwrite each other.
  4. Give them the job. They can split it on a task board and message each other as they work.
  5. Read each run’s changes before you keep them.

Related