Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/josephyaduvanshi/claude-history-manager/llms.txt

Use this file to discover all available pages before exploring further.

Chronicle can resume any indexed session directly inside the terminal and editor of your choice. Select a session in the list, press a key, and Chronicle builds the correct provider-specific resume command — preserving the original working directory — and hands it off to your terminal. Nothing to copy, nothing to paste.

Keyboard shortcuts for resuming

ShortcutAction
Resume the selected session in your default terminal
⌘↵Open the terminal picker dropdown to choose a terminal for this session
⌘⇧↵Resume the most-recently-modified session in your default terminal without opening any UI
⌘⇧↵ is the fastest path when you just want to jump back into your last session without touching the main window or the menubar dropdown — it works system-wide.

Supported terminals

Chronicle detects which terminals are installed and only shows the ones it finds. Detection resolves the installed .app bundle first, then falls back to a CLI shim on PATH.

Ghostty

Uses ghostty --working-directory=... to open the session in a new window at the correct path.

iTerm

Uses AppleScript to open a new window and run the resume command.

Terminal.app

Uses AppleScript to open a new tab or window.

Alacritty

Launches via the Alacritty CLI with the correct working directory.

WezTerm

Launches via the WezTerm CLI.

kitty

Launches via the kitty remote-control interface.
Only terminals that are actually installed appear in the terminal picker. If a terminal you expected to see is missing, verify it is installed as an .app bundle in /Applications/ or that its CLI shim is on your PATH.

Provider-specific resume commands

Chronicle routes to the correct CLI command based on the session’s provider. The working directory from the original session is preserved in the command.
claude --resume <uuid>
The UUID is the session identifier Chronicle reads from the JSONL file under ~/.claude/projects/.

Setting a default terminal

Your default terminal applies to and ⌘⇧↵. To change it:
1

Open Settings

Press ⌘, to open Settings.
2

Select the Terminal pane

Click Terminal in the Settings sidebar.
3

Pick your terminal

Choose from the terminals Chronicle detected on your system. Only installed terminals appear in the list.

Per-session terminal override

You can pick a different terminal for a specific session without changing your default. Press ⌘↵ with a session selected to open the terminal picker dropdown for that session only. The override is one-time — your default is not changed.

Opening sessions in an editor

Alongside the terminal launcher, Chronicle can open any session’s working directory in your code editor. The Open in <Editor> action supports VS Code, Cursor, Zed, and Xcode, using the same install-detection logic as the terminal launcher (bundle lookup first, CLI shim on PATH as fallback). Use ⌘,Editor to set your default.

Ghostty security prompt

Every time you resume a session in Ghostty, macOS shows a one-time-per-click “Allow Ghostty to execute…” confirmation dialog. This is a Ghostty security gate and cannot be turned off in Ghostty’s configuration. The other supported terminals do not show this prompt.

Build docs developers (and LLMs) love