Impressive reasoning on the project scaffold, but where is the "Dream" state stored?

[A561988]

Ive been stress-testing the local gateway on Windows 11 and I’m genuinely surprised by the code generation quality. I had it scaffold a full Express.js API with JWT and Zod validation, and it built all 13 files in a single turn without the usual hallucinations I see in other local-first wrappers.I see the "Dream Engine" in the sidebar, but it’s showing as a shell for me right now.

Is the plan to store the crystallized reasoning traces in a local vector store, or are we moving toward a more structured SQLite-based memory manifest?Also, if anyone has managed to get a clean Electron build from source, I’d love to know your Rollup config tweaks. I’m hitting some regex issues on the entry module and had to fall back to the web UI.Really cool to see a P2P mesh that actually has 200+ nodes live. Keep it up.

[VGIL77]

Great question. Short version — everything is SQLite, no separate vector store.

Where dreams live:

• dream_cycles table — one row per cycle (modes used, LLM calls, timing, chunks analyzed, errors)
• dream_insights table — generated insights linked to the parent cycle by dream_cycle_id
• chunks table — the main memory store. Crystallized skills have lifecycle = crystallized
• chunks_vec (sqlite-vec) — embeddings stored as BLOBs, queried via KNN for semantic recall. FTS5 for lexical. RRF fuses them in retrieval.
• MEMORY.md on disk — working memory (Phenotype, Bond, Niche, Active Context) gets rewritten every cycle from the cycles outputs

All in ~/.bitterbot/memory.sqlite (or workspace-specific if configured). Nothing goes to an external vector DB.

On the Dream Engine showing as a shell — thats normal on a fresh install. Dreams run every 2 hours by default; the first cycle needs accumulated chunks to have anything to consolidate. You can trigger one manually once you have some chat history: bitterbot dream --now (or via the Control UIs Dream panel).

On Electron — were on Tauri 2, not Electron. See desktop/TAURI.md for the build. System webview + Rust, no Rollup. That might save you some regex debugging.

Thanks for the kind words on the scaffolding.