Repository Workspace
The repository workspace at /repositories/:repositoryId is where users resume work after a repository is created. It brings together the repository header, breadcrumb, status, lifecycle tabs, recent activity, insights, processes, documentation, and graph.
When to use
- Use the workspace to understand the current state of a repository.
- Use it to move between indexing, insights, source code, processes, documentation, and graph.
- Use the overview when you are unsure what the next step should be.
- Use locked tabs as guidance for what still needs to be completed.
Before you start
- Confirm the active organization.
- Open the correct repository from
/repositories. - Check whether source code and pre-analysis are already available.
Workspace tabs
| Tab | What it is for |
|---|---|
| Overview | Summarizes the repository status, the getting-started checklist, and the recommended next step. |
| Indexing | Connects a Git repository or uploads a ZIP, and reindexes when the code changes. |
| Insights | Language breakdown, file statistics, detected stack, and cost estimates for the indexed source. |
| Source Code | Browses the indexed source files. |
| Processes | Lists, creates, and manages processes (documentation and backlog outputs). |
| Documentation | Opens generated Markdown documentation. |
| Graph | Explores relationships found in the analyzed code. |
| Settings | Manages repository integrations, including Git CI. |
Insights and Source Code unlock once analysis completes. Documentation unlocks after a process produces output, and Graph unlocks once an active source version exists.
Cost Explorer is not a repository workspace tab. It is available from the Administration area, where you select the repository inside the screen.
Repository overview
Open the workspace root (/repositories/:repositoryId) to review:
- General repository information and the active organization.
- Creation and update dates, and storage type.
- Current status and the repository journey.
- The getting-started checklist showing what is done, current, or pending.
- Recommended next action.
- Recent processes.
- Pre-analysis data, LLM cost estimates, and model recommendations when available.
- Error messages when a failure exists.
The overview is the best screen for resuming work because it consolidates the current state and points to the recommended next action.
Repository status sequence
| Status | What it means | Next step |
|---|---|---|
CREATED | Repository was created. | Open Indexing and connect or upload source code. |
UPLOADED | Source code was provided. | Wait for processing or review pre-analysis. |
PROCESSING | Source code is being processed. | Wait for completion. |
PRE_ANALYZED | Pre-analysis is available, but not confirmed yet. | Open Indexing, review the pre-analysis in the confirmation dialog, and confirm it. |
READY | Repository is ready for new work. | Create processes, read documentation, or explore the graph. |
ERROR | Creation, validation, or processing failed. | Review the Indexing step or retry with a corrected source. |
FAIL | A later repository step failed. | Review the status, provide a corrected source, or retry the affected flow. |
Expected result
The workspace should make the repository status clear, show which areas are available, and guide the user to the next action without requiring manual route discovery.