obsidian-conversation-backup

Automatically back up chat conversations to an Obsidian vault by running a shell script with jq for JSON parsing, scheduled via cron to create hourly incremental snapshots formatted as markdown.

Yes, you can schedule incremental markdown backups of conversations using cron. The cron job triggers a shell script that saves only new messages hourly, preventing data loss with minimal storage overhead.

Monitor token usage and prevent context loss by configuring Telegram warnings that alert you when token limits approach, prompting timely `/new` commands to reset the conversation context proactively.

Yes, you need jq to export conversations to markdown for Obsidian. The Skill requires jq for JSON parsing to extract and format chat data into color-coded callouts with timestamps.

Yes, the Obsidian conversation backup supports hourly incremental snapshots. It saves only new messages during each cron-triggered cycle, ensuring minimal storage usage while preventing data loss.

Your shell script may fail to parse JSON for Obsidian markdown export if jq is not installed or properly referenced. The Skill explicitly requires jq for JSON parsing to process conversation data correctly.