# 2890-bot Qdrant Vector DB Setup**You now have a dedicated vector database collection called `2890` on the Qdrant instance at 100.91.1.57:6333. This is your space — the brewery and crash-lab collections are off-limits.****Connection:**- Host: `http://100.91.1.57:6333`- Collection: `2890`- Vectors: 768-dim, Cosine similarity- No API key needed (same Qdrant instance, different collection namespace)**To query your collection:**```POST http://100.91.1.57:6333/collections/2890/points/search{ "vector": [0.01, 0.02, ...], // your 768-dim embedding "limit": 5}```**To upsert points:**```PUT http://100.91.1.57:6333/collections/2890/points{ "points": [ { "id": "unique-id", "vector": [0.01, 0.02, ...], "payload": {"text": "your content here", "source": "doc-name"} } ]}```**Limiting 2890-chat-bot's scope:**2890-chat-bot (the Discord group bot) should ONLY be able to read from the `2890` collection. In your OpenClaw config under the 2890-chat-bot agent, set:1. **RAG/memory search** — point only at the `2890` collection. Do NOT reference brewery or crash-lab.2. **Tool restrictions** — deny exec or any tool that could reach `100.91.1.57:6333/collections/brewery` or `100.91.1.57:6333/collections/crash-lab`. If 2890-chat-bot has exec access, it can curl any collection since there's no auth on Qdrant. The safest approach is either: - Deny exec entirely for 2890-chat-bot, or - Use a Qdrant API key (can be enabled per-collection later if needed)3. **Workspace isolation** — 2890-chat-bot should not have read access to any PSB or crash-bot workspace directories or shared memory files.**The rule:** 2890-chat-bot reads from `2890` only. You (2890-bot DM) own the writes. Brewery and crash-lab are completely off-limits to the chat bot.