> ## Documentation Index
> Fetch the complete documentation index at: https://ade-ac1c6011-ade-mobile-chat-stability-54bd7ef0.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Workspace graph

> See lanes, branches, PRs, stacks, and merge risk in one visual map.

The Graph view turns your repository state into a map. Use it when the lane list is not enough and you need to see how work relates.

<CardGroup cols={3}>
  <Card title="Topology" icon="diagram-project">
    See lanes, branches, PR links, and stack relationships.
  </Card>

  <Card title="Merge risk" icon="triangle-exclamation">
    Spot branches that are likely to conflict before merge time.
  </Card>

  <Card title="Navigation" icon="arrow-pointer">
    Jump from the graph into a lane or PR.
  </Card>
</CardGroup>

## What appears on the graph

| Node   | Meaning                                                |
| ------ | ------------------------------------------------------ |
| Lane   | A registered ADE lane and its branch.                  |
| PR     | A GitHub pull request linked to a lane.                |
| Branch | A branch ADE can see but has not registered as a lane. |

Edges show base-branch and stack relationships.

## When to use it

* Before merging several active lanes.
* When a stack gets hard to reason about.
* When you need to know which work depends on another branch.
* When an agent has created several lanes and you want the map.

## Merge simulation

ADE can simulate merges and surface likely conflicts. Treat the result as a warning system, not a substitute for final CI and review. Re-run simulation after major commits.

<Tip>
  Graph is most useful late in a work session, when you are deciding merge order and cleanup.
</Tip>