# Obsidian Published articles for Obsidian. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Second Brains in the AI era: still worth it? DevFeed: [Second Brains in the AI era: still worth it?]() Original publisher: [Read original article]() Published: 2026-09-06T00:00:00Z Content type: opinion Language: en Sources: [Mutt0-ds Notes]() Topics: [Artificial Intelligence](), [context](), [AI Agent](), [Graphs](), [Obsidian]() Tags: [ai](), [ai-agent](), [context](), [knowledge-graph](), [markdown](), [obsidian]() ### AI overview The article argues that maintaining a personal knowledge base, or "second brain," is more valuable in the AI era because it gives AI assistants structured, connected context. It suggests that linked notes resemble graph memory and can help agents navigate complex information, while large unstructured collections may increase confusion and hallucinations. ### Source excerpt I've been working on my second brain(s) for years now. Brains, plural, because I had to create new ones, for example when I changed jobs...... ## How I Built a Second Brain for Agents DevFeed: [How I Built a Second Brain for Agents]() Original publisher: [Read original article]() Author: Eric Roby Published: 2026-05-26T13:01:18Z Content type: tutorial Language: en Sources: [Eric Roby]() Topics: [Obsidian](), [Claude Code](), [Markdown](), [Command-line interface](), [Git](), [Artificial Intelligence]() Tags: [ai](), [claude-code](), [cli](), [git](), [markdown](), [memory](), [obsidian]() ### AI overview The author describes using an Obsidian vault of Markdown files as a persistent context system for Claude Code and other agents. The setup includes four folders, a daily note, and essential plugins, with the goal of preserving project decisions and making notes available to future agent sessions. ### Source excerpt The notes aren't for me anymore. They're for the next agent that asks me what I already know. ## Building a Deep Research Agent Over Private Notes, Highlights, and Transcripts DevFeed: [Building a Deep Research Agent Over Private Notes, Highlights, and Transcripts]() Original publisher: [Read original article]() Author: Paul Iusztin Published: 2026-04-21T08:00:51Z Content type: tutorial Language: en Sources: [Decoding ML]() Topics: [AI Engineering](), [Claude Code](), [Obsidian](), [Command-line interface](), [Markdown]() Tags: [agent](), [claude-code](), [cli](), [markdown](), [obsidian]() ### AI overview The article describes a deep-research agent built as three Claude Code skills that query private notes, reading highlights, and research transcripts through command-line interfaces. It uses multi-round query expansion, gap analysis, deduplication, re-ranking, and a filesystem-based wiki output rather than a vector database or RAG pipeline. ### Source excerpt A deep research agent over my notes, highlights, and transcripts, grounded in years of curated thinking, not the public web. ## Using Gemini CLI and the Obsidian CLI to manage note metadata DevFeed: [Using Gemini CLI and the Obsidian CLI to manage note metadata]() Original publisher: [Read original article]() Published: 2026-02-21T20:33:17Z Content type: article Language: en Sources: [maiatoday]() Topics: [Obsidian](), [AI Agent](), [GitHub Copilot CLI](), [Command-line interface](), [Script](), [Documentation](), [Markdown](), [Git]() Tags: [agent](), [ai-agent](), [ai-agents](), [automation](), [cli](), [docs](), [gemini](), [gemini-cli](), [git](), [knowledge-management-systems-metadata](), [markdown](), [obsidian](), [script]() ### AI overview The author describes using Gemini CLI with the Obsidian CLI, along with shell tools and scripts, to analyze and standardize metadata across an Obsidian vault. The work covered status values, Type and ContentType properties, tags, documentation, and validation scripts for future consistency checks. ### Source excerpt Let's talk about the "Obsidian Paralysis." For a while, I've been using Obsidian to jot down ideas, plan content, and collect those random snippets from the internet that feel like digital gold. I moved over from Notion a while back. The freedom of simple Markdown managed by Git was liberating. Pure, texty goodness. But--and there's always a but, isn't there?--one thing always held me back. That nagging little voice: Am I doing it right? I know, I know. The "experts" say just write the notes and let the system emerge organically. But I was forever second-guessing myself. Is this a status: NotStarted or status: not-started? Is the type a "thought" or a "note"? I was spending more time fiddling with the taxonomy and the metadata "meta-system" than actually creating content. But today, everything changed. I opened Obsidian and saw the news: they now have a CLI interface. 💡: "What if I introduced the Obsidian CLI to an AI Agent CLI?" For my experiments, I called in Gemini CLI. I basically sat them down in a terminal together, let Gemini CLI figure out what the Obsidian CLI could do, and then--with a spicy mix of grep, sed, awk, and the new Obsidian commands, we went to work. Here's the "Metadata Makeover": 1. The Status Cleanup I had Gemini pull every single Status property from every note in my vault to analyze them for consistency. It detected patterns I didn't even know I had (like all the versions of Idea Ideas Research researching). We cleaned up the mess, documented the new "Golden Rules" for statuses, and Gemini wrote a validation script that I can run that will clean things up or highlight inconsistencies. 2. The "Type" vs. "ContentType" Tangle We did the same for Type and ContentType. It turns out I was using them interchangeably like a chaotic neutral character. Gemini helped me settle on a single source of truth, updated my docs, and tweaked the validation script to keep things tidy. 3. The Tag Jungle We looked at everything--frontmatter tags, in-document hashtag ## The Engineer's Guide to AI-Assisted Productivity DevFeed: [The Engineer's Guide to AI-Assisted Productivity]() Original publisher: [Read original article]() Author: Alex Razvant Published: 2026-02-12T12:01:56Z Content type: article Language: en Sources: [Neural Bits]() Topics: [Artificial Intelligence](), [code productivity](), [coding](), [Pull Request](), [Claude Code](), [cursor](), [hooks](), [Obsidian]() Tags: [agent](), [ai](), [also](), [article](), [claude](), [claude-code](), [code](), [cursor](), [developer-productivity](), [guide](), [hooks](), [obsidian](), [open-source](), [productivity](), [pull-request]() ### AI overview This article argues that AI-assisted software development should prioritize design, planning, maintainability, and effective safeguards over raw lines of code. It presents habits involving Cursor Rules, Claude Code Skills, agent plugins, pull-request rules, reviews, hooks, and an Obsidian-based daily memory dump. ### Source excerpt Six habits that keep you fast and maintainable. Cursor Rules, Claude Code Skills, Agent Plugins, PR rules, non-nitpicky reviews, hooks, and Daily memory dump with Obsidian. ## How I Use Obsidian DevFeed: [How I Use Obsidian]() Original publisher: [Read original article]() Author: Calvin French-Owen Published: 2026-01-07T22:00:00Z Content type: tutorial Language: en Sources: [Calvin French-Owen]() Topics: [Obsidian](), [Local-First](), [Markdown](), [Claude Code]() Tags: [local-first](), [markdown](), [notes](), [obsidian](), [research](), [setup](), [template]() ### AI overview A personal guide to using Obsidian as a local-first Markdown environment for thinking and writing. The author's central principle is that note-taking should elicit thought, with minimal emphasis on organization and automation beyond practical needs. ### Source excerpt Obsidian has become my personal operating system for thinking and writing. Here's the golden rule I follow and the systems I use. ## What You Don't See: My Engineering Process Behind Each Article DevFeed: [What You Don't See: My Engineering Process Behind Each Article]() Original publisher: [Read original article]() Author: Alex Razvant Published: 2025-11-01T14:02:32Z Content type: article Language: en Sources: [Neural Bits]() Topics: [Building AI Systems](), [AI Strategy](), [Tooling](), [Notion](), [Obsidian](), [Markdown](), [Retrieval Augmented Generation (RAG)]() Tags: [ai](), [article](), [build](), [design](), [engineering](), [files](), [markdown](), [notes](), [obsidian](), [system-design]() ### AI overview The article explains the behind-the-scenes process of creating a practical AI/ML engineering newsletter. It describes capturing ideas, collecting notes and references, grouping them into topics, planning structure and visuals, building and revising projects, and writing about the results. It also emphasizes that engineering involves substantial reading, writing, design, and communication in addition to coding. ### Source excerpt My Working Desk. How I capture ideas, sketch System Design Diagrams, Write and Build AI Projects for this newsletter. ## Appending Text to Obsidian via Shortcuts DevFeed: [Appending Text to Obsidian via Shortcuts]() Original publisher: [Read original article]() Author: Rob Published: 2025-10-14T10:00:00Z Content type: tutorial Language: en Sources: [Rob Allen]() Topics: [Obsidian](), [context]() Tags: [apple](), [automate](), [dialog](), [keyboard](), [mac](), [obsidian](), [schema](), [shortcuts]() ### AI overview This tutorial explains how to use Apple Shortcuts and Obsidian's obsidian:// URI schema to append text to the current Obsidian daily note. The shortcut prompts for text, adds the current time as a heading, URL-encodes the content, and opens the URI with the append parameter. ### Source excerpt Sometimes it's helpful to add some text to my current Obsidian daily note without having to switch to Obsidian, find the daily note and then type my text. To do this, we can use the magic of Obsidian's obsidian:// URI schema and automate the text capture in Apple Shortcuts, with an assigned keyboard shortcut to activate it. This is the Shortcut: There's a number of steps in the Shortcut. Firstly we Ask For some text... continue reading. ## Overengineering an Obsidian dashboard to get better at Marvel Snap DevFeed: [Overengineering an Obsidian dashboard to get better at Marvel Snap]() Original publisher: [Read original article]() Author: Harsh Shandilya Published: 2025-04-01T05:16:52Z Content type: article Language: en Sources: [Posts on Harsh Shandilya]() Topics: [Obsidian](), [dashboards](), [data](), [Statistics]() Tags: [dashboard](), [data](), [games](), [markdown](), [obsidian](), [plugin](), [statistics](), [visualization](), [yaml]() ### AI overview The author describes building an Obsidian-based system to track and visualize Marvel Snap game statistics. The system uses YAML frontmatter, Markdown notes, templates, and the Obsidian DataView plugin to analyze data such as decks, locations, outcomes, and cubes. ### Source excerpt Using data to answer the ultimate gamer question - why am I so bad? ## The Obsidian Migration - One Week Later DevFeed: [The Obsidian Migration - One Week Later]() Original publisher: [Read original article]() Author: Harsh Shandilya Published: 2025-03-17T05:38:37Z Content type: article Language: en Sources: [Posts on Harsh Shandilya]() Topics: [Obsidian](), [migration](), [GitHub Copilot](), [Code](), [Python](), [Mobile]() Tags: [code](), [experience-report](), [github-copilot](), [logseq](), [migration](), [mobile](), [notes](), [obsidian](), [python]() ### AI overview An experience report about moving from Logseq to Obsidian after a week. The author describes using a Python script, developed iteratively with GitHub Copilot, to migrate dates and tags, and notes that Obsidian plugins also work on mobile. ### Source excerpt An experience report of using Obsidian for a week, coming from a year of Logseq ## Migrating from Logseq to Obsidian DevFeed: [Migrating from Logseq to Obsidian]() Original publisher: [Read original article]() Author: Harsh Shandilya Published: 2025-03-09T10:29:00Z Content type: tutorial Language: en Sources: [Posts on Harsh Shandilya]() Topics: [Obsidian](), [migration](), [task management](), [configuration]() Tags: [configuration](), [daily](), [git](), [logseq](), [migrate](), [notes](), [obsidian](), [plugins]() ### AI overview The author describes migrating a daily journaling workflow from Logseq to Obsidian after Logseq's Electron version became end-of-life and was removed from Nixpkgs on security grounds. The article covers file changes, enabled plugins, configuration settings, and unresolved migration issues. ### Source excerpt Logseq's clunky apps and glacial development pace finally motivated me to migrate my journaling to Obsidian, here's how I did it. ## Intro to the new site DevFeed: [Intro to the new site]() Original publisher: [Read original article]() Author: James Long Published: 2024-07-09T12:00:00Z Content type: article Language: en Sources: [James Long]() Topics: [Back end](), [Obsidian](), [User experience (UX)](), [Syntax Highlighting](), [render](), [math]() Tags: [backend](), [math](), [obsidian](), [render](), [syntax-highlighting](), [ux](), [workflow](), [writing]() ### AI overview The author introduces a new site backend and a workflow centered on Obsidian for fast writing and publishing. The site supports interactive JavaScript code blocks, syntax highlighting, DOM output, rendering functions, and KaTeX mathematics, motivated partly by the author's AI studies. ### Source excerpt I just pushed a new backend for this site. I love having a quick direct connection to my site: being able to write content and publish it with a quick press of a key. Previously, I was using logseq for this but while writing my latest post I got frustrated with how slow it is. I use this site not just for writing content, but also quick sketches of interactive code. I can easily make a code block interactive by tagging it to run inline in the page, making it easy to develop quick ideas. For this to work, publishing needs to be instant and the editing experience is vital. In logseq, it took 3-4 seconds to publish content (some of this is due to how I wired up the process) but worse is the editing experience in large posts with lots of code was very slow and frustrating. My new setup uses obsidian to write content which I've found extremely polished and fast. A big difference is logseq is an "outliner" and obsidian treats content as a simple file of text. I'll miss certain features of outliners but overall the UX improvement is very much worth it. New site allows code with syntax highlighting (just as before): function calc(x) { return x + 6 * 10000; } ^659b71 I can make code blocks easily run by adding the run tag to a codeblock. It looks like this: ```js run function calc(x) { return x + 5 * 10; } return calc(10); ``` ^4536cf If I want to show something from the code I can just return the value and it appears in the DOM: (note: skipping interactive content block) ^ef4d56 Alternatively I could use a render function within the code block to do the same thing: render(calc(10)). It's a little more verbose, but the benefit with this is I can render multiple things and at different places in the call stack. I also took the time to support math which is rendered with katex. For example $g(\\sqrt{a^2 + b^2})$ renders as this: $g(\sqrt{a^2 + b^2})$. This new workflow will be instrumental in my AI studies, which was the primary motivation for this rehaul. Watch this space: I ## JavaScript interoperability DevFeed: [JavaScript interoperability]() Original publisher: [Read original article]() Published: 2023-12-18T00:15:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [interoperability](), [JavaScript](), [Kotlin](), [TypeScript](), [multiplatform](), [npm](), [React](), [Website]() Tags: [gradle](), [how-to](), [interoperability](), [javascript](), [kotlin](), [multiplatform](), [npm](), [obsidian](), [react](), [typescript](), [workshop-learning-programming]() ### AI overview This tutorial explains how to move reusable code from Kotlin/JVM projects into a multiplatform module, build a package for JavaScript or TypeScript, and distribute it through npm. It discusses practical examples involving an Obsidian plugin, a web client, and a React application, along with trade-offs and Kotlin version considerations. ### Source excerpt How to interoperate between Kotlin and JavaScript. ## My Second Brain... 6 Months later: Obsidian update DevFeed: [My Second Brain... 6 Months later: Obsidian update]() Original publisher: [Read original article]() Published: 2023-09-13T00:00:00Z Content type: article Language: en Sources: [Mutt0-ds Notes]() Topics: [Obsidian](), [Markdown](), [Automation](), [Documentation](), [Python]() Tags: [automation](), [code](), [documentation](), [markdown](), [notes](), [obsidian](), [ocr](), [plugins](), [repository](), [scripts](), [search](), [security](), [update]() ### AI overview The author provides a six-month update on using Obsidian as a secure, structured repository for team documentation and personal notes. They describe collecting and organizing varied information, linking orphaned notes, storing code snippets, and experimenting with automation, including OCR-based conversion of PowerPoint and Word content into searchable Markdown. ### Source excerpt It's been quite the journey since I first delved into Second Brain technologies for organizing my team's documentation. I previously shared... ## Maximizing Productivity with Obsidian: My Second Brain for Organizing Work Notes DevFeed: [Maximizing Productivity with Obsidian: My Second Brain for Organizing Work Notes]() Original publisher: [Read original article]() Published: 2023-02-24T00:00:00Z Content type: article Language: en Sources: [Mutt0-ds Notes]() Topics: [Obsidian](), [data](), [Notion](), [Wiki]() Tags: [brain](), [documentation](), [notes](), [obsidian](), [productivity](), [ux](), [wiki](), [work]() ### AI overview The article explains brain dumping and the second-brain method for organizing information, tasks, and notes. It describes using Notion for personal notes and Obsidian for work notes, while noting that the available text ends during the discussion of Obsidian. ### Source excerpt 🧠 Introduction to Second Brains & Brain Dumping As I'm working with data all the time, I'm aware of the importance of keeping it in a safe... ## Year in Review: 2022 DevFeed: [Year in Review: 2022]() Original publisher: [Read original article]() Author: hello@taniarascia.com Published: 2023-01-02T00:00:00Z Content type: opinion Language: en Sources: [Tania Rascia]() Topics: [Development](), [Obsidian](), [App]() Tags: [gaming](), [iphone](), [life](), [mac](), [obsidian](), [review](), [twitch](), [windows](), [year-in-review]() ### AI overview A personal year-in-review covering the author's hopes and experiences around the start of 2023, along with recommendations for television, film, books, apps, and gaming. The author also discusses switching from Bear and Todoist to Obsidian for Markdown-based notes and todos with synchronization across Mac, Windows, and iPhone. ### Source excerpt Happy New Year, friends! Time to write another year in review. This will be the seventh time I've done this. Here are all the previous ones... ## Obsidian: My second brain DevFeed: [Obsidian: My second brain]() Original publisher: [Read original article]() Author: Siddhesh Patil Published: 2022-08-15T23:50:55Z Content type: article Language: en Sources: [Sid Patil - Android Engineer and Kotlin Advocate]() Topics: [Obsidian](), [Markdown](), [code productivity](), [Code]() Tags: [android](), [android-development-tools](), [best-markdown-tools](), [best-tools-for-android-developers](), [boost-developer-productivity](), [code](), [developer-productivity](), [jetpack-compose](), [markdown](), [markdown-editors](), [markdown-note-taking-tools](), [notes](), [obsidian](), [obsidian-for-markdown](), [obsidian-md](), [productivity](), [snippet]() ### AI overview The article explains how a developer uses Obsidian, a Markdown-based note-taking tool, to manage thoughts, TODOs, web links, and code snippets. It highlights Markdown's simplicity, local file organization, backlinking, and the potential to turn notes into website pages. ### Source excerpt Tired of moving between note-taking tools? Keep losing code snippets, TODOs and ideas? Meet Obsidian, a Markdown note taking tool to boost your developer productivity.