obsidian-looper

obsidian-looper

Orchestrate Claude Code at scale, with Obsidian as the shared brain.

obsidian-looper is a Claude Code skill that turns your Obsidian vault into a live control plane for a fleet of AI sub-agents. You drop work into Inbox.md, approve plans with a click, and the orchestrator handles the rest — scouting your codebase, drafting RFCs, dispatching parallel implementer agents, verifying their output, and reporting back — all without you typing another message to Claude.

---

Install as a Claude Code plugin

The recommended way to install obsidian-looper is as a Claude Code plugin — no cloning or copying required.

1. Add this repo as a marketplace

claude plugin marketplace add PandelisZ/obsidian-looper

This registers the repo as a local plugin marketplace (stored in your user config).

2. Install the plugin

claude plugin install obsidian-looper@obsidian-looper

Claude Code fetches the plugin, validates it, and makes the obsidian-looper skill available in every session. Restart Claude Code (or run /reload-plugins) to activate it.

3. Configure your project

After installation, follow the Quickstart from step 3 (Configure) onward — wire up project.config.js and set up Obsidian.

Alternative: manual install via install.sh

If you prefer to copy the skill directly into your project (e.g. to pin a specific version or modify it):

git clone https://github.com/PandelisZ/obsidian-looper ~/tools/obsidian-looper
cd ~/tools/obsidian-looper
./install.sh /path/to/your-project

---

The idea

Most "agentic" workflows still require you to babysit Claude turn-by-turn. obsidian-looper flips this: Claude runs a continuous loop against your Obsidian vault, and you steer by editing notes.

The key insight is that Obsidian's frontmatter status property — displayed as a chip-picker — becomes a signalling protocol. You set status: [approved] on a Plan, and on the next tick the orchestrator dispatches a fleet of sub-agents to execute it. You set status: [changes-requested] and write a comment under ## Review, and the orchestrator picks it up, revises the draft, and flips it back to needs-review. You never need to re-open a terminal or say anything to Claude.

Meanwhile, Claude is running as an Opus conductor — it never does the leaf work itself. Every grep, file read, implementation, and test run goes to a specialized sub-Claude (Haiku for lookup, Sonnet for implementation, nested Opus for complex sub-orchestration). The conductor's only jobs are: keep Obsidian accurate, dispatch the fleet, and synthesize results.

---

Concepts

The Obsidian brain

Your vault hosts a dedicated folder (e.g. My Project Giga/) that the orchestrator reads and writes via the mcp-obsidian MCP server and the Obsidian Local REST API plugin. Changes appear in your vault in real time.

The folder contains:

• Inbox.md — your asks, as - [ ] checkboxes. The orchestrator drains this each tick.
• RFCs/ — design decisions and proposals. Claude drafts them; you approve or request changes.
• Plans/ — scoped execution plans linked to an RFC. Approving a Plan triggers execution.
• Status/ — dated heartbeat notes. One per day, updated each loop tick.
• Roadmap.md — rolling priorities the orchestrator uses to triage inbox items.

The status-frontmatter review loop

Every RFC and Plan has a status frontmatter property. Because it's typed as an Obsidian List, it renders as a chip-picker — no markdown editing required.

The flow:

draft → needs-review → approved | changes-requested → in-progress → done

• Claude writes draft, flips to needs-review when ready.
• You never get pinged — just open Obsidian when you want to review.
• You click the chip. If approved, Claude executes on the next tick. If changes-requested, you write a comment under ## Review and Claude revises.

The continuous /loop

Start the orchestrator with:

/loop /obsidian-looper run the continuous loop

Every tick (self-paced, faster when busy, slower when idle):

1. Monitor the fleet — check in-flight agents, persist results to Obsidian.
2. Advance approved work — dispatch implementing agents for approved Plans.
3. Drain the inbox — scout, classify, and draft RFCs/Plans from open Inbox items.
4. Write the heartbeat — update today's Status/ note with the current picture.