Skip to main content

Code view

The Code view turns the raw capture in your Mirror layer into something you can navigate — a file browser backed by analysis, not just a directory tree.

What it shows​

  • File browser — your project's files, scoped to the current workspace.
  • Change history — symbol-level diffs per file (powered by tree-sitter), so you can see exactly which functions changed in which commits. Python, JavaScript and TypeScript are supported.
  • Complexity metrics — cyclomatic complexity and lines-of-code per function (via lizard).
  • Hotspot ranking — files ranked by churn and call-graph impact, surfacing the risky parts of the codebase.

Why it's useful​

Hotspots are where bugs concentrate: high-complexity functions that change often. AgentDesk flags them, and when a function crosses a complexity threshold it can suggest a work item to address it — so refactoring debt becomes visible backlog instead of a surprise.

The same data is available to your AI tools through the MCP server via get_code_symbols (complexity + hotspots) and get_file_history (symbol-level change history) — so an agent can reason about where in the code to focus, not just what the code says.

Next: Models & keys →