Buddy v0.1.26
Faster boot after version upgrades
Buddy could crash on first launch after upgrading to a version with nested documentation files (like v0.1.25). The worker tried to write files into a subdirectory that didn't exist yet, and the process exited before the frontend could connect — showing "Worker exited (code 1)" with no useful explanation.
What you could see
-
"Worker exited (code 1)" on first launch after updating. The worker crashed while deploying new documentation files into
~/.buddy/docs/memory/. Pressing Restart usually worked because the directory had been partially created, but the experience was jarring. Now the worker creates intermediate directories before writing. -
Slower startup on version upgrades. Documentation files were deployed before the RPC channel was ready, blocking the frontend connection. Now only prompts (needed for session creation) are deployed at boot; documentation is deployed after the channel is up, so the app window appears faster.
What changed underneath
Boot refresh is now split: bootRefreshIfNeeded deploys prompts only (4 small files, needed for system prompt assembly), and bootDeployDocs runs after the RPC channel connects. The deployMarkdownFiles function now creates parent directories for nested paths. A retry-reflect.ts script was also added for manually re-running a failed session-end reflect from its saved fork file.
1001 unit tests and 341 scenarios.