* 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>
9.3 KiB
OpenAI-Compatible Providers
Use any server that implements the OpenAI API format with Open Notebook. This includes LM Studio, Text Generation WebUI, vLLM, and many others.
What is OpenAI-Compatible?
Many AI tools implement the same API format as OpenAI:
POST /v1/chat/completions
POST /v1/embeddings
POST /v1/audio/speech
Open Notebook can connect to any server using this format.
Common Compatible Servers
| Server | Use Case | URL |
|---|---|---|
| LM Studio | Desktop GUI for local models | https://lmstudio.ai |
| Text Generation WebUI | Full-featured local inference | https://github.com/oobabooga/text-generation-webui |
| vLLM | High-performance serving | https://github.com/vllm-project/vllm |
| Ollama | Simple local models | (Use native Ollama provider instead) |
| LocalAI | Local AI inference | https://github.com/mudler/LocalAI |
| llama.cpp server | Lightweight inference | https://github.com/ggerganov/llama.cpp |
Quick Setup: LM Studio
Step 1: Install and Start LM Studio
- Download from https://lmstudio.ai
- Install and launch
- Download a model (e.g., Llama 3)
- Start the local server (default: port 1234)
Step 2: Configure in Settings UI (Recommended)
- Go to Settings → API Keys
- Click Add Credential → Select OpenAI-Compatible
- Enter base URL:
http://host.docker.internal:1234/v1(Docker) orhttp://localhost:1234/v1(local) - API key:
lm-studio(placeholder, LM Studio doesn't require one) - Click Save, then Test Connection
Legacy (Deprecated) — Environment variables:
export OPENAI_COMPATIBLE_BASE_URL=http://localhost:1234/v1
export OPENAI_COMPATIBLE_API_KEY=not-needed
Step 3: Add Model in Open Notebook
- Go to Settings → Models
- Click Add Model
- Configure:
- Provider:
openai_compatible - Model Name: Your model name from LM Studio
- Display Name:
LM Studio - Llama 3
- Provider:
- Click Save
Configuration via Settings UI
The recommended way to configure OpenAI-compatible providers is through the Settings UI:
- Go to Settings → API Keys
- Click Add Credential → Select OpenAI-Compatible
- Enter your base URL and API key (if needed)
- Optionally configure per-service URLs for LLM, Embedding, TTS, and STT
- Click Save, then Test Connection
Legacy: Environment Variables (Deprecated)
Deprecated: These environment variables are deprecated. Use the Settings UI instead.
Language Models (Chat)
OPENAI_COMPATIBLE_BASE_URL=http://localhost:1234/v1
OPENAI_COMPATIBLE_API_KEY=optional-api-key
Embeddings
OPENAI_COMPATIBLE_BASE_URL_EMBEDDING=http://localhost:1234/v1
OPENAI_COMPATIBLE_API_KEY_EMBEDDING=optional-api-key
Text-to-Speech
OPENAI_COMPATIBLE_BASE_URL_TTS=http://localhost:8969/v1
OPENAI_COMPATIBLE_API_KEY_TTS=optional-api-key
Speech-to-Text
OPENAI_COMPATIBLE_BASE_URL_STT=http://localhost:9000/v1
OPENAI_COMPATIBLE_API_KEY_STT=optional-api-key
Docker Networking
When Open Notebook runs in Docker and your compatible server runs on the host, use the appropriate base URL when adding your credential in Settings → API Keys:
macOS / Windows
Base URL: http://host.docker.internal:1234/v1
Linux
Base URL (Option 1 — Docker bridge IP): http://172.17.0.1:1234/v1
Option 2: Use host networking mode: docker run --network host ...
Then use base URL: http://localhost:1234/v1
Same Docker Network
# docker-compose.yml
services:
open-notebook:
# ...
lm-studio:
# your LM Studio container
ports:
- "1234:1234"
Base URL in Settings → API Keys: http://lm-studio:1234/v1
Text Generation WebUI Setup
Start with API Enabled
python server.py --api --listen
Configure Open Notebook
In Settings → API Keys, add an OpenAI-Compatible credential with base URL: http://localhost:5000/v1
Docker Compose Example
services:
text-gen:
image: atinoda/text-generation-webui:default
ports:
- "5000:5000"
- "7860:7860"
volumes:
- ./models:/app/models
command: --api --listen
open-notebook:
image: lfnovo/open_notebook:v1-latest-single
pull_policy: always
depends_on:
- text-gen
Then in Settings → API Keys, add an OpenAI-Compatible credential with base URL: http://text-gen:5000/v1
vLLM Setup
Start vLLM Server
python -m vllm.entrypoints.openai.api_server \
--model meta-llama/Llama-3.1-8B-Instruct \
--port 8000
Configure Open Notebook
In Settings → API Keys, add an OpenAI-Compatible credential with base URL: http://localhost:8000/v1
Docker Compose with GPU
services:
vllm:
image: vllm/vllm-openai:latest
command: --model meta-llama/Llama-3.1-8B-Instruct
ports:
- "8000:8000"
volumes:
- ~/.cache/huggingface:/root/.cache/huggingface
deploy:
resources:
reservations:
devices:
- driver: nvidia
count: 1
capabilities: [gpu]
open-notebook:
image: lfnovo/open_notebook:v1-latest-single
pull_policy: always
depends_on:
- vllm
Then in Settings → API Keys, add an OpenAI-Compatible credential with base URL: http://vllm:8000/v1
Adding Models in Open Notebook
Via Settings UI
- Go to Settings → Models
- Click Add Model in appropriate section
- Select Provider:
openai_compatible - Enter Model Name: exactly as the server expects
- Enter Display Name: your preferred name
- Click Save
Model Name Format
The model name must match what your server expects:
| Server | Model Name Format |
|---|---|
| LM Studio | As shown in LM Studio UI |
| vLLM | HuggingFace model path |
| Text Gen WebUI | As loaded in UI |
| llama.cpp | Model file name |
Testing Connection
Test API Endpoint
# Test chat completions
curl http://localhost:1234/v1/chat/completions \
-H "Content-Type: application/json" \
-d '{
"model": "your-model-name",
"messages": [{"role": "user", "content": "Hello"}]
}'
Test from Inside Docker
docker exec -it open-notebook curl http://host.docker.internal:1234/v1/models
Troubleshooting
Connection Refused
Problem: Cannot connect to server
Solutions:
1. Verify server is running
2. Check port is correct
3. Test with curl directly
4. Check Docker networking (use host.docker.internal)
5. Verify firewall allows connection
Model Not Found
Problem: Server returns "model not found"
Solutions:
1. Check model is loaded in server
2. Verify exact model name spelling
3. List available models: curl http://localhost:1234/v1/models
4. Update model name in Open Notebook
Slow Responses
Problem: Requests take very long
Solutions:
1. Check server resources (RAM, GPU)
2. Use smaller/quantized model
3. Reduce context length
4. Enable GPU acceleration if available
Authentication Errors
Problem: 401 or authentication failed
Solutions:
1. Check if server requires API key
2. Set the API key in your credential (Settings → API Keys)
3. Some servers need any non-empty key (use a placeholder like "not-needed")
Timeout Errors
Problem: Request times out
Solutions:
1. Model may be loading (first request slow)
2. Increase timeout settings
3. Check server logs for errors
4. Reduce request size
Multiple Compatible Endpoints
You can use different compatible servers for different purposes. When adding an OpenAI-Compatible credential in Settings → API Keys, you can configure per-service URLs:
- LLM URL: e.g.,
http://localhost:1234/v1(LM Studio) - Embedding URL: e.g.,
http://localhost:8080/v1(different server) - TTS URL: e.g.,
http://localhost:8969/v1(Speaches) - STT URL: e.g.,
http://localhost:9000/v1(Speaches)
Alternatively, add each as a separate credential with its own base URL.
Performance Tips
Model Selection
| Model Size | RAM Needed | Speed |
|---|---|---|
| 7B | 8GB | Fast |
| 13B | 16GB | Medium |
| 70B | 64GB+ | Slow |
Quantization
Use quantized models (Q4, Q5) for faster inference with less RAM:
llama-3-8b-q4_k_m.gguf → ~4GB RAM, fast
llama-3-8b-f16.gguf → ~16GB RAM, slower
GPU Acceleration
Enable GPU in your server for much faster inference:
- LM Studio: Settings → GPU layers
- vLLM: Automatic with CUDA
- llama.cpp:
--n-gpu-layers 35
Comparison: Native vs Compatible
| Aspect | Native Provider | OpenAI Compatible |
|---|---|---|
| Setup | API key only | Server + configuration |
| Models | Provider's models | Any compatible model |
| Cost | Pay per token | Free (local) |
| Speed | Usually fast | Depends on hardware |
| Features | Full support | Basic features |
Use OpenAI-compatible when:
- Running local models
- Using custom/fine-tuned models
- Privacy requirements
- Cost control
Related
- Local TTS Setup - Text-to-speech with Speaches
- Local STT Setup - Speech-to-text with Speaches
- AI Providers - All provider options
- Ollama Setup - Native Ollama integration