Worktree popover. Right-click a workspace or worktree for a new worktree, fan out, rename, Teleport, checkpoints, close, or delete the checkout. Double-click one to rename it.
|
Teleport. Move a worktree to another host with its commits, uncommitted changes, tabs, splits, running programs, and agent sessions.
|
Review an agent's changes. Open Review Changes from a tab strip's + menu, click any line to leave a note like a pull request comment, then Send to agent.
|
Side-by-side diffs and a collapsed sidebar. Switch the review to side by side, and fold the sidebar to a rail that keeps every workspace and agent one click away.
|
Browser tabs with annotations. An agent opens its page with sheprd browser open; you pick elements or regions, write notes, and send them back to that agent. Listening ports such as :4173 appear under their workspace.
|
Sidebar layouts. Pick a density or a design of its own from View > Layout or Settings; the choice applies live.
|
Plan usage. The status bar shows the signed-in AI services closest to their limits; click one for the details.
|
CPU and memory per host. The status bar follows the selected host, and with several hosts each sidebar host row shows its own, read over SSH for remote machines. NVIDIA, AMD, and Apple GPUs and their video memory can be turned on for the status bar and, on a line of their own, the sidebar.
Native settings. Grouped, searchable pages for themes, sidebar, fonts, tabs, notifications, and integrations; every change applies live to the open windows, and hovering a theme previews it in the app.
Sidebar page. Pick the layout and selection marks, tune spacing with sliders, and give each host its own colour.
|
Light or dark, or both. Any theme, or a light and dark pair that follows the system appearance; status colours keep their contrast on either.
|
Star your favorites. Pin the themes you keep coming back to at the top of the Color Scheme picker; one click stars or unstars a theme, and the stars are saved with your settings.
|
Hundreds of themes, one search away. Built-ins and Ghostty themes in one list: arrow or hover through them to preview each live, and your starred themes lead every search.
|
Also included: saved SSH hosts with [file copies](crates/sheprd-gpui/README.md#ssh-file-copies),
[inline images](crates/sheprd-gpui/README.md#images),
[clickable links](crates/sheprd-gpui/README.md#terminal-links),
[code navigation](crates/sheprd-gpui/README.md#code-navigation) that jumps to a
symbol, file, or printed `path:line` in your terminal editor,
[file drops](crates/sheprd-gpui/README.md#file-drops),
[editor groups](crates/sheprd-gpui/README.md#editor-groups), and
[system notifications](crates/sheprd-gpui/README.md#system-notifications),
[sounds](crates/sheprd-gpui/README.md#notification-sounds), and a
[Dock badge](crates/sheprd-gpui/README.md#macos-dock-badge) (on Windows, a
[taskbar badge](crates/sheprd-gpui/README.md#windows-shell)) when an agent needs you.
## Install
Release builds include a pinned herdr-core for local terminals. If Herdr 1 is
not installed, Sheprd opens a herdr-core shell; no separate daemon installation
is required. It joins an existing core first, otherwise starts your own
`herdr-core` or the bundled companion. Source builds need a usable herdr-core
binary for this path.
If you already use [Herdr 1](https://herdr.dev/), Sheprd connects to its sessions
and may start your installed `herdr server` when the target session is absent.
It does not upgrade or migrate your personal daemon or move existing Herdr 1
sessions to Herdr 2. Explicitly confirming session deletion stops that named
session first; closing or removing the GUI leaves daemon sessions and saved
configuration intact.
Then install the latest stable release:
| Platform | Command |
| --- | --- |
| macOS | `brew install penso/tap/herdr-gpui` |
| Linux (APT, DNF or pacman) | `curl -fsSL https://sheprd.org/install.sh \| sh` |
| Windows (PowerShell) | `irm https://sheprd.org/install.ps1 \| iex` |
Details, manual downloads, and other methods follow. Coding agents can read
[sheprd.org/llms.txt](https://sheprd.org/llms.txt) for the same steps.
The rename retains existing settings, sign-ins and install identities. See
[rebranding and rollout](docs/rebranding.md) for the compatibility inventory and
external rollout tasks; changing these source links does not deploy the site or
transfer the repository.
### macOS with Homebrew
Requires [Homebrew](https://brew.sh/) and macOS 14.2 Sonoma or newer, on Apple
Silicon or Intel. The cask installs the signed, notarized universal app.
```sh
brew install penso/tap/herdr-gpui
open /Applications/Herdr.app
```
`brew install` resolves casks directly, so `--cask` is not required. To update it
later, or to install by its short name, tap once first:
```sh
brew tap penso/tap
brew install herdr-gpui
```
The stable cask token remains `herdr-gpui` in `penso/tap`. It displays **Sheprd**
and installs the `Sheprd.app` payload at the legacy `Herdr.app` target so existing
clients can restart in place. The cask is published from the
[tap](https://github.com/penso/homebrew-tap) by the
release workflow. A cask install updates itself through Homebrew: the in-app
updater detects that Homebrew owns the bundle and runs `brew upgrade --cask
herdr-gpui` for you, so Homebrew's records stay correct. If its metadata is stale,
the updater runs `brew update` and retries once. The update panel shows progress
throughout. macOS `.dmg`, Linux packages, and Windows installers
and `.zip`s are also published on [Releases](https://github.com/sheprd-labs/sheprd/releases).
Betas are published as GitHub prereleases before being promoted to stable. To try
them, turn on **Settings > General > Install beta releases**
(`[updates] channel = "beta"`); turning it off never downgrades. Betas never reach
the Homebrew tap, so a Homebrew install updates in place while the setting is on,
and Homebrew takes it back at its next upgrade.
### Linux packages
Each release publishes x86_64 and ARM64 builds as a `.deb`, an `.rpm`, an Arch
Linux package, and a plain tarball, all containing the same executable. They need
glibc 2.39 or newer (Ubuntu 24.04, Debian 13, Fedora 40, current Arch, or later).
The install script picks the package for your architecture and package manager,
checks it against the release's published SHA-256, and installs it with `sudo`:
```sh
curl -fsSL https://sheprd.org/install.sh | sh
```
Read it first at [`site/install.sh`](site/install.sh). To install by hand instead,
download the file for your architecture from
[Releases](https://github.com/sheprd-labs/sheprd/releases), then:
```sh
sudo apt install ./Sheprd-VERSION-x86_64-unknown-linux-gnu.deb # Debian, Ubuntu
sudo dnf install ./Sheprd-VERSION-x86_64-unknown-linux-gnu.rpm # Fedora
sudo pacman -U Sheprd-VERSION-x86_64-unknown-linux-gnu.pkg.tar.zst # Arch Linux
```
The internal package name remains `herdr-gpui`; packages provide the canonical
`sheprd` command and a real `/usr/bin/herdr-gpui` compatibility executable.
The package manager pulls in the runtime libraries, including the Vulkan loader;
a Vulkan driver for your GPU must also be present. On laptops with two GPUs,
install the driver for the GPU your display uses, not only the discrete one.
Without it, Sheprd renders on the discrete GPU, which can go to sleep while the
window is hidden, so the window stays blank for a second or more each time you
return to its workspace. On Arch Linux, install `vulkan-radeon` for AMD or
`vulkan-intel` for Intel. **App Updates** detects which
package manager owns the installed executable, downloads the matching `.deb`,
`.rpm`, or Arch package, verifies its signed release metadata and checksum, then
installs it through APT, DNF, or pacman with a PolicyKit authentication prompt.
The authorized helper verifies and installs a protected root-owned copy.
Choose **Restart** after installation; daemon and terminal sessions stay running.
This requires `pkexec` and your desktop's PolicyKit authentication agent. Older
builds that report “Package-managed installations cannot self-update” need one
manual package upgrade to gain this support. Before a release, CI installs each package on Ubuntu 24.04,
Debian 13 and Fedora 42, and the x86_64 Arch package on Arch Linux, then checks that
the executable finds every library. The ARM64 Arch package targets Arch Linux ARM
and is not install-tested.
On NixOS, or anywhere with Nix, build from source with the repository's flake:
```sh
nix run github:sheprd-labs/sheprd
# or add it to a configuration: inputs.sheprd.url = "github:sheprd-labs/sheprd";
# then environment.systemPackages = [ inputs.sheprd.packages.${system}.default ];
```
The flake builds with the toolchain pinned in `rust-toolchain.toml` on x86_64 and
ARM64 Linux. Like the packages, it never updates itself.
### Windows installers
In PowerShell, on x86_64 or ARM64:
```powershell
irm https://sheprd.org/install.ps1 | iex
```
The script ([`site/install.ps1`](site/install.ps1)) downloads the zip for your
architecture, checks its published SHA-256, installs `sheprd.exe` and
`sheprd-launcher.exe` alongside the legacy `herdr-gpui.exe` and
`herdr-gpui-launcher.exe` entry points under `%LOCALAPPDATA%\Programs\Herdr UI`,
adds that directory to your user `PATH`, and creates a **Sheprd** Start menu shortcut
that opens the launcher. Prefer a regular installer? Each
[release](https://github.com/sheprd-labs/sheprd/releases/latest) also has
`Sheprd-VERSION-x86_64-pc-windows-msvc-setup.exe` and
`Sheprd-VERSION-aarch64-pc-windows-msvc-setup.exe`, which install the same files
to the same place for the current user, without administrator rights, and add
an uninstaller under **Settings > Apps**. Either way, the app updates itself
from **Check for Updates**: it downloads the new installer, checks it against
the release's signed manifest and its Authenticode publisher, runs it silently,
and reopens. See [Windows](#windows) for what works on the platform.
Both add **Open in Sheprd** to folders in File Explorer, and to the empty
space inside one, for your user only. It runs `sheprd open` on the folder
through the launcher, so no console window appears: the running app focuses
the folder's workspace or starts one there, and the app is started first when
it is not running. On Windows 11 the entry is under **Show more options**,
because the compact menu only lists commands of packaged apps. To remove
everything `install.ps1` added, run it with `-Uninstall`:
```powershell
& ([scriptblock]::Create((irm https://sheprd.org/install.ps1))) -Uninstall
```
Uninstalling the regular installer from **Settings > Apps** removes the entry
too.
### From source
Install Rust/rustup and, on macOS, the Xcode command-line tools. The repository
pins Rust 1.96.1 and GPUI 0.3.6 (the `gpui-pre` snapshot crate); the Rust version
is declared in `rust-toolchain.toml` and mirrored in `mise.toml`, so `mise install`
also provisions it.
```sh
git clone https://github.com/sheprd-labs/sheprd.git
cd sheprd
just run
```
`just run` uses the optimized release build;
`just run-debug` is notably slower with a dense terminal on screen.
On macOS both build a local bundle identified as `so.pen.herdr-gpui.dev`, so
it never shares a Dock tile or icon cache with an installed release.
Without `just`: `cargo run --locked --release -p sheprd-gpui --bin sheprd`.
To compile and install the optimized executable on macOS, Linux, or Windows:
```sh
just install
```
This installs `sheprd` (`sheprd.exe` on Windows, with
`sheprd-launcher.exe` beside it to open the app without a console window)
into Cargo's bin directory, normally `~/.cargo/bin` or
`%USERPROFILE%\.cargo\bin`, and replaces an earlier installation. Keep that directory on `PATH`; set `CARGO_INSTALL_ROOT`
to use a different installation root (the executable goes in its `bin` directory).
The build uses the pinned lockfile and default features.
On macOS this installs the standalone executable; use Homebrew above for the
full app bundle. Linux needs the build dependencies below; Windows needs the
Visual Studio C++ build tools and Windows SDK for the MSVC Rust toolchain.
Without `just`: `cargo install --locked --force --path crates/sheprd-gpui --bin sheprd`.
Running `cargo test` or `just ci` on Unix also requires `python3` and `jq` on
PATH: the usage-provider tests exercise each JSON parser explicitly. The Ubuntu
dependency helper below installs both; on macOS, use `brew install python jq`.
### Linux Builds
Application shortcuts use **Ctrl+Shift** on Linux, including Ctrl+Shift+T for a
new tab and Ctrl+Shift+C/V for copy/paste, and Windows uses the same profile.
Customize them from **Sheprd > Keyboard Shortcuts**; see
[keyboard shortcuts](crates/sheprd-gpui/README.md#keyboard-shortcuts).
On Ubuntu 24.04 (x86_64 or ARM64), run `bash scripts/install-linux-deps.sh`
before building. This installs GPUI's X11/Wayland/font development dependencies
and `libasound2-dev` for Rodio/CPAL native audio. CI and release builds use the
same script. Linux binaries require the system ALSA shared library (`libasound2t64`
on Ubuntu 24.04), a configured default audio device, and Vulkan for rendering.
Audio normally routes through the desktop's ALSA plugin configuration; no CLI
audio player is required. Terminal clipboard paste needs `wl-paste` (the
`wl-clipboard` package) on Wayland or `xclip` on X11; the distribution packages
and Nix build include these dependencies. Custom notification sounds are MP3 only. See
[notification sounds](crates/sheprd-gpui/README.md#notification-sounds).
### Windows
Windows is tested natively. On every change, CI checks
formatting, lints every target and feature, and runs workspace tests with default
and all features on `windows-2025` (x86_64) and `windows-11-arm` (ARM64). On the
same two runners it also opens real windows in a desktop session for the native
sidebar, notification, and paint-probe fixtures. On x86_64 it runs the live GUI
test against a pinned, checksummed Herdr `herdr.exe` in an isolated sandbox,
which creates tabs, splits and workspaces with the keyboard, types into a
PowerShell pane and reads its output back, resizes the window, reconnects,
follows a workspace another client pushes, and opens a second window. Herdr
publishes no ARM64 Windows build, and under x64 emulation its panes do not act
on Enter, so the live test is not run on ARM64. A release-mode run then holds the dense
terminal's hover, scroll, and redraw frames to a p95 budget with real Win32 mouse
and wheel messages. The release workflow installs and uninstalls both signed
installers. Hosted runners have no GPU, so CI proves rendering on Direct3D's
software rasterizer; IME composition, the clipboard, and taskbar pinning are
still checked by hand ([Windows QA](docs/windows-qa.md)).
Local connections use the named pipe the Windows daemon binds, and configuration and
state follow its `%APPDATA%` / `%LOCALAPPDATA%` layout. `sheprd COMMAND`
reaches the running app over a named pipe that only
your Windows user can open and that rejects remote clients; see
[the command line](docs/cli.md#windows). A Herdr daemon inside a
WSL distribution can be added as a device from **Add Device…**; see
[WSL distributions](crates/sheprd-gpui/README.md#wsl-distributions). GitHub
sign-ins are saved in Windows Credential Manager and avatars are cached under
`%LOCALAPPDATA%\herdr`; see
[saved sign-ins and the avatar cache](crates/sheprd-gpui/README.md#saved-sign-ins-and-the-avatar-cache).
Saved SSH hosts are unavailable and report that plainly; see
[the GUI README](crates/sheprd-gpui/README.md#windows). Shortcuts use Ctrl, not
the Win key, with the Linux defaults (Ctrl+Shift+T, Ctrl+Shift+P,
Ctrl+Shift+Q); see
[keyboard shortcuts](crates/sheprd-gpui/README.md#keyboard-shortcuts). The
taskbar button shows a badge while agents need you and progress for long
operations, the jump list offers recent workspaces and devices, clicking a
notification brings its pane forward, and both installers register
`herdr-gpui://` links that open a checkout or a device in the running app; see
[Windows shell](crates/sheprd-gpui/README.md#windows-shell).
Windows keep the system title bar, so Snap Layouts, drag-to-snap, and the
window menu are the system's own; the title bar follows the app's light or dark
theme. On Windows 11 a translucent window can blur with acrylic or Mica, and
`accent = "system"` takes the accent from Windows. Narrator and other screen
readers get the terminal's text and the title bar and tab strip controls by
name; [what is not exposed yet](crates/sheprd-gpui/README.md#screen-readers-on-windows)
is listed there.
Each release publishes `Sheprd-VERSION-x86_64-pc-windows-msvc.zip` and
`Sheprd-VERSION-aarch64-pc-windows-msvc.zip` (native ARM64), each containing
`sheprd.exe`, `sheprd-launcher.exe`, the legacy executable entry points, and
their license notices, beside
the matching `-setup.exe` installers. They carry the same checksums, Sigstore
signatures, and build provenance as the other assets. Once Windows signing is
set up, both executables, the installers, and their uninstaller are
Authenticode-signed, and a release publishes only after Windows accepts those
signatures; until then they ship unsigned, are not submitted to winget, and do
not update themselves (see
[`scripts/release/README.md`](scripts/release/README.md#windows-signing)). A
signed copy installed by the installer, winget, or the
[install script](#windows-installers) updates itself in the app: the
installer it downloads must match the release's
Ed25519-signed `windows-manifest.json` and carry a valid signature from Sheprd's
existing publisher, or it never runs (see
[App Updates](docs/updating.md#windows-installers)). The app registers with
Restart Manager, so an update, or a restart with **Restart apps** turned on,
reopens it. **Settings > General > Launch at login** (off by default) opens it
when you sign in; see [launch at login](crates/sheprd-gpui/README.md#launch-at-login).
A crash leaves a minidump and a text report beside the log, never uploaded; see
[crash reports](crates/sheprd-gpui/README.md#crash-reports). A copy run from anywhere else does not update itself; download each
new release manually. `sheprd.exe` is a console program, because it is also the
command line agents and scripts run. Open the app with
`sheprd-launcher.exe` (the Start menu shortcut's target), which starts
`sheprd.exe` without a console window.
## How it connects
```mermaid
flowchart LR
subgraph app["Sheprd (this repo)"]
ui["sheprd
