retoorandClaude Sonnet 5
9dbd1fe667
- Plexer: always-active terminal multiplexing. NativePlexerController/ TmuxPlexerController share one interface, chosen by which env var is already set (TAI_PLEXER_SOCKET vs TMUX_PANE); NativePlexerBackend is the pty.fork()-based wrapper (raw mode, SIGWINCH resize forwarding, a Unix-socket control protocol, continuous session logging, a Ctrl+A prefix key distinct from tmux's own Ctrl+B). Auto-wraps new interactive shells via a .bashrc hook mirroring the existing command-not-found install pattern, gated on $TMUX/$TAI_PLEXER_ACTIVE/ a $HOME/.tai-no-plexer bypass. New plexer_send/read/type/status tools, env-gated on a detected controller. - tests/container.py + docker-compose.yml + tests/docker/Dockerfile: a disposable podman/docker image for the tests that must never touch a real machine (installing the plexer hook into a real ~/.bashrc, a live tmux session). Required suite (test_seal.py, test_tai.py, tests/plexer.py, tests/bashrc.py) gates the result; tests/rag.py runs as best-effort since its real-LLM dependency can't be satisfied inside a disposable container with no nested engine. - tests/bashrc.py: real end-to-end hook install + bash -i auto-wrap, anti-recursion, tmux-active skip, non-interactive skip, a live TmuxPlexerController test, and an install/uninstall round-trip. - tests/plexer.py: NativePlexerBackend under a real pty, plus a dedicated robustness pass (file permissions, >64KB payload framing, a malformed control request, a genuine self-deadlock fix in the write-to-child path). - tai_test.py: the shared async process-driving framework (pipe/pty transport, group-wide kill-and-reap, a StdinBridge for --interactive) both test files build on. - ChatClient last-resort backend: when there's no local opencode CLI but the sandbox box is already running, install opencode into it (official Node tarball, not apt -- apt's nodejs/npm pull in webpack/babel/jest as transitive deps) and route through it instead of giving up. Only reachable after the first retry round already failed everything else; never creates the box itself. TmuxPlexerController.status() fixed to use `list-panes` instead of `display-message -p`, which silently fell back to the default pane instead of erroring against a dead target. - Fix 4 pre-existing test_tai.py bugs surfaced by running it in a clean environment for the first time: two stale mock signatures (subprocess.run's stdout= kwarg, Chat.complete's deadline= kwarg), one $TMUX-dependent catalog assertion, one tty-dependent color assertion. - research/: a sourced research archive (Source Dossier/Citation Card/Conclusion tiers) backing the above design decisions, with its own audit.py consistency checker. - .gitignore: fix a blanket *.md rule that was about to silently drop the entire research/ archive from version control; add __pycache__/ and the one-off debug transcript this session started from. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
49 lines
2.3 KiB
Markdown
49 lines
2.3 KiB
Markdown
# SQLite as a Vector DB: A Guide to Isolated Local-First RAG
|
|
|
|
## Metadata
|
|
|
|
| Field | Value |
|
|
|---|---|
|
|
| Institute | Molodetz Institute — Research & Retrieval Division |
|
|
| Subject | sqlite-rag-hybrid-search |
|
|
| Document type | Source Dossier |
|
|
| Tier | 1 |
|
|
| Source title | SQLite as a Vector DB: A Guide to Isolated Local-First RAG |
|
|
| Source URL | https://www.talentica.com/blogs/sqlite-vector-database/ |
|
|
| Source publisher / author | Talentica Software (vendor blog) |
|
|
| Source type | blog post |
|
|
| Source date (published) | Unknown — not stated |
|
|
| Date researched | 2026-10-09 |
|
|
| Researched by | tai (agent), model: Claude Sonnet 5, on behalf of retoor |
|
|
| Research method | web search synthesis |
|
|
| Confidence | Low |
|
|
| Status | Active |
|
|
|
|
## Summary
|
|
|
|
A vendor/consultancy blog post pitching SQLite (via a vector extension) as a viable local-first vector database for RAG applications that need isolation (e.g. per-tenant or per-device databases) rather than a shared cloud vector store.
|
|
|
|
## Key findings
|
|
|
|
- Frames SQLite-as-vector-DB primarily around the "local-first / isolated" use case — single-file portability and no shared infrastructure — rather than around raw performance claims.
|
|
- Reinforces, from a different commercial angle than `alexgarcia-sqlite-vec-hybrid-search.md`, that a vector extension is a prerequisite for this pattern.
|
|
|
|
## Pros / strengths
|
|
|
|
- Useful as a second, independent voice confirming that "SQLite as the whole RAG backend" is being discussed industry-wide in 2024/2025-era content, not just by extension authors and hobbyists.
|
|
|
|
## Cons / limitations / caveats
|
|
|
|
- A consultancy/vendor marketing post; it is implicitly selling the author's own integration services, so claims should be weighted lower than a neutral or primary-source account.
|
|
- No benchmark data, no specific extension-version detail, and no code was independently verified during this research pass.
|
|
|
|
## Relevance to tai
|
|
|
|
Contributed mainly as corroborating context that "SQLite + vector extension" is a recognized industry pattern, which strengthened confidence that the *rejection* of vectors in `conclusions/no-vectors-bm25-chunked-rag.md` was a deliberate tradeoff against a real, viable alternative — not a decision made in ignorance of one.
|
|
|
|
## Changelog
|
|
|
|
| Date | Change |
|
|
|---|---|
|
|
| 2026-10-09 | Initial dossier created. |
|