Update wiki-vector-chat skill with VectorDB field fix notes
Document the content vs text field mismatch and API key error handling. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This commit is contained in:
@@ -109,6 +109,14 @@ Preset providers get forked as `custom-*` when edited (with API key).
|
||||
| Provider management | ✅ | CRUD, preset forking, API keys |
|
||||
| Odysseus UI | ✅ | Tokyo Night palette, sidebar, bubbles |
|
||||
|
||||
## Known Issues (Fixed)
|
||||
|
||||
### VectorDB field mismatch (FIXED v2.0.0)
|
||||
The vector-db API returns message content in a top-level `content` field with `author`/`channel` also top-level (not nested under `metadata`). The backend must read `content` not `text`, and `author` directly not from `metadata`.
|
||||
|
||||
### Missing API key error (FIXED v2.0.0)
|
||||
Preset providers without API keys returned cryptic HTTP 401. Now shows clear guidance to add a key via the UI.
|
||||
|
||||
## Nginx Config
|
||||
|
||||
Located at `/etc/nginx/sites-enabled/claw.rommark.dev`:
|
||||
|
||||
Reference in New Issue
Block a user