repowiseThe 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 and GitLab
connections,
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 → Coding agents (MCP) | Mint API keys and copy the MCP snippet for your editor |
| Team | Members, invitations, shared repos, billing, and the portfolio intelligence pages (health, ownership, engineering signals) |
| Settings | Account, GitHub App, Git hosts (connect GitLab.com), 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, Performance, Tests, 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) |
Two of those tabs are worth a sentence each. Hotspots is not a tab of its own. The churn view folds into the Code Health Overview, where churn is a lens on the same code map and the ranked hotspot table sits below it, so you read churn against the health picture instead of on a separate page. The Performance tab is a queue of causes, not a list of observations: the server folds many caller paths that reach one sink into a single opportunity, because that is one piece of work instead of N warnings.
Flat links (/graph, /c4, /hotspots, /risk, /ownership,
/coverage, /blast-radius, /health) resolve to the tab above that
holds that view, and ?tab=hotspots, ?tab=heatmap, ?tab=modules and
?tab=trend land on Overview.
The chat dock
Every repo page carries a chat dock, not only the Chat nav item. It knows which page you are on: the route and its query are read into a page context that the backend folds into the system prompt, so a question asked from the Files view or a wiki page starts from that file instead of from the repo as a whole. Opening the standalone Chat page hides the dock, since you are already there.
The dock appears for Pro, Teams and Admin accounts. Free accounts get it too while their metered monthly answer allowance lasts, and it disappears once that allowance is spent. Signed-out visitors on a public snapshot do not see it.
Indexing a repo
From Repos → + Index a new repo:
- Pick GitHub or GitLab, then paste a URL or select from the list: the GitHub App's repositories once it is installed, or your projects once a GitLab.com account is connected under Settings → Git hosts.
- 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 (a GitLab project
hook needs the api scope, and polling stands in without one); no
manual update unless you want to force one.
Connecting your editor
Settings → Coding agents (MCP) mints an API key and shows a ready-to-paste MCP snippet for Claude Code, Claude Web/Desktop, Cursor, VS Code, and Windsurf. The snippet uses the HTTP transport and points at the hosted MCP endpoint for the repo you pick.
Keys are revocable any time. See Connecting your IDE for the full walkthrough.
Closing your account
Settings carries a self-serve account deletion. It is a soft delete with a seven-day grace window: the account locks immediately, a nightly sweep does the irreversible part once the window closes, and you can cancel any time before then to get the account back. Deletion has to be requested from a signed-in browser session; an API key cannot close the account it belongs to.
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.