The SeeRepo CLI

The SeeRepo CLI shows your project's map in the terminal: a module as a tree with what each part does, what changed since yesterday, and a module opened in the browser. Useful for you, and for an agent that can run commands. It reads through the API with your key. With a key you let write, it also makes three changes, and asks before each one.

It needs Node.js 18 or later.

1. Run it

Run it without installing it:

npx seerepo login

Or install it, if you'll use it often:

npm install -g seerepo

2. Log in

seerepo login

It asks for an API key: create one in Settings → API / MCP and paste it. The CLI says which account it's connected to and saves the key in ~/.config/seerepo/config.json, readable only by you.

3. Use it in your project's folder

The CLI knows the repo from the folder's git remote on GitHub. Outside the folder, add --repo owner/name.

If SeeRepo also follows the branch your folder is on, the CLI reads that branch's map. Add --branch name to pick a branch yourself.

See a module

seerepo map
seerepo map /checkout

ana/tienda
A shop.

├─ ☺ Shoppers
├─ ◆ Checkout — Takes the payment and confirms the order.  → /checkout
├─ ◆ Catalog — Lists the products.  → /catalog
└─ ▤ Data — Orders and products.  → /data

Outside services: Stripe

Go inside: seerepo map /checkout

Each module (◆) has its path: seerepo map with that path goes inside.

See what changed

seerepo changes
seerepo changes --since 2026-10-19

The last 24 hours by default: when, which agent or person, what changed in plain words and the modules it touched.

Open a module in the browser

seerepo open /checkout

Commands

Command	What it does
seerepo login	Saves your API key
seerepo map [path]	A module as a tree; / by default
seerepo changes [--since date]	The commits since a date; the last 24 hours by default
seerepo impact <file> [--name x] [--to file]	What depends on a file: who names it, how many, which pages and processes
seerepo pages	How many screens and how many are ready, as the app says it, and every page: who gets in (or «door not seen» where SeeRepo can't read it; Python has no Pages yet), the states it handles or misses and, when it only takes you somewhere else, where and the line that does it
seerepo found	How many public pages can be found, as Visibilidad's ring, and how search engines and AI see each one, and what needs work
seerepo health [n]	The score, whether it can ship and the tasks numbered; with a number, that task's prompt (seerepo health 1 | pbcopy). On a free repo, how many are open and the title of the first
seerepo history	The last 7 days, the pace and the moments
seerepo docs [page]	The repo's wiki: its tree, or a chapter with recorded version, document date, language, authorship, full markdown, diagram and sources
seerepo open [path]	Opens that module in SeeRepo
seerepo ignore <path…>	Leaves paths out of the map, as Settings → Ignore does
seerepo false <task> --why "…"	Marks a Salud task false; --files a,b for only some of its files
seerepo snooze <task> --days 7	Puts a task off, 1 to 90 days
seerepo accept <task> --why "…"	Accepts a task as it is
seerepo claim [--days 90]	The commits Codex and Claude Code made in this repo without signing, found in their sessions on this computer. It shows them by agent and, with your yes, claims them for each one; a session never leaves the computer, only each commit and its agent
--repo owner/name	The repo, when you're not in its folder
--branch name	One of the branches SeeRepo follows in that repo; by default, the folder's if SeeRepo follows it, or the main one
--version, --help	Its version, and the list of commands

The five changes (with claim) need a key you let write (in Settings → API / MCP). <task> is its number in seerepo health, or its key. Each one says what will happen and asks Apply? (y/N): without a terminal to answer in, nothing is applied.

When something goes wrong

• "This folder isn't a GitHub repo": run it in your project's folder, or add --repo owner/name.
• "… isn't connected to SeeRepo": connect the repo in your dashboard, then run it again.
• "… doesn't follow the branch …": SeeRepo reads only the branches you added in the project's settings; the message lists them.
• "Your key doesn't work": it was revoked or mistyped. Run seerepo login with a new one.