Skip to content
ryan-stoffelPublic

About

Run coding agents on computers you own, and check on them from anywhere.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

3 stars

Watchers

0 watching

Forks

Latest commit

 

History

1,403 Commits

Folders and files

Parallax

Parallax

Run coding agents on computers you own, and check on them from anywhere.
Open source. Desktop app for macOS, Windows, and Linux, with a web app and an iOS app.

Install  ·  Releases  ·  Parallax Connect  ·  Plan

Latest release macOS, Windows, and Linux Apache-2.0 license

Parallax: an orchestrator thread, approving a subagent's command, then a thread with its diff in the side panel

Parallax is a desktop app for the coding agents you already pay for: Claude Code, Codex, Cursor, OpenCode, Ollama Cloud, and any agent that speaks ACP. You give an agent a task, it works in its own git worktree, and you review the diff when it's done. Run one agent on one task, or hand a whole feature to a coordinator that splits it across several.

The agents run in plxd, a Rust daemon, on whichever computer you choose: this one, a desktop at home, or a Linux server you reach over SSH. On another computer, a long task keeps going with your laptop closed. You sign in to each provider on that computer, and Parallax runs it with your subscription or API key.

Threads

A thread is one agent working on one task. Pick a repository, say what you want, and the agent works in a fresh worktree. Every turn is checkpointed, so you can see what a turn changed and revert it. The side panel holds the diff, a terminal, the files, a browser the agent can drive, and the pull request.

A thread that reworked the app's updater, with the diff of its three files in the side panel

Orchestrator threads

An orchestrator thread is for work bigger than one chat. It plans the work, starts a subagent for each piece in its own worktree, and keeps a status board in its shared notes. It answers routine questions itself and brings you only what needs you: an approval, a decision, a failed test.

An orchestrator thread beside its status panel: three items waiting on you, two subagents working, two done

Your computers

  • Local, SSH, or Parallax Connect. The app attaches to plxd on this computer, on any machine you can ssh into, or on any computer on your Parallax account. Parallax Connect reaches a computer over its LAN or Tailscale address when it can, and through Parallax Relay when it can't, with TLS end to end, so the relay can't read your threads. Run npx plx-cli connect on a computer to add it.
  • Triggers. Schedules, webhooks, and pull request watches wake an agent while you're away.
  • Agent tools. Agents can drive a browser, render HTML, and run the iOS Simulator and Android Emulator.

On your phone and in a browser

  • iOS app. Sign in to your Parallax account, and it lists your computers. Allow the phone once on a device you already use, and it reaches them all, at home or away. It can also pair with a computer on the same network, using the code from Pair a device. Open a thread to read it, approve a request, or send a reply. A message sent offline goes out when the phone reconnects. The app lives in apps/mobile. It isn't on the App Store.
  • Web app. plxd serves the app over HTTPS on your network, and there's no hosted version. In Settings > Connections, turn on Pair computers on this network and Open in a browser, then choose Pair a device. Open the address Settings shows, and enter the code.

The web app in a browser, showing a finished thread   The iOS app's thread list A thread open in the iOS app

In a terminal

parallax runs Parallax in your terminal, laid out like Claude Code, with the same threads, Projects, and orchestrators as the app, live in both. Run it in a git checkout and new threads work there in place. /settings signs in to providers and GitHub, adds API keys, and changes this computer's settings, so the terminal works without the app. /login jumps to the first provider that isn't signed in. It comes with the app, or installs on its own (see Terminal only).

Parallax in a terminal: a Claude Code thread that added an imperial option to a forecast formatter, its tool calls folded into one line

Install

These commands install the latest nightly. The app updates itself after that.

macOS (Apple silicon) and Linux (x64 and arm64):

curl -fsSL https://raw.githubusercontent.com/ryan-stoffel/parallax/develop/scripts/install.sh | sh

Windows (x64 and arm64), in PowerShell:

irm https://raw.githubusercontent.com/ryan-stoffel/parallax/develop/scripts/install.ps1 | iex

On macOS the app goes in /Applications. On Linux it's an AppImage in ~/.local/share/parallax-nightly, with a launcher entry and a parallax-nightly command. On Windows it installs for your user, with no admin prompt. Every installer is also on the releases page.

Then sign in to at least one provider on the computer that runs the work. The app sets up this computer's agents on first launch, and Settings > Providers covers any computer.

Terminal only

To run Parallax in a terminal without the app, on macOS (Apple silicon) and Linux (x64 and arm64):

curl -fsSL https://raw.githubusercontent.com/ryan-stoffel/parallax/develop/scripts/install-tui.sh | sh

It puts plxd in ~/.parallax-plxd and links ~/.local/bin/parallax to it. Run parallax to start. Run the command again to update.

Build from source

plxd builds with Cargo. The app needs Node 24 and pnpm through corepack (corepack enable). Run pnpm inside apps/desktop, where corepack finds the pinned version.

cargo build --release -p plxd

cd apps/desktop
pnpm install
pnpm dev

pnpm check formats, lints, and type-checks the app. pnpm test and pnpm build run the rest. scripts/ci/check-rust runs the same lint, build, and tests as CI for plxd.

pnpm exec vp dev -c preview/vite.config.ts serves the renderer in a browser at http://localhost:5199/ with a fake plxd and no Electron (apps/desktop/preview).

The design lives in docs/PLAN.md, and the decisions behind it in docs/decisions.

Usage data

The installed app sends three events to PostHog, so we can count how many installs are in use and how much they do:

  • app_active, at launch and once a day while it runs.
  • prompt_sent, for each prompt you send from the app, saying whether it started a thread or followed one up.
  • tokens_used, when you're signed in, for each hour and model plxd ran on this computer and the others on your account, with the tokens used and the cost when the vendor reports one.

Each carries an id, the app's version and channel, the OS and architecture, and whether you're signed in. Signed in, the id is a one-way hash of your Parallax account's id, the same on all your devices, so we count you once and can see your activity across them. Signed out, it's a random id made for the install. None carries your name, your email, your account's actual id, a path, the text of a prompt, or code, and PostHog adds no location from them. Set DO_NOT_TRACK=1 in the app's environment to turn it off. On macOS an app opened from the Dock or Finder doesn't read your shell profile, so run launchctl setenv DO_NOT_TRACK 1 and restart the app.

License

Apache-2.0

About

Run coding agents on computers you own, and check on them from anywhere.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

3 stars

Watchers

0 watching

Forks

Releases

Contributors

Languages