github Hmbown/DeepSeek-TUI v0.8.36

7 hours ago

Install

Recommended — npm (one command, both binaries)

npm install -g deepseek-tui

The wrapper downloads both binaries from this Release and places them in the same directory.

Docker / GHCR

docker run --rm -it \
  -e DEEPSEEK_API_KEY="$DEEPSEEK_API_KEY" \
  -v ~/.deepseek:/home/deepseek/.deepseek \
  ghcr.io/hmbown/deepseek-tui:v0.8.36

The image ships the deepseek dispatcher and deepseek-tui runtime. The latest tag is also updated on release.

Cargo (Linux / macOS)

cargo install deepseek-tui-cli deepseek-tui --locked

Manual download

Both binaries must be downloaded for your platform and dropped into the same directory. See the release assets above.


Changelog: v0.8.36 (2026-05-14)

A cache-hygiene and UX polish release focused on leaner sub-agent handoffs, sidebar visibility control, and improved RLM batch safety.

Added

  • The right sidebar can be hidden for copy-friendly terminals.
    sidebar_focus = "hidden" (or Ctrl+Alt+0 for the current session) removes
    the Work/Tasks/Agents/Context rail so raw terminal selection cannot copy
    sidebar borders alongside transcript text.

Changed

  • Sub-agent completion handoffs are leaner and more cache-friendly.
    Internal <deepseek:subagent.done> sentinels now point to the preceding
    human summary line instead of duplicating the summary, elapsed time, and
    step count inside JSON sent to the parent model.
  • Prefix stability is visible beside cache telemetry by default. The
    footer now includes the prefix-stability chip in the default status layout,
    and low last-request cache hit rates are no longer colored as hard errors
    when the system/tool prefix itself is stable.
  • RLM batch helpers now require an explicit independence assertion.
    sub_query_batch, sub_query_map, and low-level *_batched helpers refuse
    dependency-unsafe parallel fanout unless callers pass
    dependency_mode="independent", and RLM now exposes sub_query_sequence
    for A-to-B dependent work.

Fixed

  • Mutex poisoning handling in InMemoryKeyringStore. Lock poison errors
    are now propagated as SecretsError::Keyring instead of causing panics.

Contributors

No new external contributors in this release cycle.

Don't miss a new DeepSeek-TUI release

NewReleases is sending notifications on new releases.