Review code changes with your coding agent.
Your agent plans a top-to-bottom walkthrough of all changes, then publishes self-contained groups with short titles and concise notes attached to hunks. Each group contains one or more hunks, all shown for review. You mark hunks Viewed as you read them. Viewed means read, not approved—it does not stage, commit, or modify your code.
Requires Node.js 24 or later on Linux or macOS.
npm install -g @gyst/cli-
Install the skills for your coding agent:
gyst skills
-
Open your agent in the repository you want to review and ask:
/gyst uncommitted changesYou can also specify a range (
/gyst main...HEAD) or a PR (/gyst PR 42). The agent plans coverage and order first, then publishes complete groups progressively into the session.
This version ships the headless session CLI, background daemon, agent skills and a browser viewer that shows each saved session's captured diff. The terminal review viewer has been removed; the browser viewer does not show agent guidance yet.
gyst # uncommitted changes, including untracked files
gyst main...feature # a Git range
gyst --session <id> # a saved sessiongyst opens the saved session for that scope (creating it only if there is none), starts a
private viewer on this machine and opens it in your browser. When it cannot open a browser, it
prints a private link instead; open that link yourself. It stays in the foreground: stop it
with Ctrl-C when you are done. Closing the browser or stopping gyst keeps every saved session.
The link is for you only. Do not paste it into an agent chat or share it. Its secret part
expires 10 minutes after launch; once opened, that browser stays signed in (reloads, new tabs)
until gyst stops. If the viewer says this browser is not signed in, run gyst again and open the
new link. The viewer's home page lists saved sessions; deleting one there asks for confirmation
and removes only that session.
The viewer runs on a new *.localhost host name for each launch and has been tested with
Chromium on Linux, directly and through a local-port SSH forward to the same machine; other
browsers, platforms and a separate remote machine are untested.
Run gyst on the remote machine and forward its port from your computer:
ssh -N -o ExitOnForwardFailure=yes -L 127.0.0.1:LOCAL:127.0.0.1:REMOTE user@remoteREMOTE is the port in the printed link and LOCAL is any free port on your computer. Open
the printed link in your local browser with its port replaced by LOCAL, keeping the host name
and the rest of the link unchanged. The viewer only listens on the remote machine's loopback
address; there is no LAN or reverse-proxy mode.
Agents open a session with gyst session open for uncommitted changes (including
untracked files) or gyst session open <range> for a Git range such as main...feature.
It prints the session id and snapshot identity as JSON without launching anything.
Every other session command names that exact session with --session <id>.
Snapshots stay fixed when files change. Refresh explicitly with
gyst session refresh --session <id>. gyst session check --session <id> reports
unchanged, changed, or unavailable without modifying review progress. Checks are
periodic and cached, not a real-time guarantee.
A snapshot keeps the exact text of every eligible project file, unchanged ones included, so
reviews keep working after the checkout changes or is removed. gyst session files --session <id> --snapshot <snapshot> lists the snapshot's files a page at a time, with each side's
availability (absent, or unavailable as binary, non-UTF-8, a symlink or a submodule). gyst session code --session <id> --snapshot <snapshot> --file <path> --side old|new returns up to
64 KiB of that side's exact text per page, from --start-line (optionally to --end-line) or
from the previous page's next.offset via --offset; a line longer than a page continues on
the next one. Reads never consult the checkout and name the session's current snapshot, from
open, status or diff; after a refresh an older one fails with stale_revision. On a
terminal, capturing (gyst, open, refresh) shows its progress on stderr.
Use /gyst-refresh in your agent's chat to refresh the existing review and revise
its affected groups and explanations while preserving unrelated review progress.
Refresh retains notes only for wholly surviving groups, and Viewed only for exactly
matching hunks; losing any member clears that group's notes without changing
unrelated groups.
Installing a new CLI does not itself restart the background daemon. On the next command, gyst checks compatibility before sending review operations. It automatically restarts an older daemon that supports the handshake only when all saved sessions are readable by the new version and no command is in flight. Saved review state is preserved; older clients cannot downgrade a newer daemon.
Incompatible saved sessions or a legacy daemon without a handshake block automatic recovery with an explicit error. Keep using the old version, or inspect your saved reviews before manually restarting and recreating incompatible sessions. Gyst never kills an unverified PID, migrates a session, or deletes its file during recovery.
Each repository and recorded scope has its own saved session, and different scopes coexist. Reopening a scope returns its saved session as it is, even after the refs it names move; only an explicit refresh recaptures it. Sessions are kept until you delete one:
gyst session list
gyst session delete --session <id> --request-id <request-id>Choose the request id once for that deletion. If the reply is lost, retry with the same request id and session to get the recorded result; a request id already used for another session is rejected.
For CLI options, run gyst --help or gyst session --help.