open-notebook/docs/3-USER-GUIDE/index.md
Luis Novo 3f352cfcce
feat: credential-based API key management (#477) (#540)
* feat: replace provider config with credential-based system (#477)

Introduce a new credential management system replacing the old
ProviderConfig singleton and standalone Models page. Each credential
stores encrypted API keys and provider-specific configuration with
full CRUD support via a unified settings UI.

Backend:
- Add Credential domain model with encrypted API key storage
- Add credentials API router (CRUD, discovery, registration, testing)
- Add encryption utilities for secure key storage
- Add key_provider for DB-first env-var fallback provisioning
- Add connection tester and model discovery services
- Integrate ModelManager with credential-based config
- Add provider name normalization for Esperanto compatibility
- Add database migrations 11-12 for credential schema

Frontend:
- Rewrite settings/api-keys page with credential management UI
- Add model discovery dialog with search and custom model support
- Add compact default model assignments (primary/advanced layout)
- Add inline model testing and credential connection testing
- Add env-var migration banner
- Update navigation to unified settings page
- Remove standalone models page and old settings components

i18n:
- Update all 7 locale files with credential and model management keys

Closes #477

Co-Authored-By: JFMD <git@jfmd.us>
Co-Authored-By: OraCatQAQ <570768706@qq.com>

* fix: address PR #540 review comments

- Fix docs referencing removed Models page
- Fix error-handler returning raw messages instead of i18n keys
- Fix auth.py misleading docstring and missing no-password guard
- Fix connection_tester using wrong env var for openai_compatible
- Add provision_provider_keys before model discovery/sync
- Update CLAUDE.md to reflect credential-based system
- Fix missing closing brace in api-keys page useEffect

* fix: add logging to credential migration and surface errors in UI

- Add comprehensive logging to migrate-from-env and
  migrate-from-provider-config endpoints (start, per-provider
  progress, success/failure with stack traces, final summary)
- Fix frontend migration hooks ignoring errors array from response
- Show error toast when migration fails instead of "nothing to migrate"
- Invalidate status/envStatus queries after migration so banner updates

* docs: update CLAUDE.md files for credential system

Replace stale ProviderConfig and /api-keys/ references across 8 CLAUDE.md
files to reflect the new Credential-based system from PR #540.

* docs: update user documentation for credential-based system

Replace env var API key instructions with Settings UI credential
workflow across all user-facing documentation. The new flow is:
set OPEN_NOTEBOOK_ENCRYPTION_KEY → start services → add credential
in Settings UI → test → discover models → register.

- Rewrite ai-providers.md, api-configuration.md, environment-reference.md
- Update all quick-start guides and installation docs
- Update ollama.md, openai-compatible.md, local-tts/stt networking sections
- Update reverse-proxy.md, development-setup.md, security.md
- Fix broken links to non-existent docs/deployment/ paths
- Add credentials endpoints to api-reference.md
- Move all API key env vars to deprecated/legacy sections

* chore: bump version to 1.7.0-rc1

Release candidate for credential-based provider management system.

* fix: initialize provider before try block in test_credential

Prevents UnboundLocalError when Credential.get() throws (e.g.,
invalid credential_id) before provider is assigned.

* fix: reorder down migration to drop index before table

Removes duplicate REMOVE FIELD statement and reorders so the index
is dropped before the table, preventing rollback failures.

* refactor: simplify encryption key to always derive via SHA-256

Remove the dual code path in _ensure_fernet_key() that detected native
Fernet keys. Since the credential system is new, always deriving via
SHA-256 removes unnecessary complexity. Also removes the generate_key()
function and Fernet.generate_key() references from docs.

* fix: correct mock patch targets in embedding tests and URL validation

Fix embedding tests patching wrong module path for model_manager
(was targeting open_notebook.utils.embedding.model_manager but it's
imported locally from open_notebook.ai.models). Also fix URL validation
to allow unresolvable hostnames since they may be valid in the
deployment environment (e.g., Azure endpoints, internal DNS).

* feat: add global setup banner for encryption and migration status

Show a persistent banner in AppShell when encryption key is missing
(red) or env var API keys can be migrated (amber), so users see
these prompts on every page instead of only on Settings > API Keys.

Includes a docs link for the encryption banner and i18n support
across all 7 locales.

* docs: several improvements to docker-compose e env examples

* Update README.md

Co-authored-by: cubic-dev-ai[bot] <191113872+cubic-dev-ai[bot]@users.noreply.github.com>

* docs: fix env var format in README and update model setup instructions

Align the encryption key snippet in README Step 2 with the list
format used in the compose file. Replace deprecated "Settings →
Models" instructions with credential-based Discover Models flow.

* fix: address credential system review issues

- Fix SSRF bypass via IPv4-mapped IPv6 addresses (::ffff:169.254.x.x)
- Fix TTS connection test missing config parameter
- Add Azure-specific model discovery using api-key auth header
- Add Vertex static model list for credential-based discovery
- Fix PROVIDER_DISCOVERY_FUNCTIONS incorrect azure/vertex mapping
- Extract business logic to api/credentials_service.py (service layer)
- Move credential Pydantic schemas to api/models.py
- Update tests to use new service imports and ValueError assertions

* fix: sanitize error responses and migrate key_provider to Credential

- Replace raw exception messages in all credential router 500 responses
  with generic error strings (internal details logged server-side only)
- Refactor key_provider.py to use Credential.get_by_provider() instead
  of deprecated ProviderConfig.get_instance()
- Remove unused functions (get_provider_configs, get_default_api_key,
  get_provider_config) that were dead code

---------

Co-authored-by: JFMD <git@jfmd.us>
Co-authored-by: OraCatQAQ <570768706@qq.com>
2026-02-10 08:30:22 -03:00

6.5 KiB

User Guide - How to Use Open Notebook

This guide covers practical, step-by-step usage of Open Notebook features. You already understand the concepts; now learn how to actually use them.

Prerequisite: Review 2-CORE-CONCEPTS first to understand the mental models (notebooks, sources, notes, chat, transformations, podcasts).


Start Here

Interface Overview

Learn the layout before diving in. Understand the three-panel design and where everything is.


Eight Core Features

1. Adding Sources

How to bring content into your notebook. Supports PDFs, web links, audio, video, text, and more.

Quick links:

  • Upload a PDF or document
  • Add a web link or article
  • Transcribe audio or video
  • Paste text directly
  • Common mistakes + fixes

2. Working with Notes

Creating, organizing, and using notes (both manual and AI-generated).

Quick links:

  • Create a manual note
  • Save AI responses as notes
  • Apply transformations to generate insights
  • Organize with tags and naming
  • Use notes across your notebook

3. Chat Effectively

Have conversations with AI about your sources. Manage context to control what AI sees.

Quick links:

  • Start your first chat
  • Select which sources go in context
  • Ask effective questions
  • Use follow-ups productively
  • Understand citations and verify claims

4. Creating Podcasts

Convert your research into audio dialogue for passive consumption.

Quick links:

  • Create your first podcast
  • Choose or customize speakers
  • Select TTS provider
  • Generate and download
  • Common audio quality fixes

5. Search Effectively

Two search modes: text-based (keyword) and vector-based (semantic). Know when to use each.

Quick links:

  • Text search vs vector search (when to use)
  • Running effective searches
  • Using the Ask feature for comprehensive answers
  • Saving search results as notes
  • Troubleshooting poor results

6. Transformations

Batch-process sources with predefined templates. Extract the same insights from multiple documents.

Quick links:

  • Built-in transformation templates
  • Creating custom transformations
  • Applying to single or multiple sources
  • Managing transformation output

7. Citations

Verify AI claims by tracing them back to source material. Understand the citation system.

Quick links:

  • Reading and clicking citations
  • Verifying claims against sources
  • Requesting better citations
  • Saving cited content as notes

8. API Configuration

Configure AI provider API keys directly through the Settings UI.

Quick links:

  • Add API keys without editing files
  • Test provider connections
  • Migrate from environment variables
  • Manage Azure and OpenAI-compatible providers
  • Understand key storage and encryption

Which Feature for Which Task?

Task: "I want to explore a topic with follow-ups"
→ Use: Chat (add sources, select context, have conversation)

Task: "I want one comprehensive answer"
→ Use: Search / Ask (system finds relevant content)

Task: "I want to extract the same info from many sources"
→ Use: Transformations (define template, apply to all)

Task: "I want summaries of all my sources"
→ Use: Transformations (with built-in summary template)

Task: "I want to share my research in audio form"
→ Use: Podcasts (create speakers, generate episode)

Task: "I want to find that quote I remember"
→ Use: Search / Text Search (keyword matching)

Task: "I'm exploring a concept without knowing exact words"
→ Use: Search / Vector Search (semantic similarity)

Task: "I need to add or change my AI provider API keys"
→ Use: Settings / API Keys (configure providers without editing files)

Quick-Start Checklist: First 15 Minutes

Step 1: Create a Notebook (1 min)

  • Name: Something descriptive ("Q1 Market Research", "AI Safety Papers", etc.)
  • Description: 1-2 sentences about what you're researching
  • This is your research container

Step 2: Add Your First Source (3 min)

  • Pick one: PDF, web link, or text
  • Follow Adding Sources
  • Wait for processing (usually 30-60 seconds)

Step 3: Chat About It (3 min)

  • Go to Chat
  • Select your source (set context to "Full Content")
  • Ask a simple question: "What are the main points?"
  • See AI respond with citations

Step 4: Save Insight as Note (2 min)

  • Good response? Click "Save as Note"
  • Name it something useful ("Main points from source X")
  • Now you have a captured insight

Step 5: Explore More (6 min)

  • Add another source
  • Chat about both together
  • Ask a question that compares them
  • Follow up with clarifying questions

Done! You've used the core workflow: notebook → sources → chat → notes


Common Mistakes to Avoid

Mistake Problem Fix
Adding everything to one notebook No isolation between projects Create separate notebooks for different topics
Expecting AI to know your context Questions get generic answers Describe your research focus in chat context
Forgetting to cite sources You can't verify claims Click citations to check source chunks
Using Chat for one-time questions Slower than Ask Use Ask for comprehensive Q&A, Chat for exploration
Adding huge PDFs without chunking Slow processing, poor search Break into multiple smaller sources if possible
Using same context for all chats Expensive, unfocused Adjust context level for each chat
Ignoring vector search Only finding exact keywords Use vector search to explore conceptually

Next Steps

  1. Follow each guide in order (sources → notes → chat → podcasts → search)
  2. Create your first notebook with real content
  3. Practice each feature with your own research
  4. Return to CORE-CONCEPTS if you need to understand the "why"

Getting Help


Ready to start? Pick the guide for what you want to do first!