1. Check what it needs

    • macOS or Linux, on arm64 or amd64.
    • git.
    • tmux, for lanes that run in a terminal pane.
    • The Claude Code CLI, installed and signed in through Anthropic's own flow. This release is qualified on Claude Code 2.1.316, 2.1.317, and 2.1.319. On another version, the worker checks the CLI on its own machine before the first lane starts on it, and Qualification says what that check covers.

    Solo mode needs no Docker, no account, and no network connection of its own.

  2. Install it

    Use one channel.

    Homebrew

    Homebrew
    brew install bkuberek/tap/ropeshift

    Homebrew may ask you to trust the tap first. If it does, run this once:

    Trust the tap
    brew trust bkuberek/tap

    The install script

    Install script
    curl -fsSL https://raw.githubusercontent.com/bkuberek/ropeshift/main/install.sh | sh

    With no --version, the script installs the newest stable release, or the newest pre-release while no release is stable, and says which it chose. It checks the archive's SHA-256 against the release's checksums file before it extracts anything, and installs to ~/.local/bin. The checksum proves that the download matches the release's own list. It does not prove who made the release, because releases are not signed yet.

    Options go after sh -s --, such as a version and a prefix:

    Install script with options
    curl -fsSL https://raw.githubusercontent.com/bkuberek/ropeshift/main/install.sh | sh -s -- --version v0.1.0-alpha.14 --prefix /usr/local

    Releasing lists every option.

    Debian, Ubuntu, Fedora, and RHEL

    Download the .deb or .rpm package for your architecture from the release page for v0.1.0-alpha.14 (opens in a new tab), and install it with sudo dpkg -i ropeshift_<version>_<arch>.deb or sudo rpm -i ropeshift-<version>-1.<arch>.rpm. Package names carry the version in the packaging system's form, such as ropeshift_0.1.0.alpha.14_arm64.deb and ropeshift-0.1.0.alpha.14-1.aarch64.rpm. Both packages recommend git and tmux.

  3. Check the installation

    Shell
    ropeshift version

    It prints the release, the commit it was built from, and the platform.

  4. Set up the machine

    Shell
    ropeshift init

    It asks for the first passphrase on the terminal, twice, and never reads one from stdin, a flag, or a variable. It then runs the doctor, which says for each agent CLI what to do next, and writes a sample contract to the installation's directory. A second run says only what is left. It exits 0 when an agent CLI is usable and 1 when none is.

  5. Start the daemon

    Shell
    ropeshiftd solo --source /path/to/repository

    The daemon reads work from the repositories it names, and serves the web UI at http://127.0.0.1:7317, on loopback only. ropeshift top watches the same fleet from a terminal.

    Run it as a service

    To keep the daemon running under this machine's service manager, install it as a service with the same flags:

    Shell
    ropeshift service install -- --source /path/to/repository

    A Homebrew install can run it with brew services start ropeshift instead, with no repository source. Use one or the other, not both, because two daemons for one installation conflict. The install script and the packages install no service.

    On Linux, turn on lingering once, so lanes keep running after you log out and the daemon starts at boot:

    Shell
    loginctl enable-linger "$USER"
  6. Before the first lane

    In solo mode, lanes run as the same operating system user as you, so the operating system does not separate an agent from your files. A repository's own configuration can also run code. Before the first lane says what that means and which boundaries help.

    Continue with the onboarding guide to run the sample contract as your first lane.