A CLI tool and lightweight WebUI that extracts course content (PDFs, DOCX, PPTX, VTT transcripts, IMSCC exports, plus Markdown/Quarto, HTML and plain text), classifies it, and uploads to an AnythingLLM workspace for embedded chatbots.
- Folder-first scanning — point at a folder, BotStash figures out the rest
- Multi-format extraction — PPTX, DOCX, PDF, VTT, QTI quizzes, IMSCC exports, Markdown/Quarto (
.md/.qmd), HTML (.html/.htm), plain text (.txt) - Recursive ZIP handling — nested ZIPs and IMSCC archives are auto-detected
- Structured unit outline parsing — extracts assessments, schedules, learning outcomes with Bloom's taxonomy
- Auto-classification — heuristic tagging of content types (lecture, worksheet, assignment, etc.)
- AnythingLLM integration — uploads documents, manages workspaces, retrieves embed code
- WebUI — FastAPI + Jinja2 interface for non-terminal users
pip install botstash# Full pipeline — point at a folder
botstash run ./course-materials/ --workspace ISYS2001
# Update an existing workspace cleanly (clears old docs first — no duplicates)
botstash run ./course-materials/ --workspace ISYS2001 --reset
# Two-step workflow (extract, review, embed)
botstash extract ./course-materials/ --output ./staging/
# ... review staging/tags.json ...
botstash embed ./staging/ --workspace ISYS2001
# Get the embeddable chatbot code for a workspace
botstash chatbot ISYS2001
# Include quiz answer choices
botstash extract ./folder/ --include-answers
# Non-recursive (top-level only)
botstash extract ./folder/ --no-recursive
# Launch WebUI
botstash serve| Command | Purpose |
|---|---|
run |
Full extract → classify → embed pipeline in one step |
extract |
Extract and auto-classify a folder into a staging directory |
embed |
Upload a staging directory into an AnythingLLM workspace |
chatbot |
Retrieve the embeddable chatbot code for a workspace |
persona |
Provision in-character persona chatbots from a manifest |
init |
Scaffold a .botstash.env config file (--global for ~/.botstash.env) |
serve |
Launch the FastAPI WebUI |
Run botstash <command> --help for the full option list.
BotStash can also provision multiple in-character persona bots (a simulated organisation's staff, for example) from a manifest. Each persona gets its own workspace, a system-prompt identity, a personal backstory plus any shared documents, and an embed widget whose id is written back into the persona's page file.
# personas.json lists personas (slug, prompt, backstory, page), shared docs, allowlist_domains
botstash persona personas.json --url http://localhost:3001 --key $ANYTHINGLLM_KEY
# Re-run cleanly (--reset clears each workspace's documents first)
botstash persona personas.json --resetManifest schema (paths resolve relative to the manifest file):
{
"shared_docs": ["company_overview.md"],
"allowlist_domains": ["example.org"],
"personas": [
{"slug": "priya_nair", "prompt": "bots/priya_nair/prompt.txt",
"backstory": "_backstories/priya_nair_cfo.md",
"page": "bots/priya_nair/index.qmd"}
]
}Settings are resolved in priority order:
CLI flag > environment variable > local .botstash.env > global ~/.botstash.env
A global ~/.botstash.env in your home directory provides defaults for every
project; a local .botstash.env in the current directory overrides it per key.
# Scaffold a local config file in the current directory
botstash init
# Scaffold a global config file at ~/.botstash.env (defaults for every project)
botstash init --global.botstash.env (local or global — same format):
ANYTHINGLLM_URL=http://localhost:3001
ANYTHINGLLM_KEY=your-api-key
INCLUDE_ANSWERS=false
RECURSIVE=true
git clone https://github.com/michael-borck/botstash.git
cd botstash
uv sync --dev
uv run ruff check src/ tests/
uv run pytestMIT