Before you begin
- A computer to run Ryspar. The current build runs on Apple silicon Macs running macOS 13 or later, Windows 10 or later on x64, and x64 Linux, Ubuntu 22.04 or newer.
- Claude Code or Codex. If neither is set up yet, Ryspar can open a terminal with the install or sign-in command ready.
- Git, if you want worktrees, diffs, commits, and pull requests.
- Your provider plan or API key. Ryspar is free; each provider bills its own usage.
Install Ryspar
Download Ryspar 1.0.11, released November 12, 2026, and install it the way you install other apps on your computer.
The first time you open Ryspar, a short setup walks through three steps: Connect, Agents, and Projects. The computer you opened Ryspar on is already connected and selected, so you can move straight on. You can skip any step and come back to it from the progress bar.
Connect your agents
Setup checks for Claude Code and Codex. If one isn't installed or signed in, select its action and Ryspar opens a terminal with the right command ready. Review it, then press Enter. Installs use each vendor's own installer, so updating them from Ryspar keeps working later.
| Agent | Install and sign in |
|---|---|
| Claude Code | Install Claude Code, then run claude auth login. |
| Codex | Choose Connect with ChatGPT during setup or in Settings → Providers, and Ryspar installs Codex for you. Or install the Codex CLI and run codex login. |
| Cursor | Install Cursor CLI, then run agent login. |
| Grok Build | Install Grok Build CLI, then run grok login. |
| OpenCode | Install OpenCode, then run opencode auth login. |
| Antigravity | Sign in with Google from Ryspar's provider settings. |
| Pi | Install Pi, then run pi once to finish its login or API-key setup. |
Turn on other agents in Settings → Providers. Their CLIs must be on the PATH of the computer where agents run. If you installed one through a version manager and Ryspar can't find it, set its Binary path there. Add another provider instance to use a second account.
Choose your projects
Ryspar lists the folders Claude Code and Codex have worked in. Git repositories come first, newest activity on top, and clones of the same repository share one group. Other folders are listed separately.
Repositories active in the last 30 days with at least three conversations are selected for you. Change the selection with the checkboxes, then import. Each project brings its Claude Code and Codex conversations from the last 30 days, and you can continue them in Ryspar.
Import is best effort. It keeps the first prompt and the newest messages, up to 200 per conversation, and leaves tool activity and attachments behind. Very large histories import in batches; run import again to continue.
Skipped this step? Add a project any time with Add project in the command palette (⌘ K), or start from nothing with New project.
Run your first task
Pick something small and visible, like a change to a page, so checking the result is easy.
- Press ⌘ N for a new thread. The card at the top shows the project and where the thread will work. Choose New worktree if the change should get its own branch.
- Describe the change and send it. The permission mode in the composer decides when the agent asks first: Supervised asks before commands and file changes, while Full access, the initial default for new threads, doesn't ask. Change the default in Settings → General.
- While it works, start something else. ⌘ ↩ sends the current draft and opens a fresh one.
- When it's done, open the browser from the panel beside the conversation and check the running app. Your agents see the same tabs you do, so you can ask for a correction in the same thread.
- Click the Git button at the top right of the thread to see Changes, then commit, push, and create a pull request. Ryspar can draft the commit message and description from your changes.
Shortcuts use ⌘ on macOS. On Windows and Linux, use Ctrl instead.
Keep parallel work in view
- Set Settings → General → Thread order to Inbox. Threads that wait on you, for an approval, an answer, a ready plan, or a failure you haven't seen, move to the top.
- ⇧ ⌘ U jumps to the next thread that needs you, and the app icon's badge counts them.
- Drag a thread from the sidebar onto a chat to open them side by side. Up to four chats fit together.
- Settle finished threads from their menu to clear the list without deleting anything. By default, threads settle after three days without activity, or once their pull request merges.
- If a provider's usage limit stops a thread, choose Resume at reset to continue automatically when the limit lifts.
Connect another device
Your agents run on one computer, the host. Another device can work with it while the host stays on and reachable. Projects, provider sign-ins, and agent work stay on the host.
On your network or tailnet
On the host, open Settings → Connections, turn on Network access, and create a pairing link using an address the other device can reach. Open the link in a browser on that device, or paste it into Add environment in another Ryspar desktop app. Turning on network access restarts the desktop app. Use a fresh link for each new device.
From your iPhone
Install the iPhone app, in beta on TestFlight. Create a pairing link on the host as above, then in the app open Settings → Environments, add an environment, and scan the link's QR code or paste the link.
Over SSH
In the desktop app, open Settings → Connections → Add environment, choose SSH, and enter a host such as user@my-server. Ryspar starts a server there and forwards the connection for you. This release supports Apple silicon Mac hosts with curl or wget, tar, and sha256sum or shasum, plus your agents' CLIs.
From the command line
With the Ryspar CLI installed on the host, start a server on its private address, then create a pairing link:
ryspar serve --host <private-ip>
ryspar pairCosts and data
- Ryspar is free. There's no Ryspar account or payment.
- Agents use your own provider accounts, and each provider bills its usage. Usage (⌘ U) estimates token use and API-equivalent cost across providers. It's an estimate, not your bill.
- Projects, threads, and settings live on the host. Agents send prompts and the code they work with to their providers. The privacy policy covers the details.
Get help
Message @ryspardev on X or email support@ryspar.dev. Include your Ryspar version and operating system, what you tried, and what happened. Above all, tell us what stopped your first useful task.
Bug reports are also welcome as issues on Ryspar's public release repository(you'll need a GitHub account).
If Ryspar crashes at startup, open Settings → Diagnostics after the next successful launch, and review any report for private data before you share it. Report security problems privately, as described in Security reports.