Shepi
Questions

Questions about Shepi.

Short answers; each links to the Guide where there is more. Something missing? Ask us.

Shepi and Herdr

Yes. Shepi is a native Mac app that shares your Herdr terminal sessions: every space, tab and agent you start with herdr is in one Mac window, in real terminals, and what you start in Shepi is in your terminal too, on Apple silicon and Intel. Quitting either stops nothing. Herdr also has its own free desktop app (Apple silicon), but it runs its agents in a separate runtime, herdr-core, so it doesn’t share them with the terminal. Herdr’s app and the other Mac apps for Herdr (herdrm, Herdr UI, Bessie, Moshi Desktop) are on the comparison.

It's the same Herdr, with the same spaces, tabs and keys, built for the places where a terminal makes you work harder: the agent that needs you turns amber and your Mac tells you, agents ask with buttons, changes read as a diff, and one search covers every machine. You can use both at once.

Yes. Shepi attaches to the same Herdr server as herdr in your terminal, so the spaces, tabs and agents you start in one are in the other, live, and they keep running when either one closes. Use both on the same Mac, or the terminal UI over SSH while Shepi stays on your desk.

Not with its sessions. The new Herdr app runs on herdr-core, which keeps sessions of its own, so the terminal UI doesn't see them and neither does Shepi. Shepi works with Herdr's server, the one herdr starts, and everything you run there.

Shepi is a window onto Herdr, so your agents keep running when you quit it, on this Mac and your servers, for $19.99 once. cmux is a terminal whose agents end when you quit it; Conductor and Paradev build each task around a worktree and a pull request. Details and sources on the comparison.

Only when you ask. It reads Herdr's config for your keys and sounds and never changes it; adding or removing a machine goes through Herdr itself.

Yes. Plugins run inside Herdr, so their panes, popups, actions and keys work in Shepi on every machine.

Yes. Shepi tells you at the moments Herdr plays its sound, with Herdr's own sounds and your Herdr sound settings.

No. Shepi is an independent client built on Herdr's public interface, made by WIO, and not affiliated with the Herdr project.

Yes. Shepi follows your Mac's language (English, Japanese or Simplified Chinese), or the one you pick in Shepi's Settings › General › Language. Menus, Settings, cards, messages and notifications are translated; your terminals, agents and commands stay as they are. shepi.app is in all three too.

Agents

Anything that runs in a terminal. Claude Code, Codex, OpenCode, Gemini CLI, Cursor, Copilot CLI and every other agent Herdr recognizes also show their state and their own mark.

Run them in Herdr, which keeps each agent alive in its own terminal, and open Shepi to see them all in one window: the sidebar lists every agent with its state, its space and folder, its branch and machine. More in the Guide: The sidebar.

It turns amber in the sidebar and its pane, and you get a banner, a macOS notification and Herdr's sound. ⌃B a (a for attention) answers its question, or jumps to it, from wherever you are. More in the Guide: When an agent needs you.

Yes. The inbox beside Find keeps every agent that needed you, finished or asked while you weren't looking, until you look at its pane. More in the Guide: When an agent needs you.

Yes. Every agent row shows how long the agent has worked in all; rest the pointer on the time for this turn and its number of turns. Starting a new conversation (/clear, /new) starts the time over; right-click the agent › Reset Time does it by hand.

Yes. An agent keeps its task list in Shepi: the step it's on shows under its name, and resting the pointer on that line, or clicking it, shows the whole list with how long each step took.

Shepi shows the list the agent keeps itself, and the section Shepi adds to each agent's instructions already tells it to keep the list moving: a step in progress when it starts, completed the moment it's done. Nothing to paste. Say "update your plan" to bring it up to date. Claude Code on its newest models keeps no list unless started with CLAUDE_CODE_ENABLE_TODO_TOOLS=1.

Yes. Every agent, on this Mac and your servers, can ask you a question with buttons, show a page or file, report progress, open panes on any side of itself, hand off to a fresh agent and manage your macros. Shepi sets this up by itself for Claude Code, Codex, Gemini CLI, OpenCode, Cursor, Copilot CLI, Amp, Grok Build and Pi. More in the Guide: What agents can do in Shepi.

Yes. Through Shepi's tools (MCP) any agent can find the others, read what one is doing, and tell it something or ask it and wait for the answer, whoever made them: Codex to Claude Code, Claude Code to OpenCode, on this Mac or a server. Shepi also installs Herdr's own skill for every agent. More in the Guide: What agents can do in Shepi.

A little, so each agent knows what it can do in Shepi without being told. Everything is marked as Shepi's, does nothing outside Shepi and never touches your project's files. Some agents ask you once to approve it; updating Shepi doesn't ask again, and removing Shepi leaves nothing behind that shows an error. Turning off "Keep the Shepi plugin installed on my machines" in Settings › Agents removes it all.

Open Shepi's Settings › Agents and click Set up again. Shepi puts back what it adds for your agents on every machine, its tools, its lines in their instructions and Herdr's skill, without touching anything you wrote yourself. It also does this on its own the next time a machine connects.

Yes. Ask it to open the page here: it opens as a pane beside the agent (or on any side you say), with Back, Forward, Reload and Open in Browser; a page served from one of your servers opens the same way.

Yes. When it finishes, Shepi starts a fresh agent of the same kind in its place with the prompt it left, or at a time, or after another agent; it runs on the machine, so it goes on with Shepi closed.

Yes. Ask it for a key that switches your model or restarts your server and it adds the macro; you can edit any of them in Settings › Macros.

Yes, with the permissions you give Shepi, as in Terminal: turn on Screen Recording or Accessibility for Shepi once, and agents in its panes on this Mac have it.

Machines and panes

Yes. Add any machine you reach over SSH; it uses Herdr's own machine setup and your own keys, and its agents keep running while your Mac sleeps. More in the Guide: Agents on other machines.

Yes: copy or screenshot it and press ⌘V in the pane, or drag files onto it. Shepi copies them to that machine and pastes their paths, up to 32 MB at a time.

Yes. ⌘-click the localhost link it prints, and the page opens on your Mac.

Yes. The first button in a pane's header sends it to the background: it leaves the tab and keeps running, and the tray beside Find brings it back.

Open View › Worktrees… (⌥⌘W): every worktree on this Mac and your servers, with what it holds. The ones with nothing to lose are already ticked, so one click removes them; anything with unsaved work waits for you. More in the Guide: Worktrees.

Yes, with a macro: write the steps once in Settings › Macros and give them a key. It can fill in where it runs: the folder, the repo, the branch or an answer you type. More in the Guide: Macros.

Yes. After a quit, a restart or a dropped connection, it opens on the same machine, space, tab and pane, or the nearest one still there.

Buying

One price, $19.99 once, every future update included. Try everything free for 14 days, with no account and no card; when the trial ends Shepi asks you to buy, and your agents keep running in Herdr either way.

Yes. macOS 15 or later, Apple silicon and Intel, notarized by Apple. It needs Herdr 0.9.3 or later, which is free.

Download it and sign in with the account you bought with (Google, GitHub or X). There is no license key.

Shepi works offline. It reaches shepi.app to start the trial, every few days during it, and about once a week after you buy; offline for 30 days in a row, it asks you to connect, with a week's warning.

Privacy and help

No analytics in the app, no automatic crash reports and no Shepi account. To buy, you sign in with Google, GitHub or X, and that sign-in is your license.

SSH to your own machines, the trial and purchase checks with shepi.app, checkout when you buy, a feedback report only when you press Send, and an update check only if you allow it. Everything is listed on the privacy page.

Help › Send Feedback, with a diagnostic log if you leave it on (never terminal contents, names or paths), or write to support@shepi.app. The support page has more.

Nothing matches. Try fewer words, or ask us.