0.8.0

A PDF in the question — read where the text already is.

A document is attached the same ways a picture is: the paperclip, dragged into the panel,
"from the vault", or an ![[embed]] in the open note. What travels, though, is not the file
but its text — the layer already inside the PDF.

Why that is the interesting part

Text works with every provider. Including DeepSeek, which takes no images at all — so the
model most of these questions were going to anyway can now be asked about a document. The
"this model does not take images" warning does not fire for documents, because there is
nothing to warn about.

Nothing is recognised here, either. What is written in the file is what goes; the plugin only
reads it.

What the chip says before you send

методичка.pdf · 12 pp. · 34 000 chars. The characters are the price of the question, and
they are on screen before the question leaves rather than in the bill afterwards.

A document longer than the limit is sent from the beginning, and the chip says so — (the beginning only). The cut falls on a page boundary, never mid-sentence: a page broken in half
reads as a failure to read the file, not as a deliberate trim. The limit is the same 40 000
characters the note-as-context has had all along.

Documents follow the same rule as pictures in a conversation: only the freshest one travels
into a new request, and about the others the model is told in words. A document is not copied
into the vault — the setting promises to keep images, and it is right to: a screenshot in a
chat is worth seeing again, a twenty-megabyte document in the attachments folder is litter.
So a PDF from disk lives until the next restart, and a PDF from the vault is read by its path
and outlives everything.

A scan says so itself

A photograph of a page has no text in it at all. The plugin says exactly that when the file
is attached — "there is no text layer in this PDF, only pictures of the pages" — rather than
sending an empty question and letting the answer explain what went wrong. Pulling text out of
a picture is a different job, and this release does not pretend to do it.

No new weight

Obsidian already ships pdf.js — its own PDF viewer runs on it — and it turns out to be
reachable: the global it installs is made read-only rather than taken away. It loads lazily,
so when nothing has opened a PDF yet the plugin loads it exactly the way Obsidian does.

Half a megabyte of library and a megabyte and a half of worker that would otherwise have been
carried a second time, for a file already sitting next door. The plugin grew by five
kilobytes.