dropbits Documentation

LLM chat & API key

Hub → LLM chat opens the optional Assistant. It uses the same tools as the editor — no parallel write path. Prefer concrete asks about the page you are on. Everyday edits do not require a key.

Ask before apply

  1. Ask what the assistant would change and whether it understands your goal.
  2. Only then ask it to apply.
  3. Save a checkpoint (Safety in chat, or Hub → Backup) before risky batches.
  4. Undo in the chat rolls back the last tool batch — that is not the same as restoring a named checkpoint slot.

API key (bring your own)

Dropbits does not ship free-tier API keys. You need a Mistral (or compatible) key for chat.

Obtain a key

  1. Create an account at console.mistral.ai.
  2. Open API keys and create a key (typically starts with sk-).
  3. Keep the secret out of git and out of the site database.

Browser (editors)

In Assistant settings (API key settings):

  1. Check Use my Mistral API key.
  2. Paste the key → Save key.

The key stays in browser localStorage and is sent only to the server proxy per chat request — never written to the site database.

Server (operators)

Operators can place a one-line key file on the server. Paths and env overrides: LLM key for operators.

Voice dictation

Where the browser supports the Web Speech API, the chat toolbar Mic button fills the input box. It never auto-sends — edit the text, then Send. Works in Chrome; some Chromium builds fail because Web Speech needs Google’s STT backend. Unsupported browsers show the button disabled.

See also