Ocassional Json parse error

[mko237]

Hello,

thanks for the great tool!

Not certain on providing an exact reproduction but facing an issue occasionally which prevents lore from working for me.

the message i receieve is:

data: {
  message: "Agent not found: \"lore-distill\". Available agents: build, explore, general, plan",
},

      at <anonymous> (/$bunfs/root/src/cli/cmd/tui/worker.js:402208:27)
      at ~effect/Effect/successCont (/$bunfs/root/src/cli/cmd/tui/worker.js:10669:32)
      at runLoop (/$bunfs/root/src/cli/cmd/tui/worker.js:10495:109)
      at evaluate (/$bunfs/root/src/cli/cmd/tui/worker.js:10465:32)
      at <anonymous> (/$bunfs/root/src/cli/cmd/tui/worker.js:10627:26)

[lore] distillation error: SyntaxError: JSON Parse error: Unexpected EOF

current .lore.json is:

{
  "knowledge": { "enabled": true },
  "curator": {
    "enabled": true,
    "onIdle": true,
    "afterTurns": 10,
    "maxEntries": 25
  },
  "agentsFile": {
    "enabled": true,
    "path": "AGENTS.md"
  },
  "budget": {
    "distilled": 0.20,
    "raw": 0.5,
    "output": 0.20,
    "ltm": 0.10
  },
  "distillation": {
    "minMessages": 8,
    "maxSegment": 50
  },
  "pruning": {
    "retention": 120,
    "maxStorage": 1024
  },
  "crossProject": true
}

and i'm currently running opencode --version 1.4.3

I'm happy to provide any additional information to help troubleshoot.

Any help would be greatly appreciated!
Thanks!

[BYK]

Thanks for the detailed report! I've traced this to two related issues and pushed a fix in #67:

Root cause: OpenCode can occasionally lose plugin agent registrations (e.g. lore-distill, lore-curator) after a config re-read, causing session.prompt({ agent: "lore-distill" }) to fail. The JSON Parse error: Unexpected EOF is a downstream effect — when the prompt is rejected, the SDK receives a malformed/truncated response.

What the fix does:

1. Uses the session.prompt() return value directly instead of ignoring it and making a separate session.messages() call — so errors are detected at the source.
2. Retries without the agent parameter when "agent not found" is detected. The system prompt is already embedded in the message text, so the retry works correctly even without the agent config.
3. Adds defensive JSON parsing for distillation DB reads, preventing a secondary crash path.

This should eliminate both error messages you were seeing. The fix will ship in the next release — in the meantime you can install from git if you'd like to test early.

[BYK]

Follow-up: also found a related issue where tool outputs (bash, grep, read commands) containing binary file content can include unpaired Unicode surrogates. These survive into the temporal messages DB and cause The request body is not valid JSON: no low surrogate in string when the recall tool includes them in results.

Fixed in #68 — sanitizes surrogates at both ingestion (temporal storage) and output (recall formatting).

[BYK]

New version out with fixes! Sorry I missed this earlier :)