Your AI Reads
Your Architecture
Stop feeding entire files. Start indexing structure. Codebase Mirror is a cognitive implant - it scans your project, extracts the structural graph, and adds a one-line summary of it to dashboard chat context.
In plain words
What it is, where it lives, when to reach for it
- What is it
- A dashboard feature of QuoxCORE that scans a project and builds a compact structure map for agents.
- Where do I use it
- In the dashboard, on the Codebase Mirror page; agents read the map through the reflection system.
- When would I use it
- When agents keep reading whole files to answer questions your project structure already answers.
- How do I use it
- Open Codebase Mirror in the dashboard, enter a project path, and click Scan.
QuoxCORE is the free, self-hosted platform underneath this. What is QuoxCORE
A cognitive implant, not just a tool
Codebase Mirror scans a project and feeds a one-line structural summary into dashboard chat context.
Structure as knowledge, not files as data
Traditional code context dumps entire files into the AI's context window. Codebase Mirror takes a different approach: it pre-computes the structural graph - components, routes, registries, exports, dependency chains - and adds a one-line counts summary (projects, routes, services, drift flag) to dashboard chat context once a project has been scanned.
This is the cognitive implant pattern. The chat sees the shape of the project without reading files. For detail, the index can be queried by element type (routes, services, plugins, registries, schemas). For natural-language code questions use RepoBrain.
- Pre-computed structural counts added to dashboard chat context
- Query API for on-demand detail by element type: scan, index and diff are the mature surface, structured query is early
- Each new scan is diffed against the previous one
- Feeds a one-line summary into dashboard chat context
Without Mirror
AI reads raw files one by one, guessing which ones matter
With Cognitive Implant
A one-line structural summary in dashboard chat context, plus typed queries for detail
Scan. Index. Query.
Three steps from messy codebase to instant structural awareness
Scan
Detects project type by marker file (React, Go, TypeScript, Rust, Python). Extracts registries, routes and services for React, Go, Node and Tauri projects.
Index
Stores structural data in SQLite. Computes diffs against previous scans. Flags drift between scans: added or removed routes, services, registries, schemas and invariant failures.
Query
Query structured elements by type (routes, services, plugins, registries, schemas). For natural-language code questions use RepoBrain.
POST /api/v1/codebase/scan { "path": "quox-website" }
{
"project": { "id": "b9e75d2c4bee847c", "name": "quox-website", "type": "react" },
"metrics": {
"fileCount": 475,
"moduleCount": 48,
"routeCount": 450,
"serviceCount": 5,
"testFileCount": 0,
"registryCount": 1
}
}
invariant checks
FAIL plugin-manifest-sync Missing manifests: mikrotik-routeros
# That failure is the point. A scanner that only ever reports success
# proves nothing - this one caught a real drift the same night it ran.
# Query takes a required type (route, plugin, service, agent, schema,
# registry), not free text. Scan, index and diff are the mature surface;
# query is early.
Structure-first intelligence
Everything your AI needs to understand your codebase without reading it
Auto-Detect Project Types
Identifies React, Go, TypeScript, Rust and Python projects. Detects project type by marker file. Extracts registries, routes and services for React, Go, Node and Tauri projects, and lists declared dependencies.
Drift Alerts
Each new scan is diffed against the last: added or removed routes, services, registries, schemas and invariant failures.
Cognitive Implant
Adds a one-line summary (project, route and service counts, plus a drift flag) to dashboard chat context once a project has been scanned.
CODEBASE_MAP.md Generation
Exports the full structural index as a markdown file. Readable by humans, parseable by any LLM or MCP tool.
Layered by design
Each layer does one job and talks only to its neighbors
Feature Page
This page - explains the cognitive implant concept
Dashboard
Visual index browser, drift alerts, scan history
Context Injector
Adds a one-line counts summary to dashboard chat context
Query API
Query structured elements by type: routes, services, plugins, registries, schemas
Storage (SQLite)
Indexed structure, diff history, project metadata
Scanner Plugin
Detects project type, extracts registries, routes and services
Part of the QuoxCORE platform
What it connects to today
- QuoxCORE dashboard - visual index browser
- Dashboard chat context - one-line structural summary
- HTTP API - scan, query, diff, summary and markdown endpoints
- Claude Code - /context-load can read an exported CODEBASE_MAP.md (workstation skill)
# Codebase Mirror - quox-dashboard Generated: 2026-03-04T14:30:00Z Type: React + Express monorepo ## Components (47) - pages/ (12): LandingPage, StorePage, ... - layouts/ (8): DocsLayout, WebsiteLayout, ... - widgets/ (27): ProductRow, SidebarNav, ... ## Routes (34) / → LandingPage /store → StorePage /solutions/* → [9 promo pages] /docs/* → DocsLayout → [25 pages] ## Registries - pluginRegistry: 14 plugins - entityRegistry: 8 entity types - sidebarConfig: 6 sections ## Exports Named: 156 | Default: 42 | Re-exports: 23
Install the scanner
The Codebase Mirror scanner plugin
Scans run on demand from the dashboard or the HTTP API. Scheduled, CI and remote-host scanning are planned, not shipped.
View Plugin DetailsWhat's built, what isn't yet
- Scan, index and query are real: the collector serves /api/v1/codebase/scan, /:id/query, /:id/diff, /:id/summary and /:id/markdown, backed by scanner, diff and query test suites
- Project-type detection covers five languages by file marker (React, Go, Node, Tauri+Rust, Python); deep registry, route and service extraction is built out for React, Go, Node and Tauri projects
- CODEBASE_MAP.md export is a real endpoint (POST /:id/markdown), not a mock file
- There is no CLI: the real interface today is the collector HTTP API (/api/v1/codebase/scan, /query, /diff) and the dashboard’s Codebase Mirror view
- Query is by element type only (route, plugin, service, agent, schema, registry); there is no natural-language path in Mirror, use RepoBrain for code questions
- "Scheduled scans" (commit hooks, cron, CI) and "Remote fleet scanning via QuoxBastion" describe no code found in the scanner: a scan runs on demand from the dashboard today, not on a schedule or against a remote host
- Python and Rust projects are detected but fall back to generic-scanner depth, so they don’t yet get the registry/route extraction React and Go projects do
Stop reading files. Start querying structure.
One scan. One index. Dashboard chat gets a one-line structural summary, and typed queries answer the rest.
How you get it
Free in the store, not shipped yet
Codebase Mirror costs nothing, and the catalogue carries it as coming soon: the row is there, the build is not out. It is the map the rest of the Dev Suite reads.
On its own
Regenerates a live map of a repository from the actual code: registries, routes, imports and configs, written back as CODEBASE_MAP.md so an agent orients from fact rather than from a stale README.
Ask it questions
The map tells you what exists. RepoBrain is what answers "where is X and what imports it" with cited snippets instead of whole files, at a fraction of the context cost.