AI Assist

by mrrepac
5
4
3
2
1
Score: 51/100

Description

Obsidian plugin: sidebar AI chat and in-place rewriting of the selected text

Reviews

No reviews yet.

Stats

1
stars
226
downloads
0
forks
112
days
12
days
12
days
0
total PRs
0
open PRs
0
closed PRs
0
merged PRs
0
total issues
0
open issues
0
closed issues
55
commits

Latest Version

13 days ago

Changelog

ChatGPT sign-in, model controls close to the message, and a smaller, cleaner composer.

ChatGPT on desktop

  • Choose ChatGPT (subscription) and Continue with ChatGPT in settings. Fetch the models available to your account, then pick a model and reasoning effort. Effort is remembered per model and applies to the next request.
  • Requests use your eligible ChatGPT plan or available credits. There is no automatic paid API fallback and no Fast mode. Account, workspace, regional and app-specific restrictions still apply.
  • Credentials are encrypted with the operating system through Electron safeStorage, outside the vault. There is no plaintext fallback. Sign-in does not import conversations, assistant memory or a personal assistant identity.
  • Model responses stream through the Responses route. A failed or incomplete response is not treated as a completed note edit.

The ChatGPT provider is desktop-only. The existing API providers remain available on desktop and mobile.

Allowance, when you ask for it

The optional Refresh allowance control reads the shared Codex/ChatGPT Work allowance through an installed, already signed-in official Codex CLI. The account email must match. There is no background polling or inference request.

This is not the plugin's app-specific cap, and matching email does not establish matching workspace. Old snapshots are marked stale and hidden at their reported reset. API credits are not displayed.

The message box

The input, attachment button and send/stop button now share one border. Model, effort and allowance controls sit in a compact toolbar that wraps on narrow sidebars. The extra bottom gap is removed without changing other Obsidian views. Keyboard focus, IME composition and a draft typed during generation are preserved.

Build and verification

The release workflow now runs the complete offline regression suite before publishing. Local checks cover subscription transport, synthetic-token authentication, quota handling, composer behavior and light/dark responsive layouts.

A normal build never deploys to a vault. Explicit deployment requires an existing absolute destination in AI_ASSIST_VAULT_PLUGIN and npm run build:deploy. User settings, conversations, credentials and local deployment backups are not release assets.

Install main.js, manifest.json and styles.css from this release into .obsidian/plugins/ai-assist/, then reload the plugin. See setup and security for details.

README file from

Github

RU AI Assist

A sidebar chat with a language model, and in-place rewriting of the text you selected.

Built for people working from Russia. Every provider it ships with is reachable without a VPN and takes Russian payment cards: DeepSeek directly, plus three Russian aggregators — Polza.ai, ChadGPT and GPTunnel — which give you GPT, Claude, Gemini and the rest through a single key. And Ollama or LM Studio, if you would rather run a model on your own machine.

Most AI plugins are built around the chat. This one is built around the note: you select a piece of text, press a key, and the text changes. The chat is there too, in the right sidebar, but the main road is selection → key → done.

Читаете по-русски? Есть русская версия README.

What it does

  • Actions over the selection. Fix spelling, improve the text, expand it, shorten it, evaluate it — or write your own prompt. The result replaces the selected text; the undo is the usual Ctrl+Z.
  • Selecting is optional. The settings decide what an action works on when nothing is selected: the whole note, the section under the cursor (from its heading down to the next one of the same level, subsections included), the paragraph — or nothing at all, if you would rather always be asked to select.
  • Quick menu opens over the selection: the digits run your presets — five keys to begin with, up to nine if you add them — and the field below takes a one-off instruction. The digit only picks a preset while the field is empty, so a prompt can start with a number. The answer to a one-off instruction comes to the chat; Ctrl+Enter puts it into the note instead. The physical key is what counts, so any keyboard layout works. The menu comes without a key of its own: switch on Alt+1 in the settings, or bind whatever suits you.
  • Nothing selected — you see what was taken. The menu then grows a row — paragraph, section, note — with the size of each, the one from your settings picked and the piece itself highlighted in the note. The arrow keys change it for this one run; the setting stays as it was.
  • Right-click on the selection. The editor's context menu offers the quick menu and a question to the chat — and the actions themselves, each on its own line, if you want them there. On a phone it is the same menu, held down. With nothing selected the plugin adds nothing to it.
  • Ask about a fragment. Select a piece of a note and go to the chat: it comes along as an attachment, so the question can be just "and shorter?" — and the fragment stays with the conversation for the questions that follow.
  • An image with the question. A screenshot from the clipboard (Ctrl+V), a file dragged straight into the panel, the paperclip in the footer — or a right-click on it: "from the vault" and "from this note", by the images embedded in it. Before it is sent the image is scaled down to a sane size, its weight is shown on the chip, and it travels along with the question. Images from earlier replies are not carried into a new request: each one is paid for on every question. A model that does not take images says so before you send, rather than by refusing afterwards.
  • A PDF in the question. A document is attached the same ways a picture is, but travels as text: the plugin reads the text layer — the one already inside the PDF — and sends it along with the question. So it works with any model, including the ones that cannot see pictures. The chip shows up front how many pages and characters are going; a long document is sent from the beginning, and it says so right there. A scan has no text in it at all, and the plugin says plainly that there is nothing to pull out. It brings no reading library of its own: it uses the one Obsidian's own PDF viewer runs on.
  • An action can have its own model. Proofreading is done just as well by the cheapest one, and judging a text without a strong one is pointless — pick a provider inside the action and it always goes there, whatever stands in the panel header.
  • A cut-off answer can be finished. The model ran out of room and stopped mid-word — "Finish it" asks for the rest and joins it to what you already have. Works both in the chat and for an edit over the selection: the half you paid for is not thrown away.
  • A journal of edits in the side panel: what ran, what came back, what exactly changed (word-level diff, "was → became"), an "Undo the edit" button and a "Run it again" one — it brings the text back and runs the same action over it once more.
  • Chat in the right sidebar with streaming, thinking blocks, the running cost in tokens, and a button that saves the conversation into a note.
  • Sources under the answer. A search model answers from pages on the web rather than from memory — the list of them sits under the answer, collapsed, and opens on a click. It is stored with the answer, so it survives a restart, and goes into the note if you save the conversation. The [1][6][8] tails such a model puts after every sentence are stripped from the text — they get in the way of reading, and the list is right there.
  • A private chat can have its own model. It is started to ask something that is not about the vault, and the model wanted there is usually a different one — pick it in the settings and the panel's own stays where it is.
  • The conversation can be rewritten. Under an answer — "ask again"; under your own question — a pencil that puts the text back into the field, so the question can leave as a different one. The bin removes what is not needed, and whatever was removed comes back from the notice.
  • The input field remembers. An unfinished question survives closing the panel and restarting Obsidian, and the up arrow walks through your previous questions.
  • The model can edit the note itself through tools — every edit is shown as a card with an Apply button, so nothing lands in your text without you. An action that answers in the panel gets no tools at all: "show it in the panel" already says "leave the note alone".

Providers

OpenAI-compatible API providers, plus an optional ChatGPT subscription provider on desktop. ChatGPT availability depends on the account, workspace and supported region; it is not included in the Russia-without-a-VPN list below.

The API presets include:

  • DeepSeek — the Chinese model directly: cheap, no middleman;
  • Polza.ai, ChadGPT, GPTunnel — Russian aggregators: one key, and behind it GPT, Claude, Gemini and dozens of other models, paid for with a Russian card;
  • Perplexity — less a model than a search engine with a model on top: it reads the web first, then answers and attaches the links. You reach for it for facts and fresh news — the things an ordinary model does not know and happily invents. It has no note-editing tools, and the plugin does not send it any;
  • Ollama and LM Studio — a model on your own computer, free and offline. With LM Studio the answer arrives whole rather than letter by letter: it does not let a plugin read it as it is written.

Plus any other base URL you type in. The API key, the model and the address are remembered separately for each provider, so switching back and forth does not lose your keys.

With Ollama or LM Studio running on your machine, nothing leaves it at all: no key is asked for and none is sent.

Getting started

  1. Install the plugin and open its settings.
  2. Pick a provider, paste its API key or use Continue with ChatGPT, and choose a model. The "Fetch" button asks the provider for the list. "Test connection" sends a short request and may use allowance or credits.
  3. In the "Quick menu" section, switch on Alt+1 — or give the "Quick menu over the selection" command a key of your own in Obsidian's hotkey settings.
  4. Select some text in a note and press it. Or right-click the selection — the plugin is already there.

Settings

Everything lives in three sections:

  • Provider — service, address, key, model, connection test.
  • Behaviour — temperature, response length limit, streaming, what to do when nothing is selected (the whole note / the section / the paragraph / nothing), the length past which it asks before sending, token usage display, the model for a private chat, where new notes go (the vault root / a folder of your own / next to the note being worked on), whether images brought into the chat are kept in the vault, note editing tools, the system prompt for the chat. The same section decides how the panel starts: whether it opens empty when Obsidian starts, and whether it is cleared before every run from a note (and if it is — whether the cards of edits already made, with their “Undo edit” button, survive the clearing).
  • Quick menu — the keys: five by default, more if you add them, and a row can be dragged by its handle; plus what the plugin puts into the editor's context menu. Each key is an action, and this is where an action is edited: name, icon, prompt, what to do with the answer and which model runs it. Your own action is created in a slot too. An action taken off a slot is not lost — it keeps its own command, and a command can be given a hotkey.

Commands

Every action is a command, so any of them can get a hotkey of your own. Plus: open the chat, start a private chat, ask about the selection, repeat the last action, stop generation, and the quick menu. The last two take Alt+1 and Alt+2 if you switch that on in the settings.

What is sent where

The text you run an action on goes to the provider you configured, and nowhere else. The plugin has no telemetry, no analytics and no server of its own; the settings live in .obsidian/plugins/ai-assist/data.json and the chat history in history.json next to it, inside your vault. ChatGPT sign-in credentials are the exception: they are encrypted with the operating system through Electron safeStorage and kept in Obsidian's local application data, outside the vault. They are never saved in plugin settings or chat history.

An image attached to a question goes to that same provider and inside the request itself, as a data: address, without being uploaded anywhere. With "Keep images brought into the chat" switched on it lands in the vault's attachment folder as the question is sent — the same folder Obsidian itself uses; switched off it lives until the next restart and never touches the disk. In a private chat it is never saved.

From a PDF it is the text that goes, not the file: the plugin reads the text layer and sends it to the same provider the question goes to. The document itself is not copied into the vault — the setting about images does not cover it.

Two things send more than the question itself. "Send the current note as context" attaches the open note to every request in the chat. And a model allowed to edit notes can read the open one whenever it decides to — that is a separate switch, and every call it makes is shown in the panel as a card.

When none of that is wanted, there is the private chat — the "New private chat" entry in the header's … menu, the command in the palette, or Alt+2 if you let the plugin take the keys. It works like a private window in a browser: a separate conversation where nothing leaves the vault at all — no note, no selected fragment, no tools, no system prompt. Just your question and the answer, the way it works on the provider's own site. The header is tinted there, and in place of the context button sits an unplugged cord: there is nothing to switch on. A normal "New chat" brings everything back.

Requirements

Obsidian 1.8.7 or newer. Desktop and mobile for the existing API providers. Use a provider's API key, a local model server, or an eligible ChatGPT account on desktop.

License

MIT — see LICENSE.

ChatGPT subscription (desktop)

Use Continue with ChatGPT in settings, fetch your account's models, then choose a model and reasoning effort. Requests use the eligible ChatGPT plan or available credits. There is no automatic paid API fallback and no Fast mode. Existing API providers are unchanged.

The optional allowance display uses an already installed and signed-in official Codex CLI. Refresh it manually to see the shared Codex/ChatGPT Work allowance for a matching email. It is not the plugin's own limit, and a matching workspace is not verified.

See setup, security and verification. For manual installation, download main.js, manifest.json and styles.css from the latest GitHub release into .obsidian/plugins/ai-assist/, then reload and enable the plugin.

For development, run npm ci, npm run build and npm run test:all. A normal build never copies into a vault. To deploy deliberately, set AI_ASSIST_VAULT_PLUGIN to the existing absolute plugin directory and run npm run build:deploy.