repo-sensei

Changelog

What changed in repo-sensei, newest first.

  1. Benchmarks, speed and safety

    • CrossLayerBench: 101 hand-labelled flows over five full-stack repositories, and how the tracer does on them, published.
    • Insights say how fast the app's pages were for your team, against their budgets.
    • Answers never load images, and every agent treats a repository's text as data.
    • The privacy page now names every provider that handles data, page-speed measurements and backups; the terms add limits and liability; privacy and security have their own addresses.
  2. The public site, Explore and settings

    • A landing page with a live demo, product pages, docs, pricing, and the security, privacy and terms pages.
    • Explore: open-source repositories, indexed and public, to read and ask about without an account.
    • Organization settings for usage against caps, the audit log, integrations, and deleting or restoring an organization.
    • Appearance (accent, contrast, density, motion and transparency) and a keyboard shortcuts page.
  3. Changes, notifications and limits

    • Ask for a change in plain words: it is planned by layer, approved, patched with new tests and verified.
    • An inbox and notifications by email and Slack for runs, approvals and indexing.
    • Public imports for anyone, with size and daily limits and a spending cap.
  4. Fixes

    • From a stack trace, a GitHub issue or a Sentry error: investigated, reproduced by a failing test, planned, approved by people with write access, patched and verified in a sandbox.
    • Patches that game the tests (editing or skipping them, faking reports) are refused.
  5. MCP, the command line and API keys

    • An MCP server for Claude Code, VS Code, Cursor and other clients, signed in with OAuth or an API key.
    • The sensei command line: sign in, connect, search, ask and trace.
    • API keys with scopes, per organization.
  6. Diagrams and the graph

    • Diagrams drawn from the code's graph, each edge checked, with the share verified on them.
    • A graph explorer, dependencies by level, cycles and what breaks them, packages, and a map of the whole codebase.
    • Impact: what a change to a symbol reaches, before you make it.
  7. Staying fresh

    • Each push is indexed again, only what changed.
    • Tracked branches and pull requests, with a branch picker.
    • Answers, traces and diagrams say when the code they cite has changed since.
  8. Ask

    • Questions about the code, each claim citing its lines and checked against them.
    • Answers that say when the code doesn't tell; scope chips and @ mentions; sharing; history; ⌘L from anywhere.
  9. Trace across layers

    • The code's graph, with frontend calls matched to the routes that serve them.
    • Trace a feature from the page to the database, with its gaps and why.
  10. Search

    • Exact, keyword and meaning search, symbols and go to definition.
  11. Repositories and indexing

    • Connect repositories through the GitHub App or by URL, and watch them index stage by stage.
    • A code browser for repositories of any size.
  12. Foundations

    • Sign in with GitHub, organizations, invitations and roles.