---
title: "I turned my Obsidian vault into an AI-powered work OS — open source, free"
tags:
  - wiki
  - sources
sources:
  - "[[I turned my Obsidian vault into an AI-powered work OS — open source, free]]"
domains: [agentic, startup]
date: "2026-07-17T06:22:58.690Z"
created: "2026-07-17T06:22:58.690Z"
includeInRss: false
---

# I turned my Obsidian vault into an AI-powered work OS — open source, free

## Takeaways

- **ObsidianOS** (`benoror/obsidianos_work`) is an open-source (MIT) Obsidian vault with agent skills run via slash commands — local markdown, no SaaS lock-in.
- Key skills: **`/meeting`** (Calendar → structured note → wrap with transcript + wikilinks + tasks), **`/recap this week`** (vault + Gmail + Calendar), **`/followup-todos`** (action items as Tasks checkboxes).
- **Agent-agnostic** — works with Cursor, Claude Code, OpenCode, or any MCP client; skills are markdown workflow descriptions.
- Targets founders/builders drowning in meetings, email, and task lists; data stays on-machine in plain files you own.
- Ben uses it daily managing an engineering team (standups, 1:1s, product reviews, tech briefs).
- Indie Hackers post is the public launch narrative for the same system documented in this vault's `AGENTS.md` and skills.

## Notes

Primary source for Ben's own ObsidianOS product thesis — this wiki ingest and vault agent architecture are direct implementations of the pattern described here.

## Open questions

- Which ObsidianOS skills should be promoted first for external adopters vs kept as personal-vault-only workflows?