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.

Smart folders are saved queries that live in the sidebar alongside your workspaces. They re-run automatically each time you select them, so their contents always reflect the current state of your session index. Chronicle ships four built-in smart folders and lets you create an unlimited number of custom compound folders with their own filter combinations.

Built-in smart folders

Four smart folders are seeded on first launch and cannot be deleted or renamed:

Today

Sessions modified on the current calendar day.

This week

Sessions modified within the last 7 days.

Used `git push`

Sessions where the assistant invoked git push during the conversation, detected from the session’s tool-call flags.

Errored sessions

Sessions that terminated with an error or that the CLI marked as failed.

Smart folder query types

Every smart folder is backed by a SmartFolderQuery value persisted as JSON in the database. The available query cases are:
CaseDescription
.todaySessions modified today
.thisWeekSessions modified in the last 7 days
.lastNDays(Int)Sessions modified within the last N days
.usedGitPushSessions with a git_push flag
.erroredSessionsSessions with an errored flag
.search(SearchQuery)A saved search query (supports all slash filters)
.compound(SmartFolderCompoundQuery)A rich user-authored filter (see below)
Unknown query types in the database decode to a .custom(raw:) case and render as regular saved searches — no crash, no data loss when opening a database from a newer Chronicle version.

Creating custom smart folders

Custom smart folders use the .compound query type, which lets you combine multiple independent filter conditions. All conditions are ANDed together — a session must satisfy every active filter to appear in the folder.
1

Open the new folder sheet

Click the + button in the Smart Folders section of the sidebar, or use the File menu.
2

Set a name

Give the folder a descriptive name that will appear in the sidebar.
3

Configure filters

Add any combination of the available filters. At least one filter must be active — a completely blank compound query would match every session, which Chronicle prevents you from saving.
4

Save

Click Save. The folder appears in the sidebar immediately and updates automatically.

Available compound filters

Restrict results to a single workspace. The value is the workspace’s internal ID — the dash-encoded folder name under ~/.claude/projects/ for Claude sessions, or the equivalent key for Codex and Gemini.
Sessions must carry every tag in the list. Specify one or more tag IDs from your tag library. An empty tag list means no tag constraint.
Filter by total token count. Set only a lower bound (minTokens) to find long sessions, only an upper bound (maxTokens) to find short ones, or both for a range. Either bound is inclusive.
Equivalent to “modified within the last N days”. Translates to a last_modified_at >= now − N × 86400 SQL clause. Leave unset for no date constraint.
Sessions must carry every flag in the list. The flag strings that Chronicle currently tracks are git_push and errored, matching the built-in smart folders.
Optional free text. When non-blank, runs the same title-LIKE or FTS5 transcript search that the main search bar uses.
The Save button is disabled when all compound filter fields are empty. A blank compound query would match every non-deleted, non-archived session, which is almost never the intended behavior.

iCloud sync

When iCloud Drive sync is enabled in Settings, smart folder definitions sync alongside tags, pins, notes, and custom titles. Every synced record carries the provider it belongs to (.claude, .codex, or .gemini), so a smart folder you create under Claude does not appear in your Codex sidebar on another Mac.
Transcript content never syncs. Only the folder definition (name, query, sort order) travels through iCloud. The sessions themselves remain on the device that generated them.

Build docs developers (and LLMs) love