Assert Local

Assert Local allows you to use the full functionality of Assert's world-class review experience using your local credentials. It does not require installing the Assert GitHub app.

Sign in or create an Assert account

Requirements

• Node.js 20.17+, 22.13+, or 23.5+ (matching the prompt library's requirements)
• GitHub CLI
• An Assert account linked to the same GitHub user as gh

Usage

npx assert-local review

To skip the repository picker, pass a repository or a GitHub pull request URL:

npx assert-local review owner/repo
npx assert-local review https://github.com/owner/repo/pull/123

Repositories open their inbox; pull request URLs open that review directly.

The command confirms the active GitHub and Assert identities, resolves the current repository or lets you search for another one, and opens a loopback web server. The server proxies Assert's production web assets and API without exposing the GitHub or Assert token to browser JavaScript.

While the server is running, it refreshes the repository-scoped inbox every two minutes and asks Assert to prepare necessary review assets.

Use --no-open to print the local URL without opening a browser. While the server is running, press o in its terminal to reopen the page.

Assert Local remembers confirmed GitHub/Assert identity matches and the most recent repository in ~/.assert-local/preferences.json. It never stores GitHub or Assert credentials there. Repository search filters repositories already available to your GitHub account locally; exact lookups and broader public searches each make a single explicit GitHub request.

Development

pnpm install
pnpm typecheck
pnpm lint
pnpm test
pnpm build

src/commands/review.ts owns the interactive setup and terminal lifecycle. src/assert-api.ts owns session exchange, refresh, and authenticated API requests; the proxy and background polling share this client. src/local-server.ts serves the browser and injects runtime configuration, while src/poll.ts runs cancellable, non-overlapping background work. UI assets remain hosted by Assert.

Sessions refresh shortly before expiry or once after a 401. Refresh must preserve the GitHub identity, Assert identity, and workspace selected at startup. Tokens stay in process memory and are never forwarded to the web-asset origin or exposed in the browser's runtime configuration.