Sessionweaver

Download

Get Sessionweaver.

One app on your own machine: hub, worker and UI together. Open it in its own window, a browser or on your phone.

Stable: manual updates, the tested build.

First release coming soon

Choosing the track: the Updates:Channel setting (and an installer flag) is coming soon. Until then installs follow the stable track. Everything else is the same for both.

Recommended

Sessionweaver app

The all-in-one app: hub and worker in a single app on your own machine, with its data in one folder. Drive it from its own window, any browser, or your phone. Add more machines later if you want to.

Download for macOS (Apple silicon)

coming soon

Other platforms

  1. macOS: open the .dmg and drag Sessionweaver to Applications. Windows: unzip and run Sessionweaver.exe. Linux: unpack the archive and run ./sessionweaver.

  2. The app opens its UI. Sign in to Claude Code once when asked, then start a session.

  3. To use it from a browser or your phone, open the address shown in the app’s settings, then add it to your phone’s home screen.

Data lives in one folder (on macOS, ~/Library/Application Support/Sessionweaver). To back up, quit the app and copy that folder. Early builds: treat them as preview.

Advanced: run a hub and workers across machines

Outgrown one machine? Run a dedicated hub on a server and add a worker on each machine that runs Claude Code. The desktop app and your phone then connect to that hub.

Hub (Linux server)

One hub per person. It serves the web UI and the phone app, and holds the database (Postgres 15). Workers connect to it.

Download hub for Linux x64first release coming soon

  1. Create a Postgres database and role named sessionweaver.

  2. Unpack the release and, as root, run the host setup. It creates the sessionweaver user, the systemd unit and /etc/sessionweaver/hub.env.

    sudo deploy/hub/setup-host.sh

  3. Put the database password in hub.env (root only, mode 600) and start the service. The UI is on port 5000.

    sudo systemctl enable --now sessionweaver-hub

  4. Mint a token per worker (shown once).

    sessionweaver-mint-worker-token <worker-name>

Updates keep running sessions alive: they live in their own processes, so the hub and workers can restart freely. A one-step installer for the hub is coming soon.

Worker: Linux (systemd)

Needs the claude CLI and git. No .NET needed with the release package.

Download worker for Linux x64first release coming soon

  1. On the hub, mint a token (shown once).

    sessionweaver-mint-worker-token <name>

  2. On the worker machine, as the user that will run sessions:

    bash install.sh --artifact worker-<ver>-linux-x64.tar.gz

  3. Edit worker.env:

    Worker__HubUrl=http://<hub>:5000/hubs/worker
Worker__Token=<token>
Worker__Name=<name>
Worker__MaxSessions=2

  4. Restart the worker and let it run without a login:

    systemctl --user restart sessionweaver-worker && loginctl enable-linger $USER

The worker updates itself from the hub.

Worker: macOS

Runs as a LaunchDaemon so it keeps working with no one logged in. Apple silicon.

Download worker for macOS (arm64)first release coming soon

  1. Use a dedicated standard user (for example sw), with Remote Login on.

  2. Install the claude CLI as that user (native installer) and sign in.

  3. Mint a token on the hub, then create worker.env with the same four settings as on Linux.

    Worker__HubUrl=http://<hub>:5000/hubs/worker
Worker__Token=<token>
Worker__Name=<name>
Worker__MaxSessions=2

  4. As that user, run the installer. It asks for sudo only to write /Library/LaunchDaemons/com.griffhutt.sessionweaver-worker.plist.

    bash install.sh --artifact worker-<ver>-osx-arm64.tar.gz

Updates ad-hoc codesign the new build and let launchd restart the worker.

Worker: Docker

Good for a server where you would rather not install Claude Code on the host. Restarting the container ends its running sessions; checkouts and logins live in volumes.

  1. Clone the Sessionweaver repository and mint a token on the hub.

  2. Create deploy/worker/docker/.env (mode 600) with SW_WORKER_TOKEN, SW_WORKER_NAME and optionally SW_HUB_URL.

  3. Build and start the worker:

    docker compose -f deploy/worker/docker/docker-compose.yml up -d --build

  4. Log Claude in, if you use a local account:

    docker exec -it sessionweaver-worker env CLAUDE_CONFIG_DIR=/home/node/.claude claude login

The compose file sets name: sessionweaver-worker. If you already run it under another project name, keep that with -p <name> so your volumes are reused. The image is built locally for now; a published image is coming soon.

Desktop app

A native window onto your hub, with the same UI. Linux x64; it updates itself once a worker is installed on the same PC.

Download desktop for Linux x64first release coming soon

  1. Install straight from your hub:

    deploy/desktop/install.sh --hub http://<hub>:5000

  2. Or, from a downloaded file:

    deploy/desktop/install.sh --artifact desktop-<ver>-linux-x64.tar.gz

It installs under ~/.local/share/sessionweaver/desktop and adds a launcher. No .NET needed. Windows and macOS desktop builds: coming soon.

Phone

No app store needed: the hub’s UI is built for phones and installs from the browser.

  1. Open your hub’s address in your phone’s browser.

  2. iPhone: Share, then Add to Home Screen. Android: the menu, then Install app or Add to Home screen.

  3. Open it from the new icon.

Reach the hub from outside your network over a VPN or a reverse proxy you trust.