Claude Studio

Notion-style AI inside Obsidian, powered by your local Claude Code CLI. It uses the CLI's logged-in session (your Claude plan), so there is no API key to configure. The vault's CLAUDE.md shapes every answer, because the CLI runs with the vault as its working directory.

Desktop only. It needs the Claude Code CLI installed and logged in.

Interface languages: English, 简体中文, 日本語, 한국어, Español, Deutsch, Français, Português (Brasil), Русский and Italiano, following Obsidian's language setting. A translation that reads wrong? Open an issue with the text and what it should say.

What it does

Actions and profiles are notes

On first run the plugin creates Templates/AI/ (configurable):

• Actions/*.md: one action per note. The frontmatter sets scope, output, model, tools, icon, group, bubble and index, and the body is the prompt. Available variables are {{selection}}, {{cursor}}, {{note}}, {{title}}, {{path}}, {{tags}}, {{hub}}, {{snap}}, {{today}} and {{input}}. Any context the prompt doesn't use is attached at the end.
• Profiles/*.md: extra instructions picked by the active note's match_tags, match_folders and match_categories. A profile with no rules is the fallback.
• Cómo funciona.md: the full reference.

Edits reload instantly, and every action also becomes a command you can bind to a hotkey.

Privacy

Never send these notes (paths, names, folders) and never send notes with these tags are enforced twice:

1. The plugin never puts those notes into the context it sends.
2. Every CLI call receives them as --settings deny rules for Read/Edit.

The second layer matters for sibling vaults: a vault's own .claude/settings.json only applies when the CLI runs inside that vault. This was tested: without the plugin's rules, a cross-vault search returns a note the deny list names; with them, it doesn't.

For other plugins and scripts

const cs = app.plugins.plugins["claude-studio"].api;
await cs.run("Three title ideas for: " + tp.file.title);   // Templater
await cs.runAction("resumir-nota");
cs.ask("¿Qué tengo pendiente?");

URIs:

• obsidian://claude-studio?do=chat&prompt=…
• obsidian://claude-studio?do=palette
• obsidian://claude-studio?do=usage
• obsidian://claude-studio?do=recap&days=7
• obsidian://claude-studio?do=run&action=Resumir%20nota&file=Notes/X.md

Requirements and disclosures

• Desktop only. The plugin starts the claude command-line program on your computer, which Obsidian on mobile cannot do.
• Install and log in to Claude Code first. Run claude once in a terminal. The plugin looks for it in the usual install locations, or you can set the path in its settings.
• Your notes leave your computer. What you send (the selection, the note around the cursor, linked notes, or what Claude reads while answering in the chat) is processed by Claude through the CLI, under the terms of your own Claude plan. The plugin has no server of its own and no telemetry.
• Cost. Runs use your Claude plan's limits; the history and usage views show what each run took.
• Why it uses Node.js modules, and exactly what for. The plugin's whole job is to run your own claude program, so it needs things Obsidian's API doesn't offer. Each use is listed here:
  • child_process (shell execution): starts the claude command-line program for each run (spawn, no shell except for the Windows claude.cmd shim), asks it for --version when you press Test, looks for it with where claude (Windows) or sh -lc "command -v claude" (macOS/Linux) when you press Detect, and runs taskkill on Windows to stop a run you cancel.
  • fs (direct filesystem access), only for these reads, none of them in your vault: checking that the claude program exists at its usual install paths and, for the Windows .cmd shim, reading that one small file to find the real .exe; and reading Obsidian's own obsidian.json to list your other vaults for the Sibling vaults setting. The plugin never writes outside your vault through fs; vault notes are always read and written through Obsidian's API.
  • Environment and system information (os.homedir(), process.platform and the HOME and APPDATA variables): only to build those install and obsidian.json paths per operating system. Nothing is sent anywhere or used to identify you. The CLI process also receives a copy of your environment (so it finds its own login and PATH), minus ANTHROPIC_API_KEY and ANTHROPIC_AUTH_TOKEN when Use my subscription is on.
• Vault listing. The plugin lists your notes to find the ones that link to the note you're working on, to match project hubs and profiles, to suggest tags, folders and properties, and to find your Actions and Profiles notes. File paths stay on your computer unless a note you chose as context is sent.
• Clipboard. Only when you press a Copy button on an answer; the plugin never reads the clipboard.
• No default hotkey. Open AI palette has no shortcut so it can't clash with yours. Assign one in Settings → Hotkeys (search "Claude Studio"); every action is also a command you can bind.
• Nothing is changed without you. Answers are inserted only after you accept them, whole-note rewrites go through a diff first, and every applied change can be reverted from the History panel.

Installation

In Obsidian, open Settings → Community plugins → Browse and search for "Claude Studio".

Development

npm ci
npm run lint
npm test             # unit tests for the pure helpers (Node ≥ 22.18)
npm run build        # tsc + esbuild → main.js

Code map:

• src/runner.ts: spawns the CLI (stream-json, partial messages, stdin prompt) and resolves the npm .cmd shim to the native exe
• src/core.ts: exclusions and deny rules, model aliases, status
• src/context.ts: chips and prompt assembly
• src/library.ts: actions and profiles
• src/actions.ts: output routing
• src/editor/*: CodeMirror card, ghost text and bubble
• src/ui/*: palette, chat, history, usage limits, diff and result modal
• src/usage.ts: last usage-limit snapshot from the CLI (rate_limit_event), saved to usage.json
• src/icon.ts: the plugin's own burst icon
• src/features.ts: vault tools
• src/integrations.ts: clippings, API and URI

More plugins by Siulved54

All of them are in the community directory: Settings -> Community plugins -> Browse, then search for the name.