Desktop app

Run coding agents on your own machine

ScrumDo Runner connects your computer to Spryng and runs the local agent runner — connect multiple runtimes, configure everything, and let them work in the background. No Docker. No terminal.

v0.1.22 · macOS 12+ (Apple Silicon) · Windows 10/11 · free · open runner

Get ScrumDo Runner

Pick your platform. The desktop app is a native menu-bar UI; on Linux and servers, use the CLI.

macOS

macOS 12 Monterey or later · Apple Silicon (arm64)

Download .dmg

Signed & notarized by Apple — installs with no Gatekeeper warning. All releases.

Windows

Windows 10 / 11 · 64-bit

Download installer

Setup .exe or .msi. SmartScreen may warn until the build is signed — choose More info → Run anyway.

Everything the runner does, with a UI

Multiple runtimes

Connect any number of machines or engines. Each runs as its own supervised process with independent, live status.

Full configuration

Every option in one panel — engine, delivery mode, repo mappings, poll cadence, permission mode and SSRF allow-list.

Secure by design

Your connect credential and BYOK keys are stored in the OS keychain, never a plaintext file. The runner is outbound-only.

Always-on

Crashed runners auto-restart with backoff. Closing the window hides to the menu-bar tray so your agents keep working.

Up and running in three steps

1

Install

Download the app for your OS, or install the CLI with pipx on Linux.

2

Paste your connect code

In Spryng, open a runtime and copy its connect code. Paste it into the app to fill the connection in one step.

3

Start the runtime

Hit Start. The agent runner picks up work from Spryng and runs it right on your machine.

Prefer the terminal?

The same runner ships as the spryng-agent CLI — perfect for Linux boxes, servers and CI. Install it with pipx, sign in with a connect code, and start the pull loop.

  • Works on Linux, macOS and Windows
  • Bring your own engine (Claude, Codex, Grok) and keys
  • Outbound-only · credentials stored locally
View on PyPI
Install the runner
      $ pipx install spryng-agent

      Connect + verify + run
      $ spryng-agent login
      $ spryng-agent doctor
    $ spryng-agent run
Complete Linux setup guidePrerequisites → install → connect → run · about 5 minutes
  1. Check prerequisites

    You need Python 3.11+, git, and pipx. Most distros already ship Python and git — confirm with:

    python3 --version && git --version
  2. Install pipx

    pipx installs the CLI into its own isolated environment and puts it on your PATH.

    python3 -m pip install --user pipx && python3 -m pipx ensurepath

    On Debian/Ubuntu you can instead run: sudo apt install pipx. Open a new shell afterwards so the PATH change takes effect.

  3. Install the runner

    Install the spryng-agent CLI from PyPI.

    pipx install spryng-agent
  4. Install & sign in to your engine

    The runner drives an engine CLI you already use — Claude Code, Codex or Grok. Install the one you want and sign in so it is authenticated and on your PATH.

    Grok is bring-your-own-key: export XAI_API_KEY=<your xAI key>. Claude and Codex use their own login command.

  5. Connect to Spryng

    In Spryng, open your runtime and copy its Runtime ID and connect credential. Run login and paste them when prompted (the base URL defaults to app.spryng.io):

    spryng-agent login

    Stored in ~/.spryng/agent.toml with 0600 permissions — your credential never lives in a world-readable file.

  6. Verify the setup

    doctor checks the engine CLI, git, engine authentication and that Spryng is reachable — it catches problems before any card runs.

    spryng-agent doctor
  7. Start the runner

    Start the pull loop — it picks up work from Spryng and runs it on your machine. For a single repo, cd into it and add --use-cwd; for several repos, map each first with spryng-agent workspace add owner/name /path.

    spryng-agent run

Your connection is saved to ~/.spryng/agent.toml. If a step fails, spryng-agent doctor tells you exactly what to fix.

System requirements

macOS

macOS 12 Monterey or later. Apple Silicon (arm64).

Windows

Windows 10 or 11, 64-bit. Unsigned for now — SmartScreen may warn.

Linux / CLI

Python 3.11+ with pipx. Any distro.

Engines

The engine CLI you use (Claude / Codex / Grok) installed and on your PATH.

🔒 Secrets are stored in your OS keychain. The runner is outbound-only — your code never leaves your machine.

Questions

Does my code leave my machine?

No. The runner works in your local checkouts and only makes outbound calls to Spryng to pick up work and report status. There are no inbound connections.

Where are my credentials stored?

The connect credential and any bring-your-own API keys are kept in your operating system keychain (Keychain on macOS, Credential Manager on Windows) — never in a plaintext config file.

What is the difference between the app and the CLI?

They run the same runner. The desktop app is a UI that supervises one or more runtimes with configuration, status and readiness checks. The spryng-agent CLI is the same runner for the terminal — ideal for Linux, servers and CI.

Which engines are supported?

Claude, Codex and Grok. You point each runtime at the engine CLI you already have installed and, if you use your own keys, add them per runtime.

Is the download safe to install?

Yes. The macOS app is signed with an Apple Developer ID and notarized by Apple, so it installs with no Gatekeeper warning. On Linux, Windows and servers you can run the same runner today via the spryng-agent CLI from PyPI.

ScrumDo Runner

Bring your runtimes online

Download the app, paste a connect code, and your machine starts doing the work.