> For the complete documentation index, see [llms.txt](https://docs.flxbl.io/flxbl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flxbl.io/flxbl/codev/development/workspace-explorer-web.md).

# Workspace Explorer (Web)

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](/flxbl/codev/development/development.md).

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.

<figure><img src="/files/ak4BqR8pURZHVmcKrP2f" alt="The web Workspace Explorer&#x27;s Component Explorer with a field selected and the Analysis tab listing code analysis findings with severity, rule, and file path"><figcaption><p>Component Explorer — a component selected, with the Analysis tab listing code analysis findings for the branch.</p></figcaption></figure>

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](/flxbl/codev/inspect/change-analysis.md) 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](/flxbl/codev/development/packages.md#versions)), and **Configuration**, a read-only view of the domain's release configuration or the package's project entry.

<figure><img src="/files/NTYrYxblfYWXkq04UKcT" alt="The Module Explorer with the frameworks domain selected and its AI insight report open, showing the report header with commit, age, duration, and model, and the report&#x27;s table of contents"><figcaption><p>Module Explorer — a domain selected, with its AI insight report in the Insight tab.</p></figcaption></figure>

## 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.

<figure><img src="/files/9ddxcGvuYpz71t6r9Jn6" alt="A package insight report showing an overall health score with executive summary, table of contents, and the report metadata chips for commit, age, duration, and model"><figcaption><p>A package insight — health score, executive summary, and section-by-section analysis.</p></figcaption></figure>

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.

{% hint style="info" %}
Insight reports require an AI provider — configure one under **Settings > Integrations > AI Providers**. See [AI Providers](/flxbl/codev/integrations/ai-providers.md).
{% endhint %}

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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.flxbl.io/flxbl/codev/development/workspace-explorer-web.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.