Free and open-source AI assistant for Obsidian with Chat, Workflow Automation, and Semantic Search (RAG). Supports multiple LLM providers — use whichever AI fits your needs.

Use any LLM provider: Gemini, OpenAI, Anthropic, OpenRouter, Grok, OpenCode Zen / Go, local LLMs (Ollama, LM Studio, vLLM, OpenCode), or CLI tools (Antigravity CLI, Claude Code, Codex CLI).

Highlights

• Multi-Provider LLM Chat - Use Gemini, OpenAI, Anthropic, OpenRouter, Grok, OpenCode Zen/Go, local LLMs, or CLI backends
• Vault Operations - AI reads, writes, searches, and edits your notes with function calling (Gemini, OpenAI, Anthropic, OpenCode Zen/Go, and tools-capable local LLMs via LM Studio / vLLM / AnythingLLM)
• Workflow Builder - Automate multi-step tasks with visual node editor and 25 node types
• Dashboard Hub Integration - Supply AI models, Chat, Base generation, and Workflow execution to the separate Dashboard Hub plugin
• Semantic Search (RAG) - Local vector search with dedicated search tab, PDF preview, and result-to-chat flow
• Discussion Hub Integration - Supply API, CLI, and local models to the separate multi-provider Discussion Hub plugin
• Edit History - Track and restore AI-made changes with diff view
• Web Search - Access up-to-date information with cited sources via Gemini and the official OpenAI, Anthropic, or xAI APIs
• Image Generation - Create images with Gemini or DALL-E
• Discord Integration - Connect your LLM to Discord as a chat bot with per-channel model/RAG switching
• Encryption - Password-protect chat history and workflow execution logs

Supported Providers

Web Search appears for Gemini providers and for OpenAI, Anthropic, or Grok providers using their official API hosts. Open the search menu and check Web search before sending the prompt; asking the model to browse does not enable the tool by itself. Web Search and one Semantic Search (RAG) setting can be enabled together so the model can synthesize current web information with retrieved vault context. The model decides whether a web search is needed. Search answers include inline citation links and a compact cited-source list; custom and OpenAI-compatible gateways are not assumed to support the providers' native search tools.

[!TIP] Multiple providers can be configured simultaneously. Switch models freely during chat — each provider has its own API key and settings.

[!TIP] CLI Options let you use flagship models with just an account - no API key needed!

• Antigravity CLI: Install Antigravity CLI, run agy and authenticate
• Claude CLI: Install Claude Code (npm install -g @anthropic-ai/claude-code), run claude and authenticate
• Codex CLI: Install Codex CLI (npm install -g @openai/codex), run codex and authenticate

Gemini Free API Key Tips

• Rate limits are per-model and reset daily. Switch models to continue working.
• Gemma 4 cannot combine function calling with RAG/Web Search in a single request. When RAG or Web Search is active, vault tools are automatically disabled. CLI models, Ollama, and the OpenCode local server don't support vault tools (use Workflows with note, note-read, etc., or {content} / {selection} variables). LM Studio / vLLM / AnythingLLM local LLMs DO support vault tools when the underlying model supports OpenAI-style function calling — incompatible models are auto-detected on first use and downgraded to marker-based skill mode.

AI Chat

The AI Chat feature provides an interactive conversation interface with your chosen LLM provider, integrated with your Obsidian vault.

Opening Chat:

• Click chat icon in ribbon
• Command: "LLM Hub: Open chat"
• Toggle: "LLM Hub: Toggle chat / editor"

Chat Controls:

• Enter - Send message
• Shift+Enter - New line
• Stop button - Stop generation
• + button - New chat
• History button - Load previous chats
• ↑ / ↓ in the input - Recall up to 100 sent prompts across chats and Obsidian restarts. Up recalls history only from the first line and Down advances only from the last line, preserving normal multiline cursor movement. Advancing past the newest entry restores the unsent draft.

Web Search

Choose a supported API model, then open the search menu beside the model picker and check Web search. You may also select one Semantic Search setting in the same menu; when both are active, matching vault context is injected before the provider receives the prompt with its native web-search tool enabled. Prompt wording alone does not turn search on. Search remains model-controlled: enabling the tool allows the model to search, but does not force a search for every prompt.

The Web and RAG choices are saved per workspace. Switching to a model that cannot use one of them leaves the preference visibly selected but inactive, and it automatically becomes active again when you return to a compatible model. Use a combined RAG setting when several indexes should be searched together.

• Gemini: supported through Google Search grounding.
• OpenAI: supported only through api.openai.com; search uses the Responses API and can run alongside vault and MCP function tools. OpenAI image-generation models are excluded.
• Anthropic: supported only through api.anthropic.com; native server search can run alongside vault and MCP client tools.
• Grok: supported only through api.x.ai; search uses xAI's Responses API and can run alongside vault and MCP function tools. Grok image/video-generation models are excluded.
• Other endpoints: OpenRouter, custom gateways, local LLMs, and CLI providers are not treated as native-search providers even if they offer OpenAI-compatible chat APIs.

The implementation intentionally has no chat-model allowlist. Compatible current or future models may use search, while an unsupported model returns the provider's actionable error. Live compatibility checks during development covered OpenAI GPT-5.6 Sol and Anthropic Claude Opus 4.8, Sonnet 5, Fable 5, and Haiku 4.5; automated Responses-stream coverage includes Grok 4.5.

Only cited sources are displayed. Provider citation positions become numbered Markdown links, while xAI's native inline Markdown citations are preserved; deduplicated sources appear as clickable pills beneath the Used web search badge. Search source metadata and provider-native continuation items are saved with chat history so later turns can retain search context when the endpoint, model, and retained message pair still match. Usage estimates add the current $0.01 OpenAI/Anthropic search fee per request; xAI responses use the provider's exact billed cost (currently $0.005 per web-search invocation), including token and tool charges.

Slash Commands

Create reusable prompt templates triggered by /:

• Define templates with {selection} (selected text) and {content} (active note)
• Optional model and search override per command
• Type / to see available commands

Default: /infographic - Converts content to HTML infographic

@ Mentions

Reference files and variables by typing @:

• {selection} - Selected text
• {content} - Active note content
• Any vault file - Browse and insert (path only; AI reads content via tools)

[!NOTE] How {selection} and {content} work: When you switch from Markdown View to Chat View, the selection would normally be cleared due to focus change. To preserve your selection, the plugin captures it when switching views and highlights the selected area with a background color in the Markdown View. The {selection} option only appears in @ suggestions when text was selected.

Both {selection} and {content} are intentionally not expanded in the input area—since the chat input is compact, expanding long text would make typing difficult. The content is expanded when you send the message, which you can verify by checking your sent message in the chat.

[!NOTE] Vault file @mentions insert only the file path - the AI reads content via tools. This does not work with CLI models or marker-only Local LLM frameworks such as Ollama/OpenCode. Tools-capable Local LLM frameworks such as LM Studio, vLLM, and AnythingLLM can read the file via vault tools when the loaded model supports function calling. Antigravity CLI can read files via shell, but response format may differ.

File Attachments

Attach files directly: Images (PNG, JPEG, GIF, WebP), PDFs, Text files

Function Calling (Vault Operations)

The AI can interact with your vault using these tools:

Vault Tool Mode

When the AI handles notes in Chat, it uses Vault tools. Control which vault tools the AI can use via the Database icon (📦) below the attachment button:

The same Database icon menu also has Previous messages (0-99). This controls how many messages before the current prompt are sent to the model as conversation context. Set it to 0 to send only the current prompt, such as when processing unrelated files one at a time. The value is saved for the workspace.

When to use each mode:

• Vault: All - Default mode for general use. The AI can read, write, and search your vault.
• Vault: No search - Use when you already know the target file. This avoids redundant vault searches, saving tokens and improving response time.
• Vault: Off - Use when you don't need vault access at all.

Automatic mode selection:

Why some modes are forced:

• CLI models, Ollama, OpenCode (Local): These do not expose OpenAI-style function calling, so Vault tools cannot be used. LM Studio / vLLM / AnythingLLM local LLMs CAN use Vault tools when the loaded model supports tool calling; if a model rejects the first tools request, it is auto-flagged and falls back to marker mode for subsequent turns (clear the flag in Settings → Local LLM → Re-enable tools).
• Gemma 4: Function calling and RAG/Web Search cannot be combined in a single request. When one is active, the other is automatically disabled.

LLM vault tool folders:

In Settings → Workspace → LLM vault tool folders, you can limit which vault folders LLM-driven vault tools may access. This applies to API providers and tools-capable Local LLMs, including LLM-triggered skill workflows. Leave the list empty to allow the whole vault. CLI models are not restricted by this setting because they do not use these vault tools.

Safe Editing

When AI uses propose_edit:

1. A confirmation dialog shows the proposed changes
2. Click Apply to write changes to the file
3. Click Discard to cancel without modifying the file

Changes are NOT written until you confirm.

Edit History

Track and restore changes made to your notes:

• Automatic tracking - All AI edits (chat, workflow) and manual changes are recorded

• File menu access - Right-click on a markdown file to access:

  • Snapshot - Save current state as a snapshot
  • History - Open edit history modal

• Command palette - Also available via "Show edit history" command

• Diff view - See exactly what changed with color-coded additions/deletions

• Restore - Revert to any previous version with one click

• Copy - Save a historical version as a new file (default name: {filename}_{datetime}.md)

• Resizable modal - Drag to move, resize from corners

Diff display:

• + lines existed in the older version
• - lines were added in the newer version

How it works:

Edit history uses a snapshot-based approach:

1. Snapshot creation - When a file is first opened or modified by AI, a snapshot of its content is saved
2. Diff recording - When the file is modified, the difference between the new content and the snapshot is recorded as a history entry
3. Snapshot update - The snapshot is updated to the new content after each modification
4. Restore - To restore to a previous version, diffs are applied in reverse from the snapshot

When history is recorded:

• AI chat edits (propose_edit tool)
• Workflow note modifications (note node)
• Manual saves via command
• Auto-detection when file differs from snapshot on open

Storage: Edit history is stored in memory and cleared on Obsidian restart. Obsidian's built-in file recovery covers persistent version tracking.

MCP Servers

MCP (Model Context Protocol) servers provide additional tools that extend the AI's capabilities beyond vault operations.

Two transport modes are supported:

HTTP (Streamable HTTP):

1. Open plugin settings → MCP Servers section
2. Click Add server → select HTTP
3. Enter server name and URL
4. Configure optional headers (JSON format) for authentication
5. Click Test connection to verify and retrieve available tools
6. Save the server configuration

Stdio (Local process):

1. Open plugin settings → MCP Servers section
2. Click Add server → select Stdio
3. Enter server name and command (e.g., npx -y @modelcontextprotocol/server-filesystem /path/to/dir)
4. Configure optional environment variables (JSON format)
5. Click Test connection to verify and retrieve available tools
6. Save the server configuration

Note: Stdio transport launches a local process and is desktop-only. Test connection is required before saving.

Using MCP tools:

• In Chat: Click the Database icon (📦) to open tool settings. Enable/disable MCP servers per conversation.
• In Workflows: Use the mcp node to call MCP server tools.

Tool hints: After successful connection test, available tool names are saved and displayed in both settings and chat UI for easy reference.

MCP Apps (Interactive UI)

Some MCP tools return interactive UI that allows you to interact with the tool results visually. This feature is based on the MCP Apps specification.

How it works:

• When an MCP tool returns a ui:// resource URI in its response metadata, the plugin fetches and renders the HTML content
• The UI is displayed in a sandboxed iframe for security (sandbox="allow-scripts allow-forms")
• Interactive apps can call additional MCP tools and update context through a JSON-RPC bridge

In Chat:

• MCP Apps appear inline in assistant messages with an expand/collapse button
• Click ⊕ to expand the app to full screen, ⊖ to collapse

In Workflows:

• MCP Apps are displayed in a modal dialog during workflow execution
• The workflow pauses to allow user interaction, then continues when the modal is closed

Security: All MCP App content runs in a sandboxed iframe with restricted permissions. The iframe cannot access the parent page's DOM, cookies, or local storage. Only allow-scripts and allow-forms are enabled.

Agent Skills

Extend the AI with custom instructions, reference materials, and executable workflows. Skills follow the industry-standard agent skills pattern (e.g., OpenAI Codex .codex/skills/).

• Built-in skills - Obsidian-specific knowledge (Markdown, Canvas, Bases) included out of the box. Based on kepano/obsidian-skills
• Custom instructions - Define domain-specific behavior via SKILL.md files
• Reference materials - Include style guides, templates, and checklists in references/
• Workflow integration - Skills can expose workflows as function calling tools
• Script execution - Skills can expose scripts (.sh, .py, .js, .ts, .rb) as function calling tools (desktop only)
• Slash command - Type /folder-name to instantly invoke a skill and send
• CLI mode support - Skills work with Antigravity CLI, Claude CLI, and Codex CLI backends
• Selective activation - Choose which skills are active per conversation

Create skills the same way as workflows — select + New (AI), check "Create as agent skill", and describe what you want. The AI generates both the SKILL.md instructions and the workflow.

For setup instructions and examples, see Agent Skills

Discord Integration

Connect your Obsidian vault's LLM to Discord as a chat bot. Users can chat with the AI, switch models, use RAG search, and activate slash commands — all from Discord.

Setup

1. Create a Discord Bot

1. Go to the Discord Developer Portal
2. Click New Application → enter a name → Create
3. Go to Bot in the left sidebar
4. Click Reset Token → copy the bot token (you'll need this later)
5. Under Privileged Gateway Intents, enable Message Content Intent (required to read message text)

2. Invite the Bot to Your Server

1. Go to OAuth2 in the left sidebar
2. Under OAuth2 URL Generator, select the bot scope
3. Under Bot Permissions, select:
   • Send Messages
   • Read Message History
4. Copy the generated URL and open it in your browser
5. Select a server and authorize the bot

3. Configure in Obsidian

1. Open plugin settings → Discord section
2. Enable Discord Bot
3. Paste the bot token
4. Click Connect (the plugin verifies the token before connecting)
5. The status indicator shows whether the bot is connected

Configuration Options

[!TIP] Finding Channel/User IDs: In Discord, enable Developer Mode (Settings → Advanced → Developer Mode). Then right-click a channel or user and select Copy ID.

Bot Commands

Users can interact with the bot using these commands in Discord:

Features

• Multi-provider support — Works with all configured LLM providers (Gemini, OpenAI, Anthropic, OpenRouter, Grok, CLI, Local LLM)
• Per-channel state — Each Discord channel maintains its own conversation history, model selection, and RAG setting
• Vault tools — AI can read, write, and search notes based on your plugin settings, including the Workspace LLM vault tool folder limit
• RAG integration — Semantic search can be enabled per channel via !rag command
• Slash commands — Activate plugin slash commands via !skill
• Deep Research — Run Gemini Deep Research via !research command. Runs in the background so you can continue chatting while it works. Results are posted to the channel when complete (requires Gemini API key)
• Long message splitting — Responses exceeding Discord's 2000-char limit are automatically split at natural break points
• Conversation memory — Per-channel history (max 20 messages, 30-minute TTL)
• Auto-reconnect — Recovers from connection drops with exponential backoff

[!NOTE] Conversation history is kept in memory only and is cleared when the bot disconnects or Obsidian restarts.

Workflow Builder

Build automated multi-step workflows directly in Markdown files. No programming knowledge required - just describe what you want in natural language, and the AI will create the workflow for you.

AI-Powered Workflow & Skill Creation

You don't need to learn YAML syntax or node types. Simply describe your workflow in plain language:

1. Open the Workflow tab in the plugin sidebar
2. Select + New (AI) from the dropdown
3. Describe what you want: "Create a workflow that summarizes the selected note and saves it to a summaries folder"
4. Check "Create as agent skill" if you want to create an agent skill instead of a standalone workflow
5. Click Generate - the AI creates the complete workflow

Modify existing workflows the same way:

1. Load any workflow
2. Click the AI Modify button
3. Describe changes: "Add a step to translate the summary to Japanese"
4. Review and apply

Available Node Types

25 node types are available for building workflows:

For detailed node specifications and examples, see Workflow Nodes

Hotkey Mode

Assign keyboard shortcuts to run workflows instantly:

1. Open the workflow file (the filename becomes the hotkey's display name)
2. Click the keyboard icon (⌨️) in the Workflow panel footer
3. Go to Settings → Hotkeys → search "Workflow: [filename]"
4. Assign a hotkey (e.g., Ctrl+Shift+T)

When triggered by hotkey:

• prompt-file uses the active file automatically (no dialog)
• prompt-selection uses the current selection, or full file content if no selection

Event Triggers

Workflows can be automatically triggered by Obsidian events:

Event trigger setup:

1. Open the workflow file (the filename is used as the trigger's display name)
2. Click the zap icon (⚡) in the Workflow panel footer
3. Select which events should trigger the workflow
4. Optionally add a file pattern filter

File pattern examples:

• **/*.md - All Markdown files in any folder
• journal/*.md - Markdown files in journal folder only
• *.md - Markdown files in root folder only
• **/{daily,weekly}/*.md - Files in daily or weekly folders
• projects/[a-z]*.md - Files starting with lowercase letter

Event variables: When triggered by an event, these variables are set automatically:

Note: prompt-file and prompt-selection nodes automatically use the event file when triggered by events. prompt-selection uses the entire file content as the selection.

Dashboard Hub Integration

Dashboard functionality is provided by the separate Dashboard Hub plugin. When both plugins are enabled, LLM Hub supplies Dashboard Hub with its configured AI models, Chat handoff, Base generation, text rewriting, and Workflow generation/execution. Dashboard Hub also contributes its dashboard Agent Skill to LLM Hub at runtime.

See the Dashboard Hub documentation for dashboard features, widgets, storage, and schema details.

Discussion Hub Integration

AI Discussion is provided by the separate Discussion Hub plugin. When both plugins are enabled, LLM Hub supplies Discussion Hub with its configured API, CLI, and local text models. Models contributed by Gemini Helper and Local LLM Hub can participate in the same discussion.

See the Discussion Hub documentation for discussion features, configuration, and usage details.

Common

Supported Models

Gemini

Thinking mode: Use the Always Think toggles for supported chat models. Gemini 3.1 Pro always uses thinking mode and does not support disabling it.

Always Think toggle:

Click the Database icon (📦) to open the tool menu, and check the toggles under Always Think:

• Flash — OFF by default. Check to always enable thinking for Flash models.
• Flash Lite — ON by default. Flash Lite has minimal cost and speed difference with thinking enabled, so it is recommended to keep this on.

When a toggle is ON, thinking is always active for that model family regardless of message content. When OFF, the existing keyword-based detection is used.

OpenAI

Anthropic

OpenRouter / Grok / Custom

Configure any OpenAI-compatible endpoint with custom base URL and models. OpenRouter provides access to hundreds of models from various providers.

OpenCode Zen / Go

OpenCode offers two hosted gateways from the same account, both selectable from the provider dropdown:

• OpenCode Zen (https://opencode.ai/zen) — pay-per-use, includes several free models (Big Pickle, MiniMax M2.5 Free, etc.) and a broad model catalog (Claude, GPT-5.x, and more). Exposes OpenAI-compatible /v1/models + /v1/chat/completions, so models are listed automatically.
• OpenCode Go (https://opencode.ai/zen/go) — $5/first month, $10/month subscription with curated coding models (Grok, GLM, Kimi, DeepSeek, MiMo, MiniMax, Qwen, and more). The plugin fetches its live /v1/models catalog during Verify, so newly added and retired models are reflected automatically.

Local LLM

Connect to locally running models via Ollama, LM Studio, vLLM, AnythingLLM, or the OpenCode local server. Models are auto-detected from the running server.

Installation

Community Plugins (Recommended)

1. Open Settings → Community plugins in Obsidian
2. Select Browse and search for LLM Hub
3. Select Install, then Enable

Manual

1. Download main.js, manifest.json, styles.css from releases
2. Create llm-hub folder in .obsidian/plugins/
3. Copy files and enable in Obsidian settings

From Source

git clone https://github.com/takeshy/obsidian-llm-hub
cd obsidian-llm-hub
npm install
npm run build

Configuration

API Providers

Add one or more API providers in plugin settings. Each provider has its own API key and model selection.

You can also add custom OpenAI-compatible endpoints.

Proxy

Route all API requests through an HTTP CONNECT proxy for corporate gateway environments. See Proxy Settings for details.

Local LLM

Connect to locally running LLM servers:

1. Start your local server (Ollama, LM Studio, vLLM, AnythingLLM, or OpenCode)
2. Enter the server URL in plugin settings
3. Click "Verify" to detect available models

[!NOTE] LM Studio / vLLM / AnythingLLM local LLMs use OpenAI-style function calling for vault tools — enabled by default for tools-capable models. If a model rejects the first tools request it is auto-flagged and downgraded to marker-based skill mode for subsequent turns; clear the flag in Settings → Local LLM → Re-enable tools to retry.

These tools follow Settings → Workspace → LLM vault tool folders, the same folder limit used for API providers and LLM-triggered skill workflows.

Ollama and OpenCode (Local) still use marker mode only. Use workflows or RAG for note operations with those frameworks.

OpenCode Local Server

The OpenCode framework connects to a local opencode serve instance, which exposes its own HTTP API instead of the OpenAI-compatible /v1/chat/completions shape. Streaming uses the server's /global/event SSE endpoint.

macOS / Linux

1. Install the OpenCode CLI:

   curl -fsSL https://opencode.ai/install | bash
   

2. Start the server:

   opencode serve
   

   It listens on http://localhost:4096 by default.
3. In plugin settings → Local LLM, select OpenCode (Local), keep the default URL (http://localhost:4096), and click Fetch models.
4. Models are listed as <providerID>/<modelID> (e.g. google/gemini-flash-lite-latest). Pick one and save.

Windows (WSL)

OpenCode recommends WSL on Windows for file-system performance and tool compatibility. Since Obsidian runs on the Windows host, the server must be bound to a reachable interface and — because it becomes accessible from outside WSL — protected with a password.

1. Install WSL (Microsoft's official guide) and open a WSL terminal.

2. Inside WSL, install OpenCode:

   curl -fsSL https://opencode.ai/install | bash
   

3. Start the server bound to all interfaces, with a password:

   OPENCODE_SERVER_PASSWORD='your-password' opencode serve --hostname 0.0.0.0 --port 4096
   

   WSL2 forwards localhost to the Windows host automatically, so from Obsidian the URL is http://localhost:4096. If that doesn't resolve, run hostname -I in WSL and use http://<wsl-ip>:4096 instead.

4. In plugin settings → Local LLM → OpenCode (Local):

   • Base URL: http://localhost:4096 (or the WSL IP)
   • Username: opencode (default; override with OPENCODE_SERVER_USERNAME if you set one)
   • Password: the value of OPENCODE_SERVER_PASSWORD

   Click Fetch models, pick a <providerID>/<modelID> model, and save.

CLI Mode (Antigravity / Claude / Codex)

Antigravity CLI:

1. Install Antigravity CLI
2. Authenticate with agy
3. Click "Verify" in Antigravity CLI section

Claude CLI:

1. Install Claude Code: npm install -g @anthropic-ai/claude-code
2. Authenticate with claude
3. Click "Verify" in Claude CLI section

Codex CLI:

1. Install Codex CLI: npm install -g @openai/codex
2. Authenticate with codex
3. Click "Verify" in Codex CLI section

CLI Limitations: No vault tool support, no web search, desktop only

TTY terminal: Run “LLM Hub: Open CLI terminal” from the command palette to open an in-Obsidian CLI terminal view. In desktop environments where node-pty and @xterm/xterm are available, the view starts a full TTY session for Antigravity / Claude / Codex with the vault root as the working directory.

[!NOTE] CLI-only usage: You can use CLI mode without any API key. Just install and verify a CLI tool.

Custom CLI Path: If automatic CLI detection fails, click the gear icon (⚙️) next to the Verify button to manually specify the CLI path. The plugin searches common installation paths automatically, including version managers (nodenv, nvm, volta, fnm, asdf, mise).

[!TIP] Claude CLI tip: Chat sessions from LLM Hub are stored locally. You can continue conversations outside of Obsidian by running claude --resume in your vault directory to see and resume past sessions.

Workspace Settings

• Workspace Folder - Chat history and settings location
• System Prompt - Additional AI instructions
• Tool Limits - Control function call limits
• Edit History - Track and restore AI-made changes

Encryption

Password-protect your chat history and workflow execution logs separately.

Setup:

1. Set a password in plugin settings (stored securely using public-key cryptography)

2. After setup, toggle encryption for each log type:
   • Encrypt AI chat history - Encrypt chat conversation files
   • Encrypt workflow execution logs - Encrypt workflow history files

Each setting can be enabled/disabled independently.

Features:

• Separate controls - Choose which logs to encrypt (chat, workflow, or both)
• Automatic encryption - New files are encrypted when saved based on settings
• Password caching - Enter password once per session
• Dedicated viewer - Encrypted files open in a secure editor with preview
• Decrypt option - Remove encryption from individual files when needed

How it works:

[Setup - once when setting password]
Password → Generate key pair (RSA) → Encrypt private key → Store in settings

[Encryption - for each file]
File content → Encrypt with new AES key → Encrypt AES key with public key
→ Save to file: encrypted data + encrypted private key (from settings) + salt

[Decryption]
Password + salt → Restore private key → Decrypt AES key → Decrypt file content

• Key pair is generated once (RSA generation is slow), AES key is generated per file
• Each file stores: encrypted content + encrypted private key (copied from settings) + salt
• Files are self-contained — decryptable with just the password, no plugin dependency

#!/usr/bin/env python3
"""Decrypt LLM Hub encrypted files without the plugin."""
import base64, sys, re, getpass
from cryptography.hazmat.primitives import hashes, serialization
from cryptography.hazmat.primitives.kdf.pbkdf2 import PBKDF2HMAC
from cryptography.hazmat.primitives.ciphers.aead import AESGCM
from cryptography.hazmat.primitives.asymmetric import padding

def decrypt_file(filepath: str, password: str) -> str:
    with open(filepath, 'r') as f:
        content = f.read()

    # Parse YAML frontmatter
    match = re.match(r'^---\n([\s\S]*?)\n---\n([\s\S]*)$', content)
    if not match:
        raise ValueError("Invalid encrypted file format")

    frontmatter, encrypted_data = match.groups()
    key_match = re.search(r'key:\s*(.+)', frontmatter)
    salt_match = re.search(r'salt:\s*(.+)', frontmatter)
    if not key_match or not salt_match:
        raise ValueError("Missing key or salt in frontmatter")

    enc_private_key = base64.b64decode(key_match.group(1).strip())
    salt = base64.b64decode(salt_match.group(1).strip())
    data = base64.b64decode(encrypted_data.strip())

    # Derive key from password
    kdf = PBKDF2HMAC(algorithm=hashes.SHA256(), length=32, salt=salt, iterations=100000)
    derived_key = kdf.derive(password.encode())

    # Decrypt private key
    iv, enc_priv = enc_private_key[:12], enc_private_key[12:]
    private_key_pem = AESGCM(derived_key).decrypt(iv, enc_priv, None)
    private_key = serialization.load_der_private_key(base64.b64decode(private_key_pem), None)

    # Parse encrypted data: key_length(2) + enc_aes_key + iv(12) + enc_content
    key_len = (data[0] << 8) | data[1]
    enc_aes_key = data[2:2+key_len]
    content_iv = data[2+key_len:2+key_len+12]
    enc_content = data[2+key_len+12:]

    # Decrypt AES key with RSA private key
    aes_key = private_key.decrypt(enc_aes_key, padding.OAEP(
        mgf=padding.MGF1(algorithm=hashes.SHA256()), algorithm=hashes.SHA256(), label=None))

    # Decrypt content
    return AESGCM(aes_key).decrypt(content_iv, enc_content, None).decode('utf-8')

if __name__ == "__main__":
    if len(sys.argv) != 2:
        print(f"Usage: {sys.argv[0]} <encrypted_file>")
        sys.exit(1)
    password = getpass.getpass("Password: ")
    print(decrypt_file(sys.argv[1], password))

Warning: If you forget your password, encrypted files cannot be recovered. Keep your password safe.

Tip: To encrypt all files in a directory at once, use a workflow. See the "Encrypt all files in a directory" example in Workflow Nodes.

Security benefits:

• Protected from AI chat - Encrypted files cannot be read by AI vault operations (read_note tool). This keeps sensitive data like API keys safe from accidental exposure during chat.
• Workflow access with password - Workflows can read encrypted files using the note-read node. When accessed, a password dialog appears, and the password is cached for the session.
• Store secrets safely - Instead of writing API keys directly in workflows, store them in encrypted files. The workflow reads the key at runtime after password verification.

Semantic Search (RAG)

Local vector-based search that injects relevant vault content into LLM conversations. No external RAG server required — embeddings are generated and stored locally.

Setup:

1. Go to Settings → RAG section
2. Create a new RAG setting (click +)
3. Configure embedding:
   • Default (Gemini): Leave Embedding Base URL empty — uses Gemini Embedding API with your Gemini API key
   • Custom server (Ollama etc.): Set Embedding Base URL and select a model
4. Click Sync to build the vector index from your vault
5. Select the RAG setting in the search menu to activate it; Web Search can remain checked at the same time

Multimodal indexing (images, PDFs, audio, video) is automatically enabled when using Gemini native embedding models (gemini-embedding-*). No manual configuration needed.

Large vaults and multiple indexes:

For large vaults, create multiple RAG settings for separate folders, sync each one, then create another RAG setting and choose Combine internal. Select the synced source settings to search them together from one chat/search selector. Combined settings use the embedding server, API key, and model from the first selected source setting.

During sync, changed files are processed and saved in small file batches. This is separate from the RAG chunk size setting. If Obsidian crashes during a large first-time sync, the next sync can continue from the saved index state instead of starting from scratch.

If PDF text extraction fails, the failed PDF paths are listed after sync, their checksums are saved, and they appear in the indexed file list with 0 chunks. They will not be retried on later syncs unless the PDF file changes. To force re-import, rename the PDF, modify the file, or clear/rebuild the RAG index.

External Index:

Use a pre-built index instead of syncing from the vault:

1. Set Index mode to External
2. Enter one absolute index directory per line. Each directory must contain index.json and vectors.bin
3. Optionally set Embedding Base URL for query embedding (empty = Gemini API)
4. The embedding model is auto-detected from the index file

How it works: When RAG is active, each chat message triggers a local vector search. Relevant chunks are injected into the system prompt as context. Sources are shown in the chat UI — click to open the referenced note.

RAG Search Tab

The RAG Search tab provides a dedicated interface for searching, filtering, editing, and sending RAG results to Chat or Discussion.

• Semantic search with adjustable Top K and score threshold
• Keyword filter to narrow results after search
• Chunk editor with adjacent chunk loading (prev/next) and overlap removal
• Send to Chat or Discussion — selected results become editable attachments
• Index settings (gear icon) — configure chunk size, overlap, target folders, sync, and more

For full details, see RAG Search Documentation

Slash Commands

• Define custom prompt templates triggered by /
• Optional model and search override per command

Requirements

• Obsidian v0.15.0+
• At least one of: API key (Gemini, OpenAI, Anthropic, OpenRouter, Grok), local LLM server, or CLI tool
• Desktop only (for mobile, see Gemini Helper)

Privacy

Data stored locally:

• API keys (stored in Obsidian settings)
• Chat history (as Markdown files, optionally encrypted)
• Workflow execution history (optionally encrypted)
• RAG vector index (stored in workspace folder)
• Encryption keys (private key encrypted with your password)

Data sent to LLM providers:

• Chat messages and file attachments are sent to the configured API provider (Gemini, OpenAI, Anthropic, OpenRouter, Grok, or custom endpoint)
• When Web Search is enabled, queries are sent through the selected provider's native search service (Google for Gemini, OpenAI Web Search, Anthropic Web Search, or xAI Web Search)
• Local LLM providers send data only to your local server

Data sent to third-party services:

• Workflow http nodes can send data to any URL specified in the workflow

CLI providers (optional):

• When CLI mode is enabled, external CLI tools (gemini, claude, codex) are executed via child_process
• This only occurs when explicitly configured and verified by the user
• CLI mode executes external CLI tools via child_process

Discord bot (optional):

• When enabled, the plugin connects to Discord via WebSocket Gateway and sends user messages to the configured LLM provider
• Bot token is stored in Obsidian settings
• Message content from Discord channels is processed by the LLM — configure allowed channels/users to restrict access

MCP servers (optional):

• MCP (Model Context Protocol) servers can be configured in plugin settings for workflow mcp nodes
• MCP servers are external services that provide additional tools and capabilities

Security notes:

• Review workflows before running - http nodes can transmit vault data to external endpoints
• Workflow note nodes show a confirmation dialog before writing files (default behavior)
• Slash commands with confirmEdits: false will auto-apply file edits without showing Apply/Discard buttons
• Sensitive credentials: Do not store API keys or tokens directly in workflow YAML (http headers, mcp settings, etc.). Instead, store them in encrypted files and use note-read node to retrieve them at runtime. Workflows can read encrypted files with password prompt.

See each provider's terms of service for data retention policies.

License

MIT

Links

• Gemini API Docs
• OpenAI API Docs
• Anthropic API Docs
• OpenRouter Docs
• Ollama
• Obsidian Plugin Docs

Support

If you find this plugin useful, consider buying me a coffee!