Choose theme
AI Resources
RepoWise
RepoWise is a self-hosted code-intelligence layer that indexes repository structure, git history, tests, architectural decisions, documentation, and code-health signals for developers and AI coding agents.
One local index powers MCP tools, a web dashboard, command-line analysis, editor integrations, pull-request checks, and cross-repository maps. Its core graph and analysis features are deterministic; model-written prose is optional. Use this as a first read, not a recommendation. Open the original project before trusting details like terms, limits, privacy, cost, setup, or safety.
What it is
Several code signals in one index
RepoWise connects file and symbol graphs with git hotspots, test reachability, change risk, code-health findings, generated documentation, and recorded architectural decisions instead of exposing each as a separate scanner.
Why it stands out
Built around change decisions
Its tools answer practical questions such as what may break, which tests exercise a change, which companion files are missing, where health problems concentrate, and why a part of the code was designed that way.
Availability
Python package and self-hosted service
The project installs from PyPI for Python 3.11 or newer and can run as a command-line tool, MCP server, and local dashboard. The repository declares AGPL-3.0-or-later or commercial licensing.
Why it matters
What makes it useful
Understanding a repository is only part of changing it safely. RepoWise brings the code map together with test impact, change history, architectural decisions, and concrete health findings, so a developer or coding agent can move from “where is this?” to “what else should change or be checked?” without assembling several disconnected tools.
What to know
Where it fits
Start by indexing a repository with repowise init --yes --no-prose. Initialization can also configure agent integrations; add --no-editor-setup to defer the quickstart's documented editor setup. Its walkthrough then covers health findings, unreferenced code, and recent-change risk. Model-written subsystem pages can be added later; the structural index does not require a provider key.
Notable points
What stands out
The project's file-retrieval benchmark measures whether it finds the right files, not whether an agent writes better code. Those project-produced results answer a code-lookup question rather than establishing coding-task success.
Before using
What to review
The package describes itself as Alpha software. Try it on a non-critical repository first and review current releases and open issues before relying on it in a production workflow.
Choose the repository scope carefully: the index can read source, git history, tests, decisions, agent transcripts, and workspace relationships depending on the features you enable.
Review generated agent instructions, hooks, editor setup, pull-request automation, and any optional model-provider configuration before enabling them.
Keep the local dashboard and MCP server bound to an appropriate interface, and treat indexed private-code context as sensitive project data.
Reader fit
Who may find it relevant
Developers who want code maps, change risk, test impact, and health findings in one local workflow.
Teams tracing contracts and blast radius across connected repositories.
Builders who want the same cited repository context available to Codex, Claude Code, Cursor, VS Code, or another MCP host.
Less relevant for small one-off repositories or anyone looking for a hosted coding agent rather than an intelligence layer around one.
Editorial note
Why LifeHubber lists it
When Distill shortens a test log or diff, look for its omission marker. Use repowise expand <ref> to retrieve the stored original instead of rerunning the command just to recover the missing detail. The documented omission store is pruned with default limits of seven days and 50 MB, so keep any output you need as a lasting record separately.
Source links
Source materials
Reader note
Before relying on this entry
LifeHubber lists entries to help readers inspect AI projects, not to endorse them or prove they are safe, suitable, accurate, maintained, or right for a specific use. We do not verify every entry in depth. Before relying on anything listed, review the original materials, terms, privacy practices, limits, and risks that matter for your situation.
What to explore next
Choose how much repository intelligence you need.
RepoWise combines code maps with change risk, tests, health findings, documentation, and decisions. These next paths narrow the comparison to a focused persistent graph or a visual code-and-knowledge workspace.
More in AI Agents
Keep browsing this category
Explore more AI agent projects.
Paperclip
paperclipai/paperclip
A self-hosted server and dashboard for coordinating agent teams through companies, goals, roles, issues, heartbeats, budgets, approvals, and persistent activity records.
OpenDots
CopilotKit/OpenDots
An early CopilotKit template for a persistent specialist-agent workspace with editable pages, per-Dot computers, and separately configured conversation, voice, and Slack services.
CopilotKit Channels SDK
CopilotKit/channels-sdk
A TypeScript SDK for bringing AG-UI-compatible agents into Slack, Microsoft Teams, Discord, Telegram, and WhatsApp, with streaming replies, native interactive components, files, tools, and approval steps inside channel conversations.
For project maintainers
Listed here? You can use the badge.
If you maintain a project with a current LifeHubber listing, you may add the optional “Listed on LifeHubber AI Resources” badge to its README, docs, or website. No introduction or permission request is needed.
