Qlaude

pending

by Ziad Kadry

Run Claude Code CLI from within your vault to read and write your notes.

Updated 1mo agoMITDiscovered via Obsidian Unofficial Plugins
View on GitHub

Qlaude Logo

Qlaude

Claude Code, inside Obsidian.

Latest release Desktop only License


Qlaude is an Obsidian plugin that brings the full power of the Claude Code CLI into your vault. Open a modal with a keyboard shortcut, type a natural-language instruction, and watch Claude read, edit, and create notes in real time — all streamed live as it works.

Features

  • Quick action mode — one-shot prompt with live streaming output; textarea locks when done
  • Chat mode — multi-turn conversation with persistent history across modal opens and Obsidian sessions; resumable via --resume
  • Markdown rendering — Claude's output renders with proper headings, lists, bold, code blocks, and more
  • Animated loading indicator — bouncing dots show when Claude is working
  • Model selection — type any Claude model ID (e.g. claude-haiku-4-5, claude-sonnet-4-6, claude-opus-4-6)
  • Granular permissions — independently control read, list, edit, and create access
  • Wikilink-aware — Claude understands [[wikilinks]], YAML frontmatter, and Obsidian conventions

Demo

Open the modal with Cmd+Shift+C, type your instruction, and press Ctrl+Enter to run.

Requirements

  • Obsidian 1.4.0 or later (desktop only)
  • Claude Code CLI installed and authenticated — install guide
    • Verify with: claude --version

Installation

From Obsidian (once listed in community plugins)

  1. Open Settings → Community plugins → Browse
  2. Search for Qlaude
  3. Click Install, then Enable

Manual installation

  1. Download main.js, manifest.json, and styles.css from the latest release
  2. Copy them to <vault>/.obsidian/plugins/qlaude/
  3. In Obsidian: Settings → Community plugins → Enable Qlaude

Usage

Quick action

  1. Open any note and press Cmd+Shift+C
  2. Make sure the Quick action tab is selected
  3. Type your instruction, e.g.:
    • "Summarise this note in three bullet points and add them at the top"
    • "Convert all plain list items to checkboxes"
  4. Press Ctrl+Enter (or Cmd+Enter) to run

Claude streams its response live with markdown rendering. The textarea locks when done to make the output easy to read.

Chat

  1. Open the modal and click the Chat tab
  2. Type a message and press Ctrl+Enter to send
  3. Claude responds in a conversation thread — your messages appear as bubbles on the right, Claude's replies render below
  4. Send follow-up messages freely; Claude remembers the full context of the conversation
  5. Click Clear to start a fresh conversation

Chat history and the session ID persist between modal opens and Obsidian restarts until you click Clear.

Configuration

Go to Settings → Qlaude to configure:

SettingDefaultDescription
Claude binary pathclaudeFull path to the claude binary if not on Obsidian's PATH
Modelclaude-haiku-4-5Any model ID supported by the CLI (e.g. claude-sonnet-4-6, claude-opus-4-6)
Clear chat on startOffWipe chat history and session automatically when Obsidian launches

Permissions

Qlaude uses Claude Code's --allowedTools flag to enforce tool-level permissions at the CLI — Claude cannot use a tool that isn't explicitly enabled regardless of what it's asked to do. Read access is further restricted via the system prompt.

By default Claude can only read the currently active file. Enable permissions progressively as needed:

PermissionDefaultWhat it enables
Read entire vaultOffRead any file in the vault
List vault structureOffGlob, Grep, LS — search and list files
Edit current fileOffEdit — modify the currently active file only
Edit any fileOffEdit, Write — modify any file in the vault
Create filesOffWrite — create new files

Building from source

git clone https://github.com/ziadkadry99/Qlaude
cd Qlaude
npm install
npm run build   # produces main.js

License

MIT — see LICENSE

For plugin developers

Search results and similarity scores are powered by semantic analysis of your plugin's README. If your plugin isn't appearing for searches you'd expect, try updating your README to clearly describe your plugin's purpose, features, and use cases.