v0.1.8 — UX polish: /status slash, next-step hints, --dir seed, qdrant pin
UX polish release between 0.1.7 (install-path stable) and 0.2.0 (GHCR image work). No behavior changes to the agent or pipeline.
New
-
`/status` REPL slash command — on-demand snapshot of backend URL + semver + sha + API version, current login (user, role, profile, FB_PROFILE env), and session totals (thread id, turn count, cumulative cost + tokens). Closes the M1 test7 gap where typing `/status` returned "Unknown slash command". Also added to the `/help` listing. (cli/slash.py)
-
Next-step hints across CLI commands — each terminal command now prints a one-line dim "Next: ..." hint after its success message:
- `financebench login` → Next: `financebench chat`
- `financebench logout` → Run `financebench login -u ` when ready
- `financebench doctor` (clean) → Next: `financebench setup`
- `financebench down` → Next: `financebench setup` (or `financebench upgrade`)
- `financebench upgrade` → Next: `financebench chat`
- `financebench setup` now ends with an explicit numbered "Next steps:" block listing the login + chat sequence with available roles inline.
-
`scripts/seed_qdrant.py --dir [--collection ]` — ingest your own PDFs into a custom Qdrant collection without editing the script:
python scripts/seed_qdrant.py --sample python scripts/seed_qdrant.py --dir ~/my-finance-pdfs/ python scripts/seed_qdrant.py --dir ~/acme-q3/ --collection acme_q3_2026
Performance caveat: the LoRA-FT reranker + tuned prompts are FinanceBench-specific, so accuracy on unrelated finance docs may differ from the 72.7% headline. Suitable for personal use / private docs, not benchmark replication.
Fixed
-
Doctor BuildKit nudge — `financebench doctor` no longer recommends `export DOCKER_BUILDKIT=1`. Modern Docker Desktop (23+) enables Buildkit by default; the nudge was confusing. Only flags now when buildx itself is missing.
-
Qdrant client version pin — `qdrant-client` pinned to `>=1.13,<1.15` to match the qdrant 1.13.2 server image. Pre-pin, pip resolved to 1.18.x and emitted a UserWarning on every call ("client 1.18.0 is incompatible with server 1.13.2 — minor version difference must not exceed 1"). Cosmetic but log-noisy. Bumping the server image is a 0.2.0-scoped decision (volume-reflow risk); pinning the client is the cheap fix.
Upgrade
pip install --upgrade financebench-rag-agent
financebench upgrade`financebench upgrade` runs `git pull` + `docker compose build` + restart + health-check, all preserving volumes. That's the recommended path for every release post-0.1.0.
Verification
- 211 KB whl / 1.0 MB sdist · `twine check` PASSED
- Fresh-venv smoke test PASSED (36 MB site-packages, no size change)
- 23 doctor unit tests pass
- `/status` slash + next-step hints visible in dev install
Next
0.2.0 — pre-built GHCR image with multi-arch CI. Cuts the ~10 minute build per release to a ~90 second pull. Sprint design already in docs/engineering-log.md §"0.2.x roadmap".