Releases: kahliburke/Kaimon.jl
Releases · kahliburke/Kaimon.jl
Release list
v2.2.0
Kaimon v2.2.0
Kaimon 2.2.0
Features
- Binary streaming transport — event-driven, wake-on-arrival stream draining
and a zero-copy raw binary frame path for high-rate streaming consumers (live
widgets/plots, KaimonSlate binary-emit), cutting stream latency and idle CPU. - Startup KaimonGate upgrade prompt — on interactive launch, offers to update
a stale registry-installed global KaimonGate so auto-connecting REPL sessions
pick up the latest gate fixes. No-op for dev/current installs; dismissals are
remembered per version; re-armed withkaimon --reset-global-prompt.
Fixes
- #67 — a raw-mode Tachikoma TUI run from a gate REPL no longer wedges the
host REPL on exit (stream guard via Tachikoma 2.4'sset_stream_guard!).
Requires
- Tachikoma 2.4, KaimonGate 1.1.
KaimonGate-v1.1.0
KaimonGate KaimonGate-v1.1.0
KaimonGate 1.1.0
Features
- Event-driven stream draining (
wait_stream_messages!) that wakes on frame
arrival instead of polling on a fixed cadence, and a zero-copy raw binary
frame path (_publish_stream_raw) that skips the Serialization envelope for
high-rate streaming consumers. Binary payloads are preserved end-to-end as bytes.
Fixes
- Register a stream guard (via Tachikoma's
set_stream_guard!) so a raw-mode
Tachikoma TUI run from a gate-hosted REPL no longer wedges the host REPL's
stdin on exit (Kaimon #67). Adds publicdisable_wedge_guard!for a host that
runs its own persistent full-screen TUI alongside the capture mux. The guard is
a no-op unless a Tachikoma new enough to define the hook is loaded.
Merged pull requests:
- Extension spawn: put Kaimon's active environment on JULIA_LOAD_PATH, not pkgdir (#61) (@mthelm85)
- Managed runtime env for registry/app-installed extensions (exposure #2) (#65) (@kahliburke)
- Fix Windows npm-shim
claudespawn + stop leaking env in spawn errors (#63) (#66) (@kahliburke)
Closed issues:
- Provide Qdrant via JLL? (lazily?) (#24)
- Can Kaimon ping claude? (#30)
- Excessive memory consumption (#33)
- Windows: ZMQ ipc:// transport not supported — TUI fails to start after /dev/tty fix (#41)
- Orphaned Gate.serve() REPLs are never reaped — multi-GB leak under headless server (#51)
- claude code bug report (#55)
- Kaimon / GLMakie interaction problems (#56)
- Kaimon writes Antigravity MCP config in wrong directory (#57)
- Kaimon should not always put a session in the background after 30s (#59)
- Registered extension
project_pathis manifest-less for registry installs, so the extension can't boot (#62) - Agent fails to spawn
claudeon Windows when the CLI is installed via npm (.ps1/.cmdshim) (#63) - False warning Julia not on path (#64)
v2.1.0
Kaimon v2.1.0
Kaimon v2.1.0
Features
- Managed (zero-Docker) Qdrant (#24): Kaimon lazily installs
Qdrant_jllinto a small Kaimon-owned environment and runs the binary itself — no Docker required. Includes TUI start/stop controls, autostart on launch, and create-collection/embedding robustness.
Fixes
- Extension runtimes are no longer treated as addressable REPL sessions: agents can no longer be auto-bound to (or eval in) an extension's runtime; explicit targeting points at
start_sessionfor a real REPL. - Windows: resolve the npm
claudeshim viaPATHEXT(#66), and stop leaking environment in spawn errors. - Extensions receive Kaimon's active environment on
JULIA_LOAD_PATH, and registry/app-installed extensions get a properly instantiated runtime env (#61, #65).
Compatibility
- Requires Tachikoma 2.3.7.
Merged pull requests:
- Fix Windows npm-shim
claudespawn + stop leaking env in spawn errors (#63) (#66) (@kahliburke)
Closed issues:
- Agent fails to spawn
claudeon Windows when the CLI is installed via npm (.ps1/.cmdshim) (#63)
v2.0.8
Kaimon v2.0.8
Kaimon 2.0.8
Fixes extension boot on a fresh registry/app install (pkg> app add Kaimon + app add <extension>), which previously crash-looped. Two independent load-path failures, both resolved:
using Kaimonfails — the extension subprocess carried the manifest-lesspkgdir(Kaimon)on its load path. Kaimon now puts the running instance's active (manifest-bearing) environment there instead. (#61, thanks @mthelm85)using <ExtensionModule>fails — the extension was launched with--project=<manifest-less, write-protected depot dir>, so its own deps couldn't resolve. Kaimon now maintains a writable, instantiated environment per extension (~/.julia/environments/kaimon-ext/<namespace>) and launches against it; dev checkouts with their own manifest are unchanged. (#65)
Merged pull requests:
- Extension spawn: put Kaimon's active environment on JULIA_LOAD_PATH, not pkgdir (#61) (@mthelm85)
- Managed runtime env for registry/app-installed extensions (exposure #2) (#65) (@kahliburke)
v2.0.7
Kaimon v2.0.7
Changes
- Require Tachikoma 2.3.6, which fixes input starvation in render-bound TUI apps (keyboard/mouse were dropped while the app kept animating when a frame exceeded its budget).
Closed issues:
- False warning Julia not on path (#64)
v2.0.6
Fixes
- Windows extensions no longer wedge at startup. On Windows a local IPC gate is bound over TCP (no IPC transport); under a non-lax (API-key) security config it enforces its auth token, but the discovery watcher connected tokenless and was rejected with
"Authentication required"— leaving extensions (e.g. KaimonSlate) stuck at:startingin a restart loop. The watcher now presents the same token, authenticating to its own local gate. - Fixed extension loading by removing an unused
using ReTestimport that forced ReTest onto extension-subprocessLOAD_PATHs, where it failed to resolve.
Observability
- A health-check ping that receives an error reply (e.g. an auth rejection) is now logged, throttled to once per distinct message, instead of being silently treated as a healthy pong.
Dependencies
- Requires Tachikoma 2.3.5 — Windows console-size/resize handling and
ReadConsoleInputWmouse + keyboard support, plus international-keyboard decoding on all platforms.
v2.0.5
Kaimon v2.0.5
Security & Claude Code compat patch.
- Security: removed a localhost OAuth auto-mint that issued bearer tokens to anyone who could reach the port (auth bypass); Kaimon now accepts only configured API keys, and
Originvalidation rejectslocalhost-spoof hosts (e.g.localhost.evil.test). - Compat: OAuth/OIDC probe paths return a clean 404 with a JSON error body, so modern Claude Code no longer crashes on discovery and keyless clients get a clear "Missing API key".
- Chore/CI: gitignore deploy artifacts; LinkCheck false-positive exclusion.
v2.0.4
Kaimon v2.0.4
Fixes
ex: a call that omitted theeparameter (e.g. the code was passed ascode) silently ran an empty eval — success with no result and only a bareagent>in the shared REPL. It now returns a clear error (with a hint whencodewas used), and the tool description / instructions / docs state plainly that the parameter ise.- TUI: control characters (
\r,\n, backspace, …) in tool-call content no longer smear the Activity table / log pane (carriage-return corruption seen on slate tool calls). Requires the companion Tachikoma 2.3.4set_string!control-char strip;[compat]bumped toTachikoma = "2.3.4". - Gate: the "advertised for discovery" diagnostic no longer prints to the console on interactive Julia startup — dropped to
@debugfor a user's own gate; spawned/extension gates keep it in their captured logs.
Changed
- Code search:
search_code(by meaning) is now the documented default for discovery overgrep_code; agrep_codecall that finds nothing (a true negative) nudges towardsearch_code.
v2.0.3
Kaimon v2.0.3
- Auto-background threshold for long evals is now configurable (Config tab or
KAIMON_GATE_PROMOTE_AFTER; 0 = never), and a promoted eval's finished result is now shown in the Activity tab instead of the placeholder (#59) - Write the Antigravity MCP config where current builds read it —
~/.gemini/config/mcp.json(also keeping the legacy path) (#57) - Extension log viewer no longer freezes the TUI (and MCP server) on large logs; extension logs are now size-capped
- Fix reattaching to a detached remote worker (a stale connection could block reconnect)