Obsidian + Claude workflows

Atenov_D’s multi-post demo was shared on X and can be found as an unrolled thread summarizing the steps and screenshots of the setup. (unrollnow.com) The workflow captured raw audio-to-text inside an Obsidian vault using a Whisper-powered transcription plugin that produces timestamped, markdown-ready transcripts for further processing. (github.com) Anthropic’s Claude Code CLI explicitly supports reading and writing local files, running shell commands, and integrating with MCP servers—capabilities used to transform vault transcripts into structured files and run automation steps. (github.com) Community plugins (for example, the “Claudian”/deivid11 Obsidian plugin and related sidebar integrations) let users invoke Claude Code from inside Obsidian with slash commands, file operations, and in‑vault editing without leaving the app. (github.com) Reusable starter kits and templates such as “claudesidian” provide.claude folders, install scripts, and recommended vault layouts so other users can reproduce a notes→site pipeline quickly. (github.com) Publishing the resulting site can be done with Obsidian Publish (an official hosting option billed from $8/month) or by exporting the vault to a static site pipeline (Next.js/Vercel or tooling like Kiln) for a self-hosted serverless deployment. (obsidian.md)