Claude Code x Obsidian poorna integration guide | Vault badhane wali AI note-taking

Har Obsidian user ne ek baar to socha hi hoga: “Kaash yeh Vault khud-ba-khud organize ho jaaye.” Claude Code Obsidian ka sabse behtareen partner hai. Kyunki Obsidian Vault asal mein Markdown files ka ek folder hi hai, aur file tree padhna-likhna Claude Code ki sabse badi takat hai.

Is article mein hum Claude Code aur Obsidian ko saath milakar Vault ko automatic grow karne ke tareeke dikhayenge - chalne wale code aur asli examples ke saath. Daily note generation, web clipping, backlink completion aur plugin development tak - sab kuch end-to-end cover karenge.

Obsidian x Claude Code kyun?

Obsidian ki taakat teen cheezon mein hai:

• Local-first: Sab kuch aapki apni machine par Markdown files
• Plain text: Koi vendor lock-in nahin, future mein bhi padhne yogya
• Link-driven: [[Note ka naam]] se har disha mein jodkar vichaar bunna

Yeh Claude Code ki taakaton se perfectly match karta hai:

• Seedhe file tree par kaam kar sakta hai (Read / Edit / Write / Glob)
• Markdown ko first-class citizen ki tarah treat karta hai (Wikilinks bhi parse karta hai)
• CLAUDE.md ke through “is Vault ke rules” sikhaaye ja sakte hain

Saar yeh hai ki Claude Code ke nazariye se Obsidian Vault “ek bahut saaf-suthra chhota project” hai. Note organization ko code likhne jaisa hi automate kar sakte hain.

Basic setup: Vault mein CLAUDE.md rakhna

Pehle Vault ki root mein CLAUDE.md rakhiye. Ab jab Vault ke andar Claude Code chalega, yeh apne aap load ho jaayegi.

# Mere Obsidian Vault ke niyam

## Directory structure
- `daily/YYYY-MM-DD.md` — Daily notes
- `zettel/` — Sthaayi notes (1 note = 1 idea, title = concept ka naam)
- `literature/` — Padhne ki notes, web article clippings
- `project/` — Chalte projects
- `meta/` — Tag definitions, templates

## Notation rules
- Note-to-note links `[[Note ka naam]]` se
- Tags file ke upar frontmatter mein
- Daily notes: fixed 3-level structure `## Today / ## Learned / ## Questions`
- Source URL frontmatter mein `source:` ke neeche

## Mana hai
- Existing notes rename karne se pehle confirm karna hoga (backlinks toot sakte hain)
- `_archive/` ke andar ki notes mein kabhi change mat karna

Vault ke rules saaf-saaf likhne se Claude Code aapke conventions ke anusaar notes generate aur edit karta hai. Inconsistent formatting ke haadse bach jaate hain.

Udaharan 1: Automatic daily note generation

Har subah ek script jo kal ki note ko summarize karke aaj ka template banaa deti hai.

#!/bin/bash
# ~/vault/scripts/daily-note.sh

TODAY=$(date +%Y-%m-%d)
YESTERDAY=$(date -d "yesterday" +%Y-%m-%d)
VAULT=~/vault

claude -p "
Kripya nimn kaarya karo:

1. $VAULT/daily/$YESTERDAY.md padho (nahin hai to skip karo)
2. Kal ke 'Today' section se 'adhoore tasks' nikalo
3. Kal ke 'Learned' section se 3 'reflection points' nikalo
4. $VAULT/daily/$TODAY.md banao, is template mein bharo:

---
date: $TODAY
tags: [daily]
---

## Today (aaj ki yojana)
- (kal ke adhoore tasks yahan)

## Learned (khoj)
_khaali_

## Questions (jaanne ke liye)
_khaali_

## Review (kal ki samiksha)
- (nikale gaye 3 points yahan)

## Links
[[$YESTERDAY]] <-> [[$(date -d tomorrow +%Y-%m-%d)]]
---

5. Banane ke baad sirf 'Daily note ban gayi' report karo
"

Isse cron, macOS launchd, ya Windows Task Scheduler mein register kar do, to subah uthte hi aaj ki note taiyaar hogi. Bas Obsidian khol kar kaam shuru.

Udaharan 2: Web articles Vault mein clip karna

Read-Later style. URL pass karo aur formatted note literature/ mein save ho jaati hai.

// scripts/clip-url.mjs
import Anthropic from "@anthropic-ai/sdk";
import { writeFileSync } from "fs";

const url = process.argv[2];
const client = new Anthropic();

const res = await client.messages.create({
  model: "claude-opus-4-6",
  max_tokens: 4096,
  tools: [{ type: "web_search_20250101", name: "web_search" }],
  messages: [{
    role: "user",
    content: `Is URL ka article laao aur Obsidian note banao:
URL: ${url}

Output format:
---
title: (article ka title)
source: ${url}
tags: [literature, (2-3 topic tags)]
clipped: ${new Date().toISOString().slice(0, 10)}
---

# (article ka title)

## TL;DR
(3 lines mein summary)

## Key Points
- (5 mukhya points)

## My Take
_baad mein add karunga_

## Related
[[existing Vault mein related notes (andaaza theek hai)]]
`,
  }],
});

const body = res.content[0].text;
const slug = body.match(/title: "(.+?)"/)?.[1]?.replace(/[\/:]/g, "-") ?? "untitled";
writeFileSync(`${process.env.VAULT}/literature/${slug}.md`, body);
console.log(`Clipped to literature/${slug}.md`);

Istemaal: node clip-url.mjs https://example.com/article

Browser ke right-click menu se bhejne ka setup kar do, to ek right-click mein koi bhi article Vault mein save - baad mein search yogya workflow taiyaar.

Udaharan 3: Automatic backlink completion

Obsidian [[Note naam]] likhne par backlinks banata hai, par “yeh note us concept se clearly related hai aur link karna bhool gaya” bahut hota hai. Claude Code se thok mein theek.

claude -p "
$VAULT/zettel/ ke sabhi Markdown padho aur yeh karo:

1. Har note ke body se 'mahatvapoorn concepts, vyakti, theories' nikalo
2. Check karo ki vah concept kisi doosri note ke title ke roop mein maujood hai ya nahin
3. Unlinked occurrences ko [[...]] se wrap karo
4. Agar '## Related' heading nahi hai to jod do, aur
   2-3 related notes list karo jo body mein naturally nahi aatin

Apply karne se pehle diff dikhao aur approval mango.
"

Mukhya baat: approval flow mat chhodna. Automatic backlink insertion kaam ki cheez hai, par galat links Vault ki credibility kha jaate hain. “Apply se pehle diff dekhna” pakka niyam hai.

Udaharan 4: Meeting minutes ko notes + tagging

Voice transcription ya raw meeting text ko structured notes mein badalna.

claude -p "
$VAULT/inbox/raw-meeting-2026-04-16.txt padho aur is structure ke saath
$VAULT/literature/meeting-2026-04-16.md mein save karo:

---
title: '(meeting title ka andaaza)'
date: 2026-04-16
type: meeting
tags: [meeting, (topic se inferred tags)]
attendees: [(nikale gaye participants)]
---

## Nirnay
## Action Items (zimmedaar aur deadline sahit)
## Charcha (topic-wise organized)
## Agli baar tak ke kaam

Ant mein vyakti ke ullekh ko [[Vyakti naam]] se link karo.
Hone par inbox/raw-meeting-2026-04-16.txt ko _archive/ mein bhej do.
"

Raw text inbox mein daal do, baad mein batch mein convert ho jaata hai.

Udaharan 5: Claude Code se Obsidian plugin development

Obsidian plugins TypeScript mein likhe jaate hain. Claude Code TS mein bahut accha hai, compatibility behtareen hai.

cd ~/my-obsidian-plugin
claude

# Claude Code ke andar:
> main.ts padhkar 3 lines mein batao ki yeh plugin kya karta hai
> Naya feature jodo: "select kiye text ko Claude API se summarize karke cursor par paste karo"
> manifest.json ko compatible version par update karo
> npm run build pass ho raha hai confirm karo

Minute mein chalta plugin taiyaar. Obsidian plugin sample repo git clone kar do, Claude Code usi par extend karta jaayega.

Obsidian-specific notation ke saath kaam

Claude Code ko pata honi chahiye Obsidian ki specific notations:

Notation	Arth	Udaharan
[[Note naam]]	Wikilink (internal link)	[[Claude Code]]
[[Note#heading]]	Specific heading par link	[[FAQ#Price]]
[[Note|alias]]	Alias ke saath link	[[Claude Code|CC]]
![[Note]]	Poori note embed	![[Quotes]]
%%comment%%	Publish view mein chhupi	%%TODO: sudharna hai%%

Inhe CLAUDE.md mein likh do, Claude Code inka sahi use karega.

5 savdhaniyan

1. Sync conflicts (Obsidian Sync / iCloud / Dropbox) Jab Claude Code files likh raha ho aur mobile se sync chale, conflicts hote hain. Claude Code chalate waqt sync pause karna surakshit hai. Scripts ke shuru mein “Obsidian Sync pause” command daalna bhi ek tareeka hai.

2. Filename mein invalid characters Titles mein colon : ya slash / ho to OS-level par file create fail hoti hai. Claude Code ko generate karate waqt saaf likho: “filename sirf akshar, ankh, hyphen aur bhaasha ke characters”.

3. Bulk backlink rewrites Rename automate karne se backlinks update nahin hote aur links toot jaate hain. Rename Obsidian UI se, sirf file move Claude Code ko do.

4. Plugin-dependent likhai Claude Code agar Dataview ya Templater syntax banata hai, to unke bina wale environments mein toot jaata hai. Standard Markdown + Wikilinks tak seemit CLAUDE.md mein likh do.

5. Bade Vaults par ek saath execution 5000 notes wale Vault mein Glob **/*.md + full read chala do to context fat jaayega. Sub-agents ko “sirf zettel/” jaise scope delegate karo.

Workflow udaharan: ek din ka prawaah

Mera khud ka istemaal:

07:00  daily-note.sh auto start, aaj ki note ban jaati hai
09:00  Obsidian khola, Today section bharna
12:00  Aacha web article mila to clip-url.mjs se save
15:00  Meeting, transcript inbox/ mein
17:00  claude chala kar literature/ mein format
22:00  Din ki sikh ko zettel/ mein sthaayi note
Raat   Haftawaari backlink-suggest.sh chala kar backlinks complete

“Likhna” mera kaam, “arrange karna” Claude Code ka - yeh batwara perfect fit hai. Aap soch aur ideation par focus, organize aur connect ka boj AI par. Yahi Obsidian x Claude Code ki asli taakat hai.

Nishkarsh

Obsidian Vault ko aksar “bagiche” se tulna karte hain. Claude Code ko bagwaan-robot rakh lo, to paani dena (daily notes) / ghaas saaf karna (backlinks) / phal katna (summaries) sab automate.

Aaj ke pehle kadam:

1. Vault ki root mein CLAUDE.md rakh kar rules likho
2. daily-note.sh register karke morning notes automate
3. clip-url.mjs install karke web articles one-shot clip

Bas yeh teen - aur Vault ke saath aapka rishta jad se badal jaayega.

Sambandhit lekh

• Harness Engineering poorna guide
• Claude Code ke 10 sub-agent patterns
• CLAUDE.md Best Practices

Sandarbh

• Obsidian official documentation
• Obsidian plugin development guide
• Claude Code official guide