| name | sync-claude-sessions |
| description | Sync Claude Code sessions to Obsidian markdown. Export, resume, add notes, close sessions. USE WHEN user says "sync sessions", "export sessions", "resume session", "add session note", "close session", "log session". |
Sync Claude Sessions
Export Claude Code conversations to Obsidian for observability and analysis.
Quick Reference
alias cs="python3 ~/.claude/skills/sync-claude-sessions/scripts/claude-sessions"
cs list
cs list --all
cs export --today
cs resume --pick
cs note "got it working"
cs close "done"
Commands
| Command | Description |
|---|
sync | Sync session (hook or explicit) |
export | Batch export (--today, --all, <file>) |
resume | Resume session (--pick, --active, <file>) |
note | Add timestamped comment |
close | Mark done + optional comment |
list | List sessions (--active, --all, --json) |
Workflow Routing
Output
Sessions exported to Claude-Sessions/ with:
- Frontmatter:
type, date, session_id, title, summary, skills, messages, status, tags, rating, comments
- Content: Summary, Skills Used (linked), Artifacts (wiki-linked), My Notes, Conversation
Preserved on Sync
## My Notes section
- Frontmatter:
comments, related, status, tags, rating
Frontmatter Schema
See Templates/Types/claude-session.md for the canonical template.
type: claude-session
date: YYYY-MM-DD
session_id: uuid
title: "..."
summary: "..."
skills: [skill1, skill2]
messages: 42
last_activity: ISO timestamp
status: active | done | blocked | handoff
tags: []
rating: null
comments: |
[2026-02-05 14:30] Comment here
[2026-02-05 15:00] Another comment
related: []
Tags Schema
Tags are defined in schema/tags.yaml with descriptions, keywords, and examples.
Type tags: research, implementation, debugging, planning, brainstorm, admin, quick, video, automation, writing
Project tags: lab, openclaw, personal, client
Agent should read schema/tags.yaml to validate tags when logging sessions.