Shepherd Capture (browser extension)
Shepherd Capture is a Chromium (Chrome, Edge, Brave, …) browser extension that turns the tab you’re looking at into a Shepherd task or a live session — with a screenshot and page context attached — in one click.
Install from the Chrome Web Store
Section titled “Install from the Chrome Web Store”Published and ready to use:
Shepherd Capture on the Chrome Web Store → Add to Chrome.
The store install works with your server out of the box — the published
extension ID is allowlisted by default, so there is no pairing step and no
SHEPHERD_ALLOWED_HOSTS configuration required. Just point the extension at
your Shepherd core (below) and capture.
Point it at your core
Section titled “Point it at your core”Open the extension’s options (right-click the toolbar icon → Options) and set:
-
Base URL — your Shepherd core:
- Local:
http://localhost:7330. - Remote (Tailscale):
https://<host>.ts.net— saving ats.netURL prompts the browser to grant access to that host; accept it once and captures file against your remote core.
- Local:
-
Token — a bearer credential for the core. Mint one in the HUD under Settings → Access: give it a name (e.g. “Capture extension — work laptop”), choose the Submit scope, copy the value while it is shown (it is shown once), and paste it here. You can revoke that one token later without disturbing any other client. If your deployment provisions
SHEPHERD_TOKENin the server’s environment, that value works here too.Submit is the scope this extension needs — it covers filing an issue, starting a session and attaching a screenshot, and nothing more. The narrower Read scope cannot file captures, and Full would hand the extension the live agent terminal it never uses.
-
Repo path — the default target repo (must resolve inside the server’s
SHEPHERD_REPO_ROOT). -
Base branch and Model — optional.
-
Routing rules — optional URL→repo rules so a capture lands in the right repo automatically.
What a capture includes
Section titled “What a capture includes”- A screenshot (visible area or full page).
- Page metadata (title, URL).
- Optional signals: an accessibility (axe-core) audit, console errors, and failed network requests.
You choose whether a capture spawns a live session now or is filed as an issue (GitHub / Gitea) via the task API.
Open the popup
Section titled “Open the popup”Click the toolbar icon, or press Alt+Shift+S (rebindable at
chrome://extensions/shortcuts).
For developers
Section titled “For developers”To run an unpacked development build instead of the store version, see the
extension’s README.
The server’s origin allowlist and the SHEPHERD_ALLOWED_HOSTS knob are documented
under Configuration.