Skip to content

5.0.2

Choose a tag to compare

@DuckTapeKiller DuckTapeKiller released this 30 Jul 20:06
· 36 commits to main since this release

Dive 5.0.2

llama.cpp router support now works without configuration

Preset sync previously had to be enabled by hand, with two .ini paths and two LaunchAgent labels typed into settings. All four defaulted to empty, so on a fresh install the feature did nothing.

Dive now reads the preset file and models directory from the running llama-server process, and restarts it by signal — launchd's KeepAlive brings it back. The five settings fields are gone; the MODELS tab reports the routers it detected instead. If no router is running, Dive manages its own servers as before and none of this applies.

Downloading a model now writes it into the router's preset and restarts the router, so it is usable immediately. Deleting one removes its entry the same way.

Fixed

  • The CONTEXT slider was ignored for any model served by a router, which loaded at its trained maximum instead. On a small model with a very long context window this could request more memory than the machine had. The chosen context is now written into the preset, capped at the model's trained maximum.
  • The token counter now follows the slider rather than lagging a reload behind it.
  • Embedding models could not be loaded or unloaded from the MODELS tab when their preset section was named for something other than the file. Loading failed outright; unloading reported success while leaving the model resident. Models are now matched by file path rather than by name.
  • Tool calling failed on models whose preset lacked a Jinja chat template. jinja is now written into generated sections, and the fallback that drops native tools correctly recognises llama.cpp's error.
  • Dive could take the router's port during a restart, leaving the router unable to rebind and serving one model where the preset served several. Loads now wait for the restart to finish.

Added

  • MERGE SYSTEM PROMPTS, a per-model option under ADVANCED, off by default. Dive normally sends the assistant policy, database context and skills policy as separate system messages. Some chat templates reject any system message after the first and fail the request; enable this for those models only.

Changed

  • New models start at 20480 context instead of 4096. Existing models keep their saved value.

Upgrading

Nothing to do. Any preset paths and LaunchAgent labels previously saved are ignored and removed from the config on next save. Preset files are backed up before first modification.