Tags: kdeps/kdeps

Nightly release 2026-08-11-03:58

Nightly release 2026-08-10-04:10

Nightly release 2026-08-09-03:54

Nightly release 2026-08-08-03:44

Nightly release 2026-08-07-04:36

Nightly release 2026-08-06-05:31

Nightly release 2026-08-05-05:26

fix: agent loop startup hang, GGUF crash remediation, system-role fol…

…ding, /prompt command

- Bound the unbounded llmfit exec call at startup with a timeout and add a
  startup status line, fixing a silent multi-minute hang on first run.
- Fix extractTarGzSiblings to preserve symlinked sibling libraries (e.g.
  libllama-common.0.dylib), and extend macOS crash remediation to reinstall
  llama-server for any missing-dylib crash, not just libomp.
- Fold system-role messages into the leading message for local GGUF/llamafile
  backends on both the raw-map (workflow) and langchaingo (streaming/REPL)
  request paths, fixing llama-server rejecting requests outright for chat
  templates that don't support a system role (e.g. Gemma).
- Fix a data-loss bug where CacheControl-wrapped system preamble content
  (memory rules, tool guidance, skills, date) was silently dropped instead of
  folded/displayed, because langchaingo wraps cached parts in CachedContent
  rather than plain TextContent.
- Exclude mmproj (multimodal projector) files from the model harvester so
  they're never catalogued as standalone servable models.
- Soften the single-task goal directive to consider tools for time-sensitive
  queries instead of unconditionally answering from memory.
- Add /prompt and /prompt raw REPL commands showing the exact messages and
  tool definitions sent to the LLM on the last call, with local token
  estimates.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

Nightly release 2026-08-04-05:29

fix: decoy process in a Serve() test now misread as a crash

TestLlamafileManager_Serve_StartsAndBecomesHealthy spawns a "#!/bin/sh
exit 0" placeholder solely to satisfy cmd.Start() -- the actual health
endpoint it polls is a separate httptest server, unlocked 100ms later.
The new process-exit crash detection now races that: the decoy exits
in a few milliseconds, well before the 100ms health-ready delay, so it
was misread as *ServerCrashedError instead of the test ever reaching a
successful health check.

Have the decoy sleep briefly instead of exiting immediately, so it
stays alive across the health-ready window like a real (successful)
llamafile process would.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>