Skip to main content
The History tab is your project’s timeline. It has two surfaces sharing one page: a Commits view — a GitKraken-style commit graph for the focused lane — and an Activity view that merges operations, chat sessions, CTO sessions, and worker runs into one feed. Use it to recover context, audit agent work, or recover from a lane that wandered off.

Commits

The Commits surface draws the commit DAG for whichever lane you pick from the toolbar. Each row shows the short SHA, optional HEAD and merge pills, branch ref pills, the subject, the author, and a relative timestamp — laid out as a virtualized graph that stays fast on long histories. Right-click any commit (or use the actions strip in the detail panel) for a full set of git actions:

Inspect

Check out, compare with parent, view changed files, or open the commit in the Lanes git pane.

Create

Branch, tag, or fork a brand-new lane from this exact commit with Create lane here.

Apply

Cherry-pick, revert, or soft/mixed/hard reset to the commit.

Share

Open or copy the GitHub link, copy the patch, the SHA, or the subject.
A search box above the graph supports bare text plus prefixed keys — message:, author: (or @), commit: (or #), branch:, parent:, and filters like is:merge, is:local, is:pushed. The Commits toolbar also carries a lane git actions menu for fetch, pull, push, rename, archive, rebase, and other lane-scoped operations without leaving History.
The Commits view also exposes per-lane undo / redo for the last HEAD-changing operation. ADE re-reads HEAD before it touches git and refuses if the branch moved since, so a reset never clobbers work you did afterward.

Activity

The Activity surface is a unified feed. It combines recorded operations — discrete, typed actions that changed state — with synthesized rows pulled from chat sessions, CTO snapshots, and worker runs, sorted newest-first.
SourceExamples
Git operationsCommit, checkout, merge, rebase, push, pull, fetch, cherry-pick, revert, tag, reset, stash, undo/redo.
PR operationsPR creation and related actions.
Pack refreshesLane and project context-pack regeneration.
Chat sessionsAgent chats, with provider, model, and status.
CTO & workersCTO sessions and worker runs with their status and wakeup reason.
Pick from three view modes — Graph (per-lane swimlanes), List (a sortable table), or Compact (one dense line per event). A scope selector sets how much detail shows (Key → Standard → Detailed → All), and you can further filter by lane, category, status, and time range, or search across labels, kinds, and metadata. Running events auto-refresh while the tab is focused.
Synthesized chat/CTO/worker rows are rebuilt on every refresh for display only — they’re never written into the operations table, and they don’t appear in an export.

Export

Export the operations history to CSV or JSON with the current lane and status filters applied. ADE returns the rows and the desktop writes the file through a native save dialog.
History is also available from the ade CLI and ade code:
ade history list                 # recent operations in the active project
ade history list --lane <id>     # scope to one lane's timeline
Run ade history --help to see every filter and flag.
History is local project evidence — it makes agent work inspectable. The Commits view reads real git log; it doesn’t replace Git history or GitHub review.

Files & diffs

Open the diff behind any commit you find in History.

Review

Run an on-demand AI review over a commit range you spot in the graph.