Workspace Explorer (Web)

Browse your repository in the web app — components and modules at any branch, code analysis findings, and AI-generated insight reports per package or domain.

The web app's Workspace Explorer browses your repository — no local workspace involved. Pick a branch, explore what the project contains, read code analysis findings, and generate AI insight reports for a package or a whole domain. Everything here is read-only: editing source, retrieving from orgs, and creating domains happen in the desktop workspace.

The page has two explorers, switched at the top of the tree, and a set of tabs on the right that follow what you select.

Component Explorer

The Component Explorer shows the branch's source as a tree — package, metadata category, type, component — with the same filters as the rest of the page (domain, package, type, modified). Selecting a component opens it read-only in the Code tab.

Component Explorer — a component selected, with the Analysis tab listing code analysis findings for the branch.

The Analysis tab lists the branch's code analysis findings — rule, severity, message, and file — with the totals summarised at the top. Analysis is collected automatically for the branch (and refreshed daily), so the findings are ready when you open the tab; see Change Analysis for the analyzer itself.

Module Explorer

The Module Explorer shows the same repository as domains and packages: each domain with its pool and packages, plus an Unassigned Packages group. Selecting a domain or a package drives the tabs on the right — Insight, Versions (packages only, the same list as Packages → Versions), and Configuration, a read-only view of the domain's release configuration or the package's project entry.

Module Explorer — a domain selected, with its AI insight report in the Insight tab.

AI insight reports

The Insight tab holds an AI-generated analysis of the selected package or domain: an executive summary and health assessment, followed by sections on overview, architecture, dependencies and relationships, and quality. The report is grounded in the repository — the analysis reads the actual source and git history of the scope it covers.

A package insight — health score, executive summary, and section-by-section analysis.

Reports are generated only when you ask: click Generate Insight (or Regenerate on an existing report) and the analysis runs in the background — a few minutes for a package, longer for a domain. Each report carries the commit it analysed, when it ran, how long it took, and the model that produced it. Requesting a report when one already exists for the current commit does nothing — codev tells you the report is up to date, and one analysis runs per scope at a time.

Insight reports require an AI provider — configure one under Settings > Integrations > AI Providers. See AI Providers.

Insight reports analyse the project's main branch regardless of the branch selected in the explorer — the branch selector scopes the trees, the code, and the analysis findings, not the AI reports.