Dashboard tour
What lives behind sign-in at repowise.dev/dashboard — the hosted control plane for your indexed repos, workspaces, MCP keys, billing, and team.
The hosted dashboard at repowise.dev/dashboard
is the control plane for everything you can do with the hosted version
of repowise. The same intelligence layers that repowise serve exposes
locally are here, plus the bits that only make sense for a managed
service: indexing status, MCP key minting, GitHub App management,
billing, and team membership.
What's on it
The landing page at repowise.dev/dashboard lists your indexed repos with
live indexing status, recent jobs, and a workspace summary card if you've
grouped repos into a workspace. A Cmd/Ctrl+K command palette jumps straight
to any repo or page from anywhere.
| Section | What you do here |
|---|---|
| Dashboard (repo list) | Index a new repo, watch indexing progress live, jump into any repo |
| Workspace | Overview, System Map, Conformance, Contracts, and Co-Changes across every repo in the workspace |
| Settings → Editor | Mint API keys and copy the MCP snippet for your editor |
| Settings → Team | Members, invitations, shared repos, billing, and the portfolio intelligence pages (health, ownership, engineering signals) |
| Settings | Account, GitHub App, email notification preferences, billing |
Inside a repo
Every indexed repo gets a full analysis surface under a grouped nav, not just a wiki:
| Group | Pages |
|---|---|
| (top) | Overview (KPIs, activity, languages, health ring, recent significant commits) · Docs (the LLM-authored wiki with citations and freshness) · Architecture (tabs: Communities, Explore, Coupling, Dependencies, Symbols) · Knowledge Graph (node search, path finder, community detail) · Code Health (tabs: Overview, Findings, Hotspots, Coverage, Dead code, Impact, Security) · Refactoring (ranked plans, blast radius, copy-to-agent) · Files (every indexed file, ranked by importance, browsable by folder) |
| People & History | Commits (history with categories, per-change change risk) · Contributors (ownership, bus factor) · Decisions (linked to the files they govern, with staleness tracking) |
| (chat) | Chat — natural-language Q&A over the repo, the same RAG that powers get_answer |
| Settings | Stats · Usage & savings (LLM spend and what Repowise saved your agents in tokens) · Settings (re-sync, visibility, alert webhooks, danger zone) |
Older flat links (/graph, /c4, /hotspots, /risk, /ownership,
/coverage, /blast-radius, /health) still resolve — they redirect into
the tab above that now owns that view.
Indexing a repo
From Repos → + Index a new repo:
- Pick a GitHub URL (or select from the list once the GitHub App is installed).
- Choose the LLM provider (Repowise-managed by default — your account's pooled key — or BYOK).
- Submit. Indexing runs on managed infrastructure; you'll get an email when it's done.
The repo card shows status (indexing, ready, stale, error)
and a re-sync button. Pushes auto-sync via webhook — no manual update
unless you want to force one.
Connecting your editor
Settings → Editor mints an API key and shows a ready-to-paste MCP snippet for Claude Code, Cursor, Claude Desktop, VS Code, and Windsurf. The snippet uses the HTTP transport and points at the hosted MCP endpoint.
Keys are scoped per repo or per workspace and revocable any time. See Connecting your IDE for the full walkthrough.
What's not on the dashboard
- The five intelligence layers themselves — they live in the wiki and the MCP tools, not as separate dashboard pages.
- The CLI — the dashboard wraps the same server as
repowise serve, but you don't run shell commands here.
Self-hosted? repowise serve gives you most of the same screens
locally at http://localhost:3000. The bits that only exist on the
hosted dashboard are the ones that wrap a managed service — billing,
team management, the GitHub App installer.
Hosted vs self-hosted
Both modes ship the same intelligence layers, the same nine MCP tools, and the same dashboard. The differences are about ops, billing, and team features — not about what the agent can do.
PR review bot
A deterministic GitHub App that posts one useful comment per pull request — code-health deltas, hotspots, hidden coupling, dead code, change risk, and an optional merge gate. Zero LLM calls, free for OSS.