Codebase Stats (project health dashboard)
A multi-tab report on one real project: its size, health, git activity, dependency risk, AI spend and test coverage, gathered from the filesystem, git, npm and Omniscio's own database into a single modal. Covers opening it, the headline numbers, the per-tab detail, ignoring a noisy finding, and spawning a fix-it session from one.
On this page
What it is
Codebase Stats is a multi-tab modal that analyzes a real project and reports on its size, health, git activity, dependency risk, AI spend, and test coverage — everything you'd normally get from a half-dozen CLI tools, gathered and presented in one place. It scans the filesystem, reads git log, checks package.json, runs the coverage tool, and aggregates session costs from Omniscio's own database. Results cache for 24 hours so repeat opens are instant, but you can force-refresh anytime. The modal is per-project and only shows for real codebases — virtual projects (Gmail, SMS, OpenClaw, Skills, etc.) don't have a filesystem to analyze so the menu item is hidden there.
Where to find it
It opens from a project's three-dot menu in the left sidebar, under View Codebase Stats. Because it needs a folder to scan, the menu item is only there for real projects — the built-in virtual rows such as Gmail, SMS or Skills have no filesystem behind them and never show it.
If the project's folder has been moved or deleted, the modal says "This project's folder can't be
found" and shows no numbers, rather than a screen of zeros. Nothing is cached for that run, so the
stats come back as soon as the folder does. The check lives in the stats handler and the analyzer
both (projectFolderExists, ProjectFolderMissingError in
codebase-analyzer.ts).
How it behaves
How to use it
- Open the modal. Click the three-dot menu on any real project in the left sidebar → View Codebase Stats. The modal takes over the screen.
- Skim the Overview. The first tab shows 8 headline numbers: total lines, source vs test lines, commits in last 30 days, AI spend to date, test count, TODO count, dependency count, and known vulnerabilities. If any secrets were detected, a red alert banner appears at the top.
- Drill into tabs. Switch between Files (language breakdown + extension table), Health (TODO/FIXME count,
anytypes, detected secrets, large files over 300 lines), Git (activity, churn hotspots, knowledge silos), Deps (outdated and vulnerable packages by severity), Costs (input/output token usage and total dollars), and Coverage (donut chart + untested file list). If the file scan hit an aggregate cap — too many files, too much cumulative content, or too deep a folder tree — an amber banner at the top of the Overview and Files tabs explains which cap stopped it and that the analysis is partial. - Run coverage manually. The Coverage tab doesn't auto-run — click Run Coverage and Omniscio invokes your test suite with
@vitest/coverage-v8instrumentation (and offers a one-click install if the provider is missing). Progress streams live as it works. - Ignore noisy findings or launch a fix-it session. Click the X on any flagged finding (a large file, a TODO, a detected secret) to hide it from future reports — restore later from the "show ignored" toggle. Or click Fix in Session on a finding (on the Health, Git or Deps tab) to open the Start session dialog for that project, with a pre-written description of the problem as the item's details. Add your own instructions or pick a model if you like, then press Start: the new session opens and the stats window closes. If the session cannot start, the stats window stays open and a message offers Try again. Use Refresh (bottom-left) to bypass the 24h cache.
Related
Running an analysis on a schedule rather than by hand is a job for the step machinery described on the use recipes page. The projects that are exempt from stats because they have no local folder are covered on OpenClaw provider.
- background-codebase-stats-warmer-contract.md — the background warmer's test-locked invariants
- use-recipes.md — if you want to run codebase analysis on a schedule across many projects, wire it into a recipe step
- openclaw-provider.md — OpenClaw projects are exempt from stats (no local filesystem)
Last verified 2026-11-20