repowiseDashboard 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
| Section | What you do here |
|---|---|
| Repos | Index a new repo, watch indexing progress live, browse the wiki, jump into chat |
| Workspaces | Group repos into a workspace, view cross-repo co-changes, contracts, and the security rollup |
| Chat | Natural-language Q&A over any repo or workspace — the same RAG that powers get_answer |
| Costs | LLM spend per repo, per day, per model — plus what Repowise saved your agents in tokens |
| 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, not just a wiki:
| Page | What it shows |
|---|---|
| Overview | KPIs, activity, languages, health ring, recent significant commits |
| Wiki & Docs | The LLM-authored wiki with citations and freshness, plus the docs explorer |
| Graph / C4 / Modules / Symbols | Dependency graph (5 view modes), C4 architecture levels, module and symbol explorers |
| Hotspots / Ownership / Dead code | Churn-ranked hotspots, per-file owners and bus factor, tiered dead-code findings |
| Health | The 1–10 per-file score, biomarker findings, trend over time, coverage, refactoring targets |
| Commits & Change risk | Commit history with categories, per-change defect-risk scoring, blast radius |
| Decisions | Recorded architectural decisions linked to the files they govern, with staleness tracking |
| Security | Vulnerabilities with usage/reachability triage, secrets, SBOM/VEX export, scan status |
| Repo settings | Re-sync, visibility, alert webhooks, danger zone |
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.