Working with repositories

Everything peek can answer about comes from a repository you've added. Here's how adding, tuning, and refreshing them works.

Adding repositories

• From your GitHub App installation. Install the peek GitHub App on a personal or org account and grant it the specific repos you want. These can be private, and they reindex automatically on push (subject to the cadence below).
• Search public repos. Add any public repository by name without installing the App. Because there's no App on these, there's no push webhook — they reindex on demand only.

Indexing status

Each repo reports its state: pending (queued), indexing (being summarized), ready (queryable), or failed (something went wrong — usually access or a transient error; a reindex normally clears it). Only ready repos can be asked questions, in the web chat and over MCP alike. In the sidebar a queued repo shows a pulsing queued… dot the moment a trigger is registered, switching to a spinner once a worker picks it up — so you can see the request landed before indexing actually starts. While it runs, a thin progress bar and a rough ETA (e.g. indexing 45% · ~3m) track how far along it is.

Excluding paths

peek skips obvious noise by default — node_modules, .git, dist, build. You can edit the exclude globs (one glob per line) when adding a repo or later in its settings. Excluding generated code, vendored dependencies, and large fixtures keeps the atlas sharp and your indexing spend down.

Keeping it fresh

For App-connected repos, choose how often a push may trigger a reindex — Manual only, or no more often than every 5 min, 1 hr, 6 hr, or 24 hr. It's a debounce, not a schedule: a busy branch won't reindex on every commit, only once per window. Public repos are always manual. Either way, the Reindex now button in a repo's settings forces a fresh pass on demand.