0.5.0

A chat that leaves the vault alone when you ask it to, a model that stopped rummaging in
your note uninvited, and the price of a question written on the button.

A private chat

Like a private window in a browser: a separate conversation where nothing leaves the
vault at all — no note, no selected fragment, no editing tools, no system prompt, not even
your own one from the settings. Just the model, the way it answers on the provider's own
site.

Start it from the … menu in the panel header, from the command palette, or with Alt+2 if
you let the plugin take the keys. The header is tinted while you are in it, and in place of
the "note as context" button sits an unplugged cord — there is nothing to switch on. A
normal "New chat" brings everything back.

It is a property of the conversation, not a setting: nothing to leave switched on by
accident and forget about. A fragment selected in a note is never picked up there, however
it got selected — and the plugin says so out loud rather than quietly sending it.

The model stopped rummaging in your note

Asked to invent a joke about cheese, the model would first go and read whatever note you had
open. It cost a whole extra round trip — 5 600 tokens in instead of 1 100 — for a question
that had nothing to do with the note. The system prompt only ever explained how to edit
a note and never said when not to reach for it.

Now the model is told whether it can see the note at all: with the note attached it is asked
not to read it a second time, and without it — not to go looking just in case. Most
questions are answered with words, and it is told that too.

The card for a read no longer says "Applied" in green either. Nothing was applied — the note
did not change.

What a question costs

• The context button now carries a number. With it on, the open note goes to the model
  with every question; the button looked exactly the same for a one-line note and for a
  twelve-thousand-character script. Hover it for the exact figures — the note and the
  conversation separately.
• The running total for the conversation sits under the input field. Each answer already
  showed its own cost; nobody was adding ten of them up by hand. Edits made over a selection
  count towards it too — they are paid for the same way.

Ask again — with a different model

"Ask again" used to re-run the same question through the same model that had just
disappointed you. It now opens a menu: the same one first, then every provider you have
configured. The choice is for that one run — the plugin does not switch over, so your next
question goes where it was going before.

The journal of edits gained the same menu, and its cards are now signed with the model that
did the work — otherwise there is no telling which one came out better.

Where new notes go

A saved conversation, and anything the model creates on its own, used to land in the vault
root. There is now a choice in the settings: the root, one folder of your own, or next to
the note you are working on. A folder is created if it is not there yet — matched
case-insensitively, one step at a time, so archive/ai cannot quietly become a second
Archive.

Things that were quietly going wrong

• An answer that arrived only as reasoning is no longer thrown away. Some models — and
  some providers — put the whole text in the reasoning field and leave the answer empty. The
  panel said "the model returned an empty answer" and dropped everything, including the
  tokens you had paid for. The reasoning now becomes the answer, and the chat says as much.
• A stopped stream no longer lands in the middle of the next question. Pressing Stop
  returns whatever arrived as a normal answer, not an error, so the panel filed it away
  without checking whose turn it was. Ask something new before the previous answer finishes
  and the leftovers used to appear underneath your new question.
• An edit card no longer claims success when the edit failed. A fragment that was not
  found, a note that had been closed, a tool the model invented — all of it was marked
  "Applied", and the model was then told in the conversation that the work was done.
• The down arrow in the quick menu no longer wipes what you typed. In a three-line field
  it is how you move to the next line; instead it replaced the prompt with nothing, with no
  way back.
• A malformed action in data.json no longer stops the plugin from loading. An action
  missing its name took the whole load down with it — settings and conversation included —
  which is precisely what the merge routine exists to prevent.
• A provider answering with something that is not JSON now says so instead of showing a
  bare SyntaxError. Proxies and portals hand back an HTML page with a 200 more often than
  one would think.