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

# Timeline

> See every change to a project over time — who changed what, when, and on which stream — and restore an earlier version whenever you need to.

The Timeline is your project's change history. It records every version of the project as a change you can inspect, compare, and restore — so you always know how the logic reached its current state, and you can go back if you need to.

## Where to find the Timeline

Open the **Timeline** tab in the right sidebar of the [Blueprint Editor](/editor/toolbars-and-panels#right-sidebar).

<img src="https://mintcdn.com/leapter/qD4bhNedlRbMsoV4/images/timeline-panel.png?fit=max&auto=format&n=qD4bhNedlRbMsoV4&q=85&s=305477bb7382b24c483450876e2b7f38" alt="The Timeline of the Loan Application Scorecard — the newest change on main, the closed draft lower_affordability_limit with Review opened and its struck-through changes, and older changes on main, one of them marked with the release v1.0" width="368" height="610" data-path="images/timeline-panel.png" />

Each row is one change, newest at the top. The panel shows:

| Element | Description |
| :- | :- |
| **Change title** | A short summary of what happened — for example *Edit logic in 'Quick Affordability Check'* or *Review opened* |
| **Stream pill** | A colored label (**main** or **draft / …**) marking the stream the change belongs to |
| **Release pill** | The [release](/release-and-integrate/releases) that was created from this change, such as **v1.0** |
| **Graph** | The colored lines on the left connect the changes of each stream and show where drafts start from and return to main |
| **Time** | When the change was made, as a relative time (*3h ago*) |

**+ New draft** at the top starts a [draft](/track-changes/change-workflow#start-a-draft) when the project uses **Pending changes + Save**.

<Note>
  The list does **not** show who made each change. To see the author, open the change.
</Note>

## Streams and the change graph

A **stream** is a line of changes. Every project has a **main** stream. With the [change workflow](/track-changes/change-workflow) **Pending changes + Save**, you also work on **drafts** — separate streams that start from main and return to it when you save them.

The graph makes this visible:

* A draft's lane starts at the version of main it was created from.
* When a draft is saved, a new change appears on main. Its card says which draft was saved and lists the changes it included.
* **Saved drafts are struck through** — once a draft is saved, its history stays visible but is crossed out.

## Open a change to see the detail

Click any change to expand its card.

<img src="https://mintcdn.com/leapter/qD4bhNedlRbMsoV4/images/timeline-change-card.png?fit=max&auto=format&n=qD4bhNedlRbMsoV4&q=85&s=20bdbc59d92042ee8bb4df4a652a6062" alt="The card of the newest change on main — Edit logic in 'Quick Affordability Check', Apply draft Lower affordability limit to main with the included changes, the badges Applied to main, System, and main, René with the timestamp and project v10, and the actions Open review, Open this version, Restore this version, Create release, and Compare" width="334" height="476" data-path="images/timeline-change-card.png" />

The card shows:

* **What happened** — a description and badges for the kind of change (for example **Applied to main**), its origin (**Manual edit**, **AI**, or **System**), and its stream
* **Who and when** — the author, the exact timestamp, and the **project version** the change produced
* **Actions** — inspect, restore, release, or compare the change

<Note>
  Timestamps in the list are rounded (*3h ago*). The exact time — down to the minute — is only shown on the card.
</Note>

### Actions on a change

| Action | What it does |
| :- | :- |
| **View conversation** | Opens the Lab Agent conversation that produced this change, when there is one — so you can read the reasoning behind an edit, not just the result |
| **Open review** | Opens the [review](/track-changes/review-and-approvals) of the draft this change saved, read-only |
| **Open this version** | Loads the project as it looked at this change, read-only, so you can look around without altering anything |
| **Restore this version** | Brings the project back to this state |
| **Create release** | Freezes the project as it was at this change into a [release](/release-and-integrate/releases) — available on changes on main |

### Compare changes

Use the **Compare** section of a change card to see exactly what a change altered:

* **Compare with previous** — compare this change with the one before it
* **Compare with target stream** — on a draft, compare it with the stream it will be saved to (usually main)
* **Select for compare…** — pick this change as one side of a comparison, then choose another change as the other side

### Reading a comparison

Once you pick two versions, the editor switches to **Compare** and shows the difference between them.

<img src="https://mintcdn.com/leapter/qD4bhNedlRbMsoV4/images/timeline-compare.png?fit=max&auto=format&n=qD4bhNedlRbMsoV4&q=85&s=45507dee1c642f16c89d9037ba70209b" alt="Compare from main v9 to main v10 — the section Compare With Income with 40 struck through and 35 added in its description and in the step Within the 35% limit, the changed sections marked in the Contents sidebar, and the Diff Summary listing three changes" width="1440" height="900" data-path="images/timeline-compare.png" />

* The document marks every change **in place**: removed values are struck through in red, added values are highlighted in green. In the example above, the affordability limit changes from `40` to `35`.
* The Contents sidebar marks the Blueprints and sections that changed.
* The **Diff Summary** at the bottom names the two versions — for example **main v9 → main v10** — and lists every change, grouped by Blueprint and element.

Click **Close compare** to return to the current version.

## Restore an earlier version

If a change introduced a problem, you can roll the project back:

1. Open the change you want to return to.
2. Click **Restore this version** and confirm.

Leapter adds a new **Restored** change at the top of the Timeline, so the history in between is never lost. Restoring can't be undone with **Ctrl+Z** — to go back, restore again from another point in the Timeline.

## What to do next

* **[Change Workflow](/track-changes/change-workflow)** — choose how edits are saved, and work on drafts
* **[Review & Approvals](/track-changes/review-and-approvals)** — require a review before changes reach main
* **[Lab Agent](/editing/lab-agent)** — the conversations behind your changes, available from **View conversation**


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.