---
schema: 1
type: term
title: _Obsidian vault_
description: >-
  An **_Obsidian vault_** is the central knowledge repository — a collection of
  notes, research, and ideas — hosted on a home server and used as the layer
  that an AI assistant (Claude Code) reads, writes, and reasons over.
canonical: >-
  https://liquidgold.cc/channel/everyinc/explore/term/obsidian-vault-c87109db65c6
markdown: >-
  https://liquidgold.cc/channel/everyinc/explore/term/obsidian-vault-c87109db65c6.md
llms: null
parent: 'https://liquidgold.cc/channel/everyinc/llms.txt'
channel: everyinc
updated: '2026-10-23T22:12:35.346Z'
language: null
children: []
---


# \_Obsidian vault\_

Canonical: https://liquidgold.cc/channel/everyinc/explore/term/obsidian-vault-c87109db65c6

Parent: [Channel index](https://liquidgold.cc/channel/everyinc/llms.txt)

## Definition

An **_Obsidian vault_** is the central knowledge repository — a collection of notes, research, and ideas — hosted on a home server and used as the layer that an AI assistant (Claude Code) reads, writes, and reasons over.

&lt;Section title='How it appears in this channel'&gt;&gt;n&gt;nAn **_Obsidian vault_** is the central knowledge repository in Noah Bryer's second-brain setup: a collection of **notes, research, and ideas** stored on his **home server** in the basement. Claude Code runs on top of the vault, reading and writing into it, while the vault itself holds the accumulated knowledge.[^0a68c52c-cc6f-52e7-95b0-ff0bb1862a77@0]&gt;n&gt;n&gt; Noah Bryer runs Claude Code on a basement home server, layered over his **Obsidian vault** — turning his phone into a portal to a true _second brain_.[^0a68c52c-cc6f-52e7-95b0-ff0bb1862a77@0]&gt;n&gt;n&lt;/Section&gt;&gt;n&gt;n&lt;Section title='Where the vault sits in the stack'&gt;&gt;n&gt;nThe vault is one layer of a three-part system:&gt;n&gt;n1. **Home server** — hosts the Obsidian vault and runs Claude Code on top of it.&gt;n2. **Obsidian vault** — the central repository for notes, research, and ideas.&gt;n3. **Claude Code** — the AI layer that reads, writes, and reasons over the vault.&gt;n&gt;nThe everyday interface is the **phone**: because the vault lives on the server, Noah can think, research, write, and ship code from anywhere.[^0a68c52c-cc6f-52e7-95b0-ff0bb1862a77@0]&gt;n&gt;n&lt;/Section&gt;&gt;n&gt;n&lt;Section title='What the vault enables'&gt;&gt;&gt;n&gt;nIn the captured workflow, Claude Code works over the vault to:&gt;n&gt;n- **Pull research** — searching both the web and Noah's whole node archive inside the vault.&gt;n- **Keep a running log** — accumulating learnings and best ideas over time.&gt;n- **Produce** — supporting writing, structuring ideas, and shipping code.&gt;n&gt;nThe key insight: **the power lives on the server, but the experience lives on the phone.** That separation is what makes the vault-backed setup feel like a genuine _second brain_ rather than a desk-bound tool.[^0a68c52c-cc6f-52e7-95b0-ff0bb1862a77@0]&gt;n&gt;n&lt;/Section&gt;&gt;n&gt;n&lt;KeyPoints&gt;&gt;n- The **Obsidian vault** is the central knowledge repository — notes, research, and ideas.&gt;n- It is **hosted on a home server**, with Claude Code running on top as the AI layer.&gt;n- The phone is the everyday interface into the vault-backed system.&gt;n&lt;/KeyPoints&gt;
