a04a16c717
HAIKU_RAG_DB and DB_PATH are gone: a capability covers what the configuration places or the db_path it is given, and the app backend and the AG-UI example load their configuration as the CLI does. The compose files point HAIKU_RAG_CONFIG_PATH at the mounted haiku.rag.yaml, which places the database at /data where DB_VOLUME is mounted; the backend refuses a configured set since it serves one database. The chat scopes a selection by source only over a set and names databases on filter rows only across several. Docstrings, docs and test fixtures stop describing an unnamed database; every database a search, listing or citation reports carries a name. |
||
|---|---|---|
| .. | ||
| docker | ||
| samples | ||
| custom_agent.py | ||
| custom_agent_agui.py | ||
| README.md | ||
haiku.rag Examples
This directory contains example scripts demonstrating various features of haiku.rag.
Docker Example
Directory: docker/
Complete Docker setup for running haiku.rag with all services:
- Continuous ingestion from a watched directory via
haiku-ingester - MCP server for AI assistant integration
See docker/README.md for setup instructions.
Custom Agent
Script: custom_agent.py
Uses the eagerly loaded RAG capability to build a conversational agent.
uv run python examples/custom_agent.py /path/to/db.lancedb
Custom Agent with AG-UI Streaming
Script: custom_agent_agui.py
A Starlette app that adapts a native RAG-capable agent to AG-UI. The configuration places the database (HAIKU_RAG_CONFIG_PATH, or ./haiku.rag.yaml):
uv run uvicorn examples.custom_agent_agui:app --reload --port 8000