Skip to main content

arvre

A terminal graph of your Claude Code sessions and their forks.

/resume shows sessions as a flat list. arvre shows them as a tree, so you can see which session was forked from which, when each one was last used, and jump between parents and children.

Example output (sample names):

● Auth refactor  · 3h ago (2026-10-30 19:12)  · 2 children
├─ ● try the other approach  · 1h ago (2026-10-30 21:02)  · ↑ Auth refactor
└─ ● spike rename test  · 2m ago (2026-10-30 22:08)  · ↑ Auth refactor

Install

With pipx (macOS and Linux, Python 3.11+):

pipx install git+https://github.com/victorcarrico/arvre

You need Claude Code installed, with claude on your PATH, for the "open in this terminal" action.

Usage

arvre                      # sessions from the current directory, last 24 hours
arvre --all-time           # all sessions, not just the last 24 hours
arvre --all-projects       # sessions from every project
arvre --style flow         # start with the left-to-right flowchart
arvre --theme ocean        # start with a colour theme
arvre --print              # print the tree as text and exit

Run arvre --help for all options.

Keys

Key Action
↑ / ↓ (k / j) Move. In compact style, through the tree. In flowchart style, to the next session at the same depth.
← / → (h / l) Go to the parent / first child
Enter Open the action menu for the selected session (or click it twice)
a Toggle last 24 hours / all time
p Toggle this directory / all projects
v Toggle compact / flowchart style
t Cycle colour themes (classic, ocean, forest, sunset)
r Reload
q Quit

The action menu offers:

  • Open in this terminal: runs claude --resume <id> in the session's directory, and returns to arvre when Claude exits.
  • Copy command: copies cd '<dir>' && claude --resume <id> to the clipboard, for pasting into another terminal.

How forks are detected

Claude Code doesn't record a parent link when you fork a session. A fork is a copy of its parent's messages, so arvre links each session to the earlier session that shares the most message IDs with it. The details are in docs/forks.md.

Session data is read from ~/.claude/projects. This is an undocumented format, so a future Claude Code release could change it.

Development

python3 -m venv .venv
.venv/bin/pip install -e ".[test]"
.venv/bin/python -m pytest

License

MIT. See LICENSE.

Metadata

Release files for arvre 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for arvre 0.1.0
File Size Uploaded Provenance Actions
arvre-0.1.0.tar.gz 17.0 kB With provenance Details for arvre-0.1.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for arvre 0.1.0
File Interpreter ABI Platform Actions
arvre-0.1.0-py3-none-any.whl Python 3 none any Details for arvre-0.1.0-py3-none-any.whl

Total release size: 33.5 kB

Release files / arvre-0.1.0.tar.gz

Download URL arvre-0.1.0.tar.gz
Size 17.0 kB
Tags Source
SHA-256 checksum
How to use checksums
ce7b774fc685b9654fd9f80e1e7f9db14df606a53d32b776cac3e2468c37dc1b
BLAKE2b-256 checksum
How to use checksums
976dba28c6661439f7c80a33042992c3ba06ed0ac5366dcb5d839aeca77a003e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 31, 2026.

Transparency log

Release files / arvre-0.1.0-py3-none-any.whl

Download URL arvre-0.1.0-py3-none-any.whl
Size 16.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
88d2ede76ea7d88c4bd04c0f32c67db7f40b2e6dcb0863c2954beb32da2474ba
BLAKE2b-256 checksum
How to use checksums
2e93cc164cdebe49ef0280b6c2072b6dd5bb23b00de4cc2793496263ed22402f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 31, 2026.

Transparency log

Security for arvre 0.1.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for arvre-0.1.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 31, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page