Environment
- OS: Windows (platform string: mingw64_nt-10.0-26200/amd64)
- Shell: PowerShell
- Lumen: v0.0.41 (installed as Claude Code plugin, lumen@ory)
- Ollama: 0.24.0, model ordis/jina-embeddings-v2-base-code (768 dims), on localhost:11434
What happens
lumen index . walks the project (658 files), reports them detected
(e.g. "637 added, 21 modified"), runs for several minutes, then ends with:
Done. Indexed 0 files, 0 chunks. Every run produces zero chunks.
What I've ruled out
- Binary runs fine: lumen-windows-amd64.exe prints help/commands correctly.
- Ollama embedding works directly: POST /api/embeddings with the same model
returns a valid 768-dim embedding vector.
- No index DB is created anywhere — checked %LOCALAPPDATA%\lumen,
%APPDATA%\lumen, and ~/.local/share/lumen: all empty/nonexistent.
- Forcing a writable data dir (set XDG_DATA_HOME to a real folder) +
--force
still produces 0 files, 0 chunks.
- LUMEN_LOG=debug produced no error output — the failure is completely silent.
Also
The plugin SessionStart hook fails on startup with:
"Failed with non-blocking status code: Downloading lumen v0.0.41 for
mingw64_nt-10.0-26200/amd64" — even when the binary is already present in bin/.
So: files are read, embeddings work, but chunks are never written and no index
DB is created, with no error surfaced. Appears to be a Windows-specific
indexing/persistence bug.
Environment
What happens
lumen index .walks the project (658 files), reports them detected(e.g. "637 added, 21 modified"), runs for several minutes, then ends with:
Done. Indexed 0 files, 0 chunks. Every run produces zero chunks.What I've ruled out
returns a valid 768-dim embedding vector.
%APPDATA%\lumen, and ~/.local/share/lumen: all empty/nonexistent.
--forcestill produces 0 files, 0 chunks.
Also
The plugin SessionStart hook fails on startup with:
"Failed with non-blocking status code: Downloading lumen v0.0.41 for
mingw64_nt-10.0-26200/amd64" — even when the binary is already present in bin/.
So: files are read, embeddings work, but chunks are never written and no index
DB is created, with no error surfaced. Appears to be a Windows-specific
indexing/persistence bug.