---
title: Obsidian as agent IDE
tags:
  - wiki
  - concepts
sources:
  - "[[How I use Obsidian — Steph Ango]]"
  - "[[Building Your AI-Powered Second Brain Claude Code and Obsidian]]"
  - "[[AI-Native Obsidian Vault Setup Guide]]"
  - "[[I turned my Obsidian vault into an AI-powered work OS — open source, free]]"
  - "[[The PARA Method]]"
  - "[[Karpathy LLM Wiki]]"
date: "2026-07-17T06:24:22.666Z"
created: "2026-07-17T06:24:22.666Z"
includeInRss: false
---

# Obsidian as agent IDE

Obsidian = readable filesystem UI; agents = writers/maintainers; markdown git repo = codebase.

## Takeaways

- **File over app** (kepano) — plain files outlive products.
- Bottom-up linking beats rigid PARA for some; PARA still useful for *actionable* buckets.
- AI-native vaults add CLI, skills, MCP, Bases — not just ChatGPT-in-a-pane.
- Vault-as-OS experiments (ObsidianOS, work OS plugins) push toward agent-operated personal software.

## Vault stance

Human homes (`Daily/`, `ToDos/`, `SoM/`, `Projects/`) + agent runtime (`.agents/`) + compile layer (`Wiki/`). PARA-ish intentionality without full PARA folders.