Obsidian AI Exporter

Chrome Extension that exports AI conversations from Google Gemini, Claude AI, ChatGPT, Perplexity, and Gemini Notebook (formerly NotebookLM) to Obsidian via the Local REST API.

日本語版はこちら

• Multi-platform support: Export from Google Gemini, Claude AI, ChatGPT, Perplexity, and Gemini Notebook (formerly NotebookLM)
• One-click export: Floating "Sync" button on supported AI pages
• Multiple output options: Save to Obsidian, download as file, or copy to clipboard
• Deep Research support: Export Gemini Deep Research, Claude Extended Thinking, and Perplexity Deep Research reports
• Artifact support: Extract Claude Artifacts with inline citations and sources
• Image export: Gemini-generated images are saved alongside the conversation — embedded in your vault, downloaded as files, or stripped for clipboard
• Source citations: Gemini Notebook chat citations are exported as footnotes
• Auto-scroll: Automatically loads all messages in long conversations, including virtualized (windowed) Claude and ChatGPT threads
• Append mode: Only new messages are added to existing notes
• Filename schemes: Choose title-id (default) or title-date naming for exported notes
• Vault path templates: Organize with {platform} and date tokens ({YYYY}, {MM}, …) for auto-sorting
• Filename collision safety: Never overwrites a note belonging to a different conversation
• Tool content support: Optionally include Claude's web search results and tool activity as collapsible [!ABSTRACT] callouts
• Question headers (optional): Prepend a ## heading (first 60 chars of the question) before each user message for TOC navigation in long conversations
• Large-callout flattening: Optionally flatten very long messages to plain text when saving to Obsidian, avoiding renderer slowdowns; the line threshold is configurable (default 200)
• Configurable timezone: Set timezone for frontmatter dates (created/modified)
• Math formula preservation: LaTeX math ($...$ and $$...$$) is preserved across all platforms for Obsidian's math renderer
• Obsidian callouts: Formatted output with [!QUESTION] and [!NOTE] callouts
• YAML frontmatter: Metadata including title, source, URL, dates, and tags
• Configurable: Customizable vault path, template options, and frontmatter fields
• Localized: English and Japanese UI support

• Google Chrome 96+ (or Chromium-based browser)
• Obsidian
• Obsidian Local REST API plugin

Install from Chrome Web Store

1. Clone this repository:

   git clone https://github.com/sho7650/obsidian-AI-exporter.git
   cd obsidian-AI-exporter

2. Install dependencies:

   npm install

3. Build the extension:

   npm run build

4. Load in Chrome:

   • Navigate to chrome://extensions
   • Enable "Developer mode"
   • Click "Load unpacked"
   • Select the dist/ folder

1. Install the Local REST API plugin in Obsidian
2. Enable the plugin and copy your API key
3. Click the extension icon in Chrome and enter:
   • API Key: Your Local REST API key
   • API URL: Default is http://127.0.0.1:27123 (HTTPS is also supported — see HTTPS Setup)
   • Vault Path: Folder path in your vault (e.g., AI/{platform} to auto-organize by source)

1. Open a conversation on gemini.google.com (regular chats and Gem conversations are both supported)
2. Click the purple "Sync" button in the bottom-right corner
3. The conversation will be exported based on your selected output method:
   • Obsidian (default): Saved directly to your vault via Local REST API
   • File: Downloaded as a Markdown file
   • Clipboard: Copied to clipboard for pasting anywhere

Gemini-generated images are captured and exported automatically (see Image Export).

1. Open a conversation on claude.ai
2. Click the purple "Sync" button in the bottom-right corner
3. The conversation will be exported with the same output options as Gemini

Keep Auto-scroll enabled for long conversations. Claude mounts only a window of turns at a time and discards the rest; with Auto-scroll off, only the turns currently on screen can be exported.

1. Open a conversation on chatgpt.com (regular chats and custom GPTs via /g/ URLs are both supported)
2. Click the purple "Sync" button in the bottom-right corner
3. The conversation will be exported with the same output options as Gemini

Keep Auto-scroll enabled for long conversations. ChatGPT mounts only a window of turns at a time and discards the rest; with Auto-scroll off, only the turns currently on screen can be exported.

1. Open a conversation on www.perplexity.ai
2. Click the purple "Sync" button in the bottom-right corner
3. The conversation will be exported with the same output options as Gemini

1. Open a notebook on notebook.google.com (the old notebooklm.google.com links still work — Google redirects them)
2. Click the purple "Sync" button in the bottom-right corner
3. The chat conversation will be exported with inline source citations as footnotes

Gemini Deep Research:

1. Open the Deep Research panel (expanded view)
2. Click the "Sync" button
3. The full report will be saved with its original heading structure

Claude Extended Thinking (Artifacts):

1. Open a conversation with an Artifact
2. Click the "Sync" button
3. The Artifact content with inline citations and sources will be extracted

Perplexity Deep Research:

1. Open a Perplexity conversation containing a Deep Research report
2. Click the "Sync" button
3. The report content will be extracted alongside normal conversation messages

Conversations are saved as Markdown files with YAML frontmatter:

---
id: gemini_abc123
title: "How to implement authentication"
source: gemini
url: https://gemini.google.com/app/abc123
created: 2025-01-10T12:00:00Z
modified: 2025-01-10T12:30:00Z
tags:
  - ai-conversation
  - gemini
message_count: 4
---

> [!QUESTION] User
> How do I implement JWT authentication?

> [!NOTE] Gemini
> To implement JWT authentication, you'll need to...

When "Include tool/search results" is enabled, Claude's web search and tool activity are rendered as collapsible callouts before the assistant response:

> [!ABSTRACT]- Searched the web
> Rust latest version 2026 (10 results)
> - Rust Versions | Rust Changelogs (releases.rs)
> - Rust | endoflife.date (endoflife.date)

> [!NOTE] Claude
> Here are the latest Rust version details...

The [!ABSTRACT]- callout is collapsed by default in Obsidian (the - suffix).

Deep Research reports include a type field and preserve the original structure:

---
id: gemini_deep-research-a1b2c3d4
title: "Comprehensive Analysis of..."
source: gemini
type: deep-research
url: https://gemini.google.com/app/xxx
created: 2025-01-11T10:00:00Z
modified: 2025-01-11T10:00:00Z
tags:
  - ai-research
  - deep-research
  - gemini
message_count: 1
---

# Report Title

## 1. Introduction

The report content with original headings...

## 2. Analysis

Detailed analysis sections...

The Vault Path setting supports template tokens that are resolved at save time, so notes can be auto-organized. The default is AI/{platform}.

Example: AI/{platform}/{YYYY}/{MM} sorts notes into per-month folders. Date tokens use your local time zone. In append mode, existing conversations continue updating their original file even after the month rolls over.

Note: Gemini Notebook still resolves {platform} to notebooklm, unchanged by the rebrand, so notes keep landing in the folder your existing ones already use.

Choose how exported note filenames are built (Advanced Settings → Filename scheme):

• title-id (default): {title}-{conversationId}.md — stable across renames of the conversation.
• title-date: {title}-{YYYY}-{MM}-{DD}.md — uses the local save date.

If the intended filename is already occupied by a different conversation, the extension writes to a safe alternative name instead of overwriting it.

Gemini-generated images are exported alongside the conversation (enabled by default; toggle with Export images in Advanced Settings). Each image is captured as base64 and then resolved per output destination:

• Obsidian: images are written to your vault under Image Folder (default AI/{platform}/images, supports the same template tokens as the vault path); the note body embeds them with ![[filename]] wikilinks.
• File download: the Markdown file and each image are downloaded as separate files.
• Clipboard: image placeholders are stripped (no binary is copied).

Gemini serves generated images either from blob: URLs, which only the page can read, or from Google's image CDN (googleusercontent.com). The extension reads blob: URLs in the page and downloads CDN-hosted images in the background worker — the browser blocks the page from fetching them directly. This is why the extension requests access to googleusercontent.com; it is used only to download images you asked to export.

Guards: up to 20 images per note and 10 MB per image. Append mode strips image placeholders (image handling in append mode is deferred). If an image cannot be saved, the note is still written and a warning names the images that were skipped.

The dev environment is provisioned by Nix (see ADR-010). With direnv and nix-direnv installed, entering the directory loads the environment automatically; otherwise run nix develop.

Every workflow has a Nix entry point (canonical) and an npm run alias (compatibility). See ADR-011.

If node_modules/ is missing, the Nix wrapper exits with an instruction to run npm ci first. Dependency installation is intentionally not auto-run.

Content Script (gemini.google.com, claude.ai, chatgpt.com, www.perplexity.ai, notebook.google.com + legacy notebooklm.google.com)
    ↓ extracts conversation / Deep Research / Artifacts
Background Service Worker
    ↓ sends to Obsidian
Obsidian Local REST API (default: http://127.0.0.1:27123)

The extension supports HTTPS connections to the Obsidian Local REST API. This is useful when:

• The Local REST API is configured with HTTPS (self-signed certificate)
• You want to connect to an Obsidian instance on your local network (LAN)

1. Extract the certificate from the running Obsidian REST API:

   openssl s_client -connect 127.0.0.1:27124 -showcerts \
     </dev/null 2>/dev/null | openssl x509 -outform PEM > obsidian-cert.pem

2. Import into macOS Keychain as a trusted root certificate:

   sudo security add-trusted-cert -d -r trustRoot \
     -k /Library/Keychains/System.keychain obsidian-cert.pem

3. Restart Chrome completely (Cmd+Q → relaunch). A simple tab reload is not sufficient.

4. Set the API URL in the extension popup to your HTTPS endpoint (e.g., https://127.0.0.1:27124).

Note: If Obsidian regenerates its certificate (e.g., after a plugin update), you must re-extract and re-import the new certificate. Chrome extensions require OS-level certificate trust — browser-level "proceed anyway" exceptions do not apply to extension service workers.

Import the certificate into your OS certificate store and restart Chrome. The general approach is the same — the certificate must be trusted at the OS level, not just accepted in the browser.

• Secure storage: API key stored in chrome.storage.local (not synced)
• Input validation: Message content and filenames validated
• Path traversal protection: Vault paths sanitized against directory traversal attacks
• Sender verification: Only trusted origins can send messages
• CSP: Content Security Policy configured for extension pages
• YAML escaping: Frontmatter values properly escaped

This extension:

• Does not collect your data, and sends no analytics or telemetry anywhere
• Sends your conversations only to your Obsidian instance (default: 127.0.0.1, configurable for LAN access)
• Downloads generated images from Google's image CDN (googleusercontent.com) when image export is enabled — the same host the AI page already loads them from, and only for images in the conversation you are exporting
• Stores API key locally in your browser (not synced to cloud)

See our Privacy Policy for details.

MIT

Contributions are welcome! Please read the CLAUDE.md for development guidelines.