What changed across Social Archiver

Two fixes. First, on Windows `executor --watch` crashed with a runtime panic right after CLI detection — resolved by changing how tool version checks spawn subprocesses. Second, we found the real reason AI summary jobs failed with PROVIDER_MISSING while detection looked perfectly healthy: the job details the executor fetched from the server were missing which AI to use (the provider). The server is fixed alongside this release, so already-installed 0.1.9/0.1.10 and the desktop app work again without updating.

• Fixed executor --watch crashing right after detection on Windows — watch mode now runs to completion.
• AI jobs no longer arrive from the server without their provider — fixed server-side too, so existing installs recover immediately.
• The executor now sends its client ID when fetching job details, so it always receives the complete job.

The executor could report an installed Claude, Gemini or Codex CLI as "not installed", and AI summary jobs then failed with PROVIDER_MISSING. The cause: it only checked a few well-known install locations — native installers, nvm, volta and scoop put the CLI elsewhere, which is exactly what hit Claude Code and Codex on Windows. Now, if the command runs in your terminal, the executor finds it too. Alongside that, an AI job that fails on one machine is no longer dead: another executor on your account (the Obsidian plugin or the desktop app) can pick it up and finish it.

• AI CLI detection now resolves commands the same way your terminal does — native installers, npm, nvm/volta/fnm and scoop layouts are all recognized.
• Fixes Claude Code and Codex going undetected on Windows, where previously only npm installs were recognized.
• An AI summary or translation job that fails on one executor is no longer terminal — another executor picks it up shortly after and completes it.
• Retries stay bounded by the server, so when no executor can handle a job it still fails clearly.

Until now the CLI could only create a subscription. Pausing one, listing them, or working out why new posts stopped arriving meant opening the app. All of that now works from the terminal, and the run history shows what each run saved, what it cost, and — when it failed — why. The same commands were added to the Obsidian plugin CLI in 4.6.6, so both behave the same way.

• List your subscriptions, pause or resume one, run it on the spot, or delete it when it has served its purpose.
• Diagnose it yourself from the run history — per-run saved counts and credits, plus the reason when a run failed.
• Pausing keeps its place, so resuming does not skip the posts from while it was off.
• Deleting requires an explicit confirmation flag, and the archives it already saved stay put.
• The Obsidian plugin CLI gained the same commands, plus place-candidate review and bulk Inbox triage (plugin 4.6.6).

A standalone tool for archiving, finding, and organizing from a terminal. It runs on Windows, macOS, and Linux with no desktop app and no Node.js required. With 0.1.5 the Microsoft Store listing completes the set of install routes, and exports now carry each archive's places and product details. The CLI guide documents every command.

• One line to install, anywhere: Microsoft Store or winget on Windows, Homebrew on macOS, a checksum-verified installer on macOS and Linux, and npm wherever Node.js already lives. No desktop app required.
• Archive and find: archive a URL, search your whole archive server-side, move posts between Inbox and Archived, and subscribe to public profiles.
• Organize locally: export archives to Markdown, grep them, add tags and notes, then push the edits back. After one export, searching costs no further server calls.
• New in 0.1.5 — exported Markdown carries places (name, address, coordinates, category) and product details (price, currency, availability, brand, rating), and the new places command reviews extracted candidates with their evidence so you can confirm or detach them.
• AI work stays in the terminal: request AI comments, run them yourself with a local AI tool through the executor, and transcribe video and audio archives.
• Built with coding agents in mind: every command answers in the same JSON shape, and an installable skill bundle teaches Claude Code, Codex, and OpenCode to drive it safely.