AI (bring your own key)

How the model works

There's no Ledger-hosted AI service. Instead:

• You supply your own API key from a provider you already have.
• The key is stored only in your browser's local storage.
• When you run an AI action, your browser calls the provider's API directly — the request never goes through any DosanjhLabs server.

So you control the model, you control the cost, and your key stays with you. The free local tier works fine with no AI at all — AI is opt-in.

Supported providers

You can override the model with any model string the provider supports (e.g. a different Claude or GPT model) in the Model override field. Leave it blank to use the default for that provider.

Setting up your key

1. Click AI in the top bar.
2. Choose your Provider.
3. Paste your API key (the field is masked). Optionally set a Model override.
4. Click Save key. The status line confirms: "✓ Configured — calls go directly to <provider>, never to DosanjhLabs."
5. To remove it later, click Forget key — it's wiped from local storage.

The three flows

1. Draft a doc from notes

1. Open the AI panel and choose a document Type (runbook, server asset page, network note, SOP/procedure, or onboarding checklist).
2. Paste bullet Notes — no passwords; link a vault item instead.
3. Click Draft it.
4. Ledger creates a new page from the AI's Markdown (tagged ai-drafted, placed in Runbooks) and opens it in the editor. Review it before keeping it — AI output is advisory.

2. Summarize the open page

1. Open a document.
2. In the AI panel, click Summarize "<title>".
3. A 2–3 sentence TL;DR appears in the panel (marked AI-drafted). It doesn't modify your page.

3. Ask your docs

1. In the AI panel, type a question (e.g. "how do I restore internet after an outage?").
2. Click Ask.
3. Ledger retrieves the most relevant pages from your KB, sends only those excerpts, and the answer comes back with the page paths it used cited. If your docs don't contain the answer, it says so rather than inventing one.

The secret scrubber

Even though Ledger stores no secrets, you could still paste one into a prompt. Before any request leaves your browser, a scrubber checks the text for secret/PII patterns: password:, secret:, api_key:, provider keys (sk-…), PEM private keys, US Social Security numbers, and email addresses.

• For the draft flow (your free-text notes), if the scrubber detects a likely secret it blocks the request and tells you what it found, so you can remove it (and link a vault item) before retrying.
• Detected patterns are redacted (replaced with [redacted]) so they never reach the provider.

This reinforces the no-secrets posture: the AI helps you write documentation without ever transmitting a credential.

Cost & privacy notes

• You pay the provider directly for usage at their rates — DosanjhLabs is not in the loop and bills you nothing for AI.
• The content you send (notes, the open page, or retrieved excerpts) goes to your chosen provider under their privacy terms. Don't send anything you wouldn't send that provider.
• AI output is advisory — always review drafts and answers before adopting them. Drafts are tagged ai-drafted so they're easy to find and vet.

Related topics

• The no-secrets posture
• Security & privacy
• Troubleshooting: AI errors