Skip to content
This repository was archived by the owner on Sep 21, 2026. It is now read-only.

JevSeek v0.2.1 — follow-up execution hotfix

Choose a tag to compare

View all tags
@morcoan morcoan released this 18 Sep 15:49
v0.2.1
3e1a4af

JevSeek v0.2.1 — follow-up and premature-completion hotfix

Fixed

  • Preserves the previous assistant response as explicitly labeled conversation, so “proceed” can refer to offered work. Assistant claims are never treated as execution evidence.
  • Reviews a proposed done against the current request and recorded effects. When work remains, Jev selects a relevant tool instead of immediately emitting an inactivity summary.
  • Tells the response generator not to invent an inability to use tools just because none ran. Ordinary conversational questions can still finish without tools.
  • Shows completion review in live activity and records its API usage.

Included in this release

This packages the existing local v0.2.0 Bonsai implementation plus the hotfix, hence v0.2.1 rather than v0.1.1. Settings → Generation model offers the official Prism or community CRACK Bonsai model, with automatic downloads, progress, integrity checks and DeepSeek switchback. Bonsai replaces DeepSeek generation; Jev still requires a key and receives routing context. Model files download separately (~7.2 GB each). Existing sessions and keys are preserved. JevSeek's MIT license notice is included in the EXE.

Updating

Close JevSeek, replace the old executable with JevSeek.exe, and reopen it. Use the new EXE—not an older shortcut pointing elsewhere. Your saved history and credentials remain in their existing Windows locations. To continue the affected conversation, send a new follow-up message; simply reopening history deliberately does not execute work.

Windows x64, unsigned. Python/Node are not needed to run the app; project-specific developer tools are separate. Verify the download against SHA256SUMS.txt. Do not disable Windows security protections. Microsoft WebView2 terms/privacy apply. See the repository's release and security documentation.

Scope and verification

The failure was diagnosed from actual session events: immediate done selections with no tool calls, combined with missing prior assistant context. This release was compiled and its source and decompressed package audited for private data. No new test suite, live-model check or benchmark was run for this hotfix, at the owner's request. Earlier Bonsai/runtime validation predates this change. Completion review is model-based, adds Jev latency/API cost, and is not a guarantee that every model decision will be correct. Historical research results describe the earlier routing policy.

The cancelled Terminal-Bench run, VM, private logs, API keys and local sessions are not included or restarted.

Assets 5
Loading