obsidian-catalog

Sync Claude conversations by running the obsidian-catalog script, which imports browser exports and Claude Code history into your Obsidian vault as organized Markdown files with rich frontmatter metadata, enabling searchable catalogs under Sessions/Browser and Sessions/Code folders.

Yes. Obsidian-catalog writes structured frontmatter (session_id, date, topics, summary) compatible with Dataview queries, allowing you to filter and analyze conversations by date, topic, or project directly in your vault dashboards.

Obsidian-catalog processes browser exports and Claude Code history files, converting them into Markdown with frontmatter. It preserves original exports for re-processing or auditing while creating indexed, queryable session records.

No. Obsidian-catalog performs incremental syncs, processing only new sessions on subsequent runs. Full syncs import all conversations at once, then only new additions are fetched—no manual re-cataloging needed.

Original exports are retained in raw form for re-processing or auditing purposes. Obsidian-catalog preserves them while creating separate indexed Markdown files with metadata and summaries for fast search and organization.

Yes. The frontmatter includes topic and project metadata, and the Dataview-compatible structure supports filtering and dashboard creation by any metadata field, letting you organize conversations by project, date, or topic automatically.