> ## Documentation Index
> Fetch the complete documentation index at: https://docs.overcut.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Context Map

> Visualize and manage repository correlations across your workspace using the interactive Context Map.

The Context Map is an interactive visual graph that shows every repository in your workspace and how they relate to each other. Use it to explore correlations between code repositories and ticket projects, create or remove links, and edit repository properties, all without leaving the map.

## Accessing the Context Map

Navigate to **Context Map** in the workspace sidebar (under **Configuration**). The Context Map is a **workspace-level** view: it shows every repository connected to the workspace, regardless of project boundaries.

<Note>
  The Context Map is distinct from the **Project Map**. Project Map (`Project → Project Map`) is a project-scoped orchestration view that shows the workflows, agents, and resources inside a single project. Context Map shows the cross-workspace repository graph. See [Multi-Project Workspaces](/docs/concepts/multi-project-workspaces) for the workspace-vs-project boundary.
</Note>

## Reading the Visualization

The map uses a two-column layout powered by a graph canvas:

* **Left column**: code repositories (marked with a green **Code** tag)
* **Right column**: ticket projects (marked with a blue **Tickets** tag)
* **Edges**: directed arrows from code repositories to their correlated ticket projects

Repositories are grouped by organization, with the provider logo (GitHub, GitLab, Bitbucket, Azure DevOps, Jira) displayed on each group header. If a repository is configured for both code and tickets, it appears in both columns with a mirror node.

### Node Details

Each repository node shows:

* Repository name and provider logo
* Role tags (**Code**, **Tickets**, or both)
* Feature indicators for enabled capabilities such as Repo Hints, Cache, Code Indexing, and Custom Instructions
* Active or inactive state (inactive nodes appear dimmed)

### Special Edges

* **Self-correlation**: repositories marked for both code and tickets display a dashed edge that cannot be deleted.
* **Implicit Azure DevOps correlations**: repositories under the same Azure DevOps project are linked automatically.

### Canvas Controls

Use standard canvas interactions to navigate the map:

* **Pan**: click and drag the background
* **Zoom**: scroll wheel or pinch gesture
* **Fit to view**: use the controls overlay to reset the viewport
* **Minimap**: a small overview in the corner shows your current position in the graph

***

## Filters and Focus Tools

When your workspace contains many repositories the filter bar and focus tools help you narrow the view.

### Filter Bar

The top bar provides two filter types:

| Filter            | Description                                                                          |
| ----------------- | ------------------------------------------------------------------------------------ |
| **Organization**  | Show only repositories belonging to selected organizations. Multi-select supported.  |
| **Feature flags** | Filter by enabled features: Repo Hints, Cache, Cache Dependencies, or Code Indexing. |

When filters are active the map shows only matching repositories and their edges. Clear filters to return to the full view.

### Highlight and Pin

Hover over a repository node to reveal two focus controls:

* **Highlight**: click to highlight the selected node and all directly connected nodes and edges. Unrelated nodes dim to reduce visual noise.
* **Hide unrelated**: after highlighting, toggle this option to hide all unconnected nodes entirely, isolating the subgraph you care about.

Click the background or clear the selection to restore the full map.

<Tip>
  For large graphs, combine an organization filter with highlight to quickly isolate the repositories that matter for a specific team or project.
</Tip>

***

## Creating and Deleting Correlations

You can manage correlations directly on the canvas without opening repository settings.

### Create a Correlation

1. Hover over a code repository node to reveal the connection handle.
2. Drag from the handle to a ticket project node.
3. Release to create the correlation.

The system validates that the source is a code repository and the target is a ticket project. Invalid connections are rejected.

### Delete a Correlation

1. Click an edge to select it.
2. Confirm the deletion in the dialog that appears.

<Warning>
  Implicit correlations (self-correlations and Azure DevOps project-based links) cannot be deleted from the map. Adjust the underlying repository configuration instead.
</Warning>

***

## Properties Panel

Click any repository node to open the **Properties Panel** on the right side of the screen. The panel displays the full repository configuration form, letting you review and edit fields without navigating away from the map.

### What You Can Edit

The properties panel exposes the same fields available in repository settings:

* Repository purpose (**Use for Code**, **Use for Tickets**)
* Related Ticket Projects and Related Code Repositories
* Identification hints
* Cache and indexing configuration
* Custom instructions

### Saving Changes

Edits save when you click **Save** inside the panel. The map refreshes automatically to reflect updated correlations, purposes, or feature flags. Close the panel by clicking the background or the close button.

***

## Best Practices

* **Start with correlations**: set up explicit links between your most important code repos and ticket projects before relying on AI-powered identification.
* **Use filters for large workspaces**: narrow by organization first, then highlight specific nodes to trace relationships.
* **Audit regularly**: open the Context Map periodically to verify that correlations still reflect your team structure and project boundaries.
* **Combine with Repository Mapping**: correlations created on the Context Map feed directly into the [repo.identify](/docs/workflows/repo-identify) step for automatic repository selection in workflows.

## See Also

* [Repository Mapping](/docs/repositories/repository-mapping): configure correlations and use AI-powered repository identification
* [Repository Selector](/docs/repositories/repository-selector): filter repositories for scheduled workflows