Add AI-powered analysis to your archived posts. Comments run locally with AI CLI tools on your computer, or through Cloud AI on the Social Archiver server for supported actions.
AI Comments lets you generate intelligent analysis of archived content — summaries, fact-checks, sentiment analysis, and more. Run it locally with AI CLI tools installed on your computer (nothing leaves your device), or use Cloud AI on the Social Archiver server for supported actions when no local executor is available.
Privacy: Your content never leaves your device. All AI processing happens locally.
No API Costs: Use your existing AI CLI subscriptions - no additional fees per analysis.
Full Control: Choose which AI model to use and customize prompts.
Two ways to run AI Comments
AI Comments run either locally through a desktop executor (AI CLI tools on your computer) or on Cloud AI (the Social Archiver server). Mobile and web can complete supported actions through Cloud AI even with no desktop executor open. See Where AI Comments Run.
A local executor runs the AI CLI tools you installed (Claude Code, Codex, or Gemini CLI) on your machine. Any of these can be the executor:
Obsidian desktop plugin — desktop Obsidian with AI Comments enabled.
Social Archiver desktop app — the standalone desktop app can run AI Comment jobs with your local AI CLIs, no Obsidian required.
Headless CLI — sa executor --watch runs queued jobs from your terminal. See Command Line (CLI).
Local execution keeps your content on your device, uses your existing CLI subscriptions, and does not spend Social Archiver AI credits. A request from mobile or web is queued until one of your local executors picks it up.
Cloud AI runs supported actions on the Social Archiver server (Cloudflare Workers AI), so they complete even when no local executor is open — useful from the mobile app or web. Cloud AI currently supports these comment actions:
Summary
Glossary
Translation
It also powers AI tag suggestions (see Tags). Other comment types — Fact Check, Critique, Sentiment, Connections, Reformat, and Custom — run on a local executor only.
How Cloud AI differs from local execution:
Your content is sent to the server. Cloud AI forwards the archive text needed for the action to Cloudflare Workers AI, and asks for your consent the first time. Choose Local only (below) if you never want archive text to leave your device.
Credits. Translation with Cloud AI uses AI credits from your plan; local AI does not. Premium plans include monthly Cloud AI credits.
Length limit. Very long archives can exceed the Cloud AI limit — split the content, or run it with a local executor.
Obsidian security scans may show a Shell Execution warning for Social Archiver. For AI Comments, this is expected because desktop Obsidian launches the selected AI CLI as a local process. Commands run only after you enable AI Comments and request generation, and they use the CLI account/session already installed on your computer. Mobile requests can queue jobs, but mobile Obsidian does not run the shell command; the connected desktop executor does.
Use this checklist when the mobile app says AI Comments need setup:
Install the Social Archiver Obsidian plugin and sign in to the same account used by the mobile app.
Install and sign in to at least one supported desktop AI CLI: Claude Code, Codex, or Gemini CLI.
In desktop Obsidian, open Settings → Social Archiver → AI Comments and turn on Enable AI Comments.
Keep desktop Obsidian open when you want requests to run immediately. If it is offline, mobile requests are queued until the desktop plugin reconnects.
Improve the markdown formatting of archived content without changing the actual text. Useful when:
Post content has broken line breaks or spacing
Content could benefit from section headers
Inline lists need proper bullet formatting
Visual hierarchy needs improvement
The AI will only modify formatting (headers, lists, emphasis) while preserving the original words, links, media embeds, and comments section.
Apply Changes
After generating a Reformat comment, click the Apply button (checkmark icon) to replace the post body with the reformatted version. The original content is preserved in the AI comment history.
Use your own prompt for specialized analysis. When you select "Custom" from the type dropdown, an input field appears where you can enter your specific request or question about the content.
Click "Add AI Comment": Banner appears on archived posts
Select Type: Choose analysis type from dropdown
Processing: AI CLI runs locally (progress shown)
Result Saved: Comment added to your markdown file
AI Comments are stored in your note's ## AI Comments section:
markdown
## AI Comments### 🤖 Claude · Summary · Dec 16, 2024This post discusses the impact of AI on creative industries,highlighting both opportunities and challenges...---
When you run AI Comments locally, all AI processing happens on your device using CLI tools. Your content is processed by the AI models but never stored on external servers beyond what's required for the API call.
With Cloud AI, the archive text needed for the action is sent to Cloudflare Workers AI on the Social Archiver server. Cloud AI runs only for supported actions and only after you consent. Choose Local only in Settings → AI Execution to keep archive text on your device.
AI Comments
Add AI-powered analysis to your archived posts. Comments run locally with AI CLI tools on your computer, or through Cloud AI on the Social Archiver server for supported actions.
Overview
AI Comments lets you generate intelligent analysis of archived content — summaries, fact-checks, sentiment analysis, and more. Run it locally with AI CLI tools installed on your computer (nothing leaves your device), or use Cloud AI on the Social Archiver server for supported actions when no local executor is available.
Why Local AI?
Two ways to run AI Comments
AI Comments run either locally through a desktop executor (AI CLI tools on your computer) or on Cloud AI (the Social Archiver server). Mobile and web can complete supported actions through Cloud AI even with no desktop executor open. See Where AI Comments Run.
Where AI Comments Run
Every AI Comment is produced by an executor. You can use a local executor on your own computer, or Cloud AI on the Social Archiver server.
Local Executors
A local executor runs the AI CLI tools you installed (Claude Code, Codex, or Gemini CLI) on your machine. Any of these can be the executor:
sa executor --watchruns queued jobs from your terminal. See Command Line (CLI).Local execution keeps your content on your device, uses your existing CLI subscriptions, and does not spend Social Archiver AI credits. A request from mobile or web is queued until one of your local executors picks it up.
Cloud AI
Cloud AI runs supported actions on the Social Archiver server (Cloudflare Workers AI), so they complete even when no local executor is open — useful from the mobile app or web. Cloud AI currently supports these comment actions:
It also powers AI tag suggestions (see Tags). Other comment types — Fact Check, Critique, Sentiment, Connections, Reformat, and Custom — run on a local executor only.
How Cloud AI differs from local execution:
Execution Mode
In the mobile app, Settings → AI Execution controls how the two paths combine:
Obsidian Shell Execution Warning
Obsidian security scans may show a Shell Execution warning for Social Archiver. For AI Comments, this is expected because desktop Obsidian launches the selected AI CLI as a local process. Commands run only after you enable AI Comments and request generation, and they use the CLI account/session already installed on your computer. Mobile requests can queue jobs, but mobile Obsidian does not run the shell command; the connected desktop executor does.
Setup Checklist
Use this checklist when the mobile app says AI Comments need setup:
Supported AI CLI Tools
You need at least one of the following CLI tools installed:
Recommendation
Claude Code is recommended for most users. It has the easiest setup and includes web search capabilities for fact-checking and glossary features.
→ See AI CLI Setup Guide for detailed installation instructions
When AI Comments Appear
AI Comments are available when all of the following conditions are met:
When these conditions are met, you'll see an "Add AI Comment" banner below archived posts in Timeline View.
Without a local executor, Cloud AI can still run Summary, Glossary, and Translation — see Where AI Comments Run.
Comment Types
Summary
Generate a concise 2-3 sentence overview of the content. Great for quickly understanding long posts.
Fact Check
Verify claims in the content using web search. Returns verdicts with sources for key claims. Best used with Claude Code (has built-in web search).
Critique
Get a balanced critical analysis including:
Sentiment
Analyze the emotional tone of the content:
Glossary
Identify and explain technical or specialized terms in the content. Uses web search to find accurate definitions with sources. Ideal for:
Connections
Find related notes in your Obsidian vault. The AI scans your vault and suggests:
Vault Integration
Connections uses your vault's metadata to find relevant notes. Enable "Vault Context" in settings for best results.
Reformat
Improve the markdown formatting of archived content without changing the actual text. Useful when:
The AI will only modify formatting (headers, lists, emphasis) while preserving the original words, links, media embeds, and comments section.
Apply Changes
After generating a Reformat comment, click the Apply button (checkmark icon) to replace the post body with the reformatted version. The original content is preserved in the AI comment history.
Custom
Use your own prompt for specialized analysis. When you select "Custom" from the type dropdown, an input field appears where you can enter your specific request or question about the content.
How It Works
AI Comments are stored in your note's
## AI Commentssection:Plugin Settings
Configure AI Comments in Settings → Social Archiver → AI Comments:
Platform Visibility
Control which platforms show the AI Comment banner:
Web Sharing
AI Comments are included when you share posts to the web:
Troubleshooting
AI Comment Banner Doesn't Appear
Possible causes:
Solutions:
claude --version(or equivalent)Generation Fails or Times Out
Possible causes:
Solutions:
Poor Quality Results
Solutions:
Privacy & Security
Local Processing
When you run AI Comments locally, all AI processing happens on your device using CLI tools. Your content is processed by the AI models but never stored on external servers beyond what's required for the API call.
With Cloud AI, the archive text needed for the action is sent to Cloudflare Workers AI on the Social Archiver server. Cloud AI runs only for supported actions and only after you consent. Choose Local only in Settings → AI Execution to keep archive text on your device.
Each AI tool has its own privacy policy: