<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Obsidian on Lynx Tech Blog</title><link>https://blog.lynxflow.co/en/tags/obsidian/</link><description>Recent content in Obsidian on Lynx Tech Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Sun, 13 Sep 2026 17:45:00 +0800</lastBuildDate><atom:link href="https://blog.lynxflow.co/en/tags/obsidian/index.xml" rel="self" type="application/rss+xml"/><item><title>Obsidian + Claude Code: My Founder OS Dual-Driving Workflow</title><link>https://blog.lynxflow.co/en/posts/obsidian-claude-code-founder-os-workflow/</link><pubDate>Sun, 13 Sep 2026 17:45:00 +0800</pubDate><guid>https://blog.lynxflow.co/en/posts/obsidian-claude-code-founder-os-workflow/</guid><description>&lt;img src="https://blog.lynxflow.co/images/obsidian-claude-code-cover.png" alt="Featured image of post Obsidian + Claude Code: My Founder OS Dual-Driving Workflow" /&gt;The previous post, I Built Myself a Founder OS With Claude Code, covered how to build a knowledge base. This one covers how to use it.
Specifically: how to let human and AI collaborate inside the same knowledge base. I read the dashboard and tweak notes in Obsidian; Claude Code runs batch triage, fills templates, and migrates files in the terminal. Both sides edit the same Markdown files, and Git records everything.</description></item></channel></rss>