Repository navigation
Keiko 0.3.16 (v0.3.16)
Keiko 0.3.16
Keiko's first public download release. Pick your platform below, unzip, and start it —
Node.js and the OpenCode sidecar are already inside; nothing else has to be installed.
Unsigned evaluation build (ADR-0121 D1, ADR-0163 D9). The bundles are sealed, so macOS
will not report a damaged app, but they carry no Apple Developer ID, no notarization and no
Windows trusted publisher yet. That is why the first launch needs the one extra confirmation
described below. Every integrity digest, containment and provenance check stays enforced.
What changed
Keiko 0.3.16 Release Notes
High · Improvements
- Every activity-log line carries a process id, an instance id and a gap-free sequence number, so an analyzer can order events exactly and detect any line that was dropped.
- One correlation id follows a request from the browser through the BFF to every model-gateway call, retry and circuit-breaker transition, to WebSocket sessions and to the background jobs it spawns; a background job also names the request that started it.
- A chat error now shows a Support ID you can quote; the same id is on every server line of that request.
- Request lines record the matched route template, the query parameter names, the response size and whether the client abandoned the request; every event stream ends with a line stating how many frames and bytes were sent and why it closed.
keiko support exportwrites one support file — redacted log lines of the last seven days, the product version and platform, and a content-free fingerprint of each local store — andkeiko support analyzereconstructs per-request timelines from it; the export never modifies, migrates or unlocks a store.- Errors carry a Keiko-code stack (package and file positions, never absolute paths) and a closed error classification; provider errors record the HTTP status and retry-after; rate limits, key resolution, keychain fallbacks, encryption migrations and store opens leave body-free evidence.
- Console-only diagnostics (memory retrieval degradation, Figma snapshot failures, a crash on a directly launched
keiko ui) now reach the activity log, and the operator's stderr diagnostic carries no more than the log does. - Browser-side failures are reported to the server as bounded, content-free notes joined to the request they belong to, behind a process-wide rate limit.
Technical release metadata
- Package:
@oscharko-dev/keiko@0.3.16 - Release tag:
v0.3.16 - npm dist-tag:
latest - Registry:
https://registry.npmjs.org/ - Generated by:
npm run release:publish
Structured impact entries:
2026-08-22-keiko-0.3.16-reconstructable-activity-log: high / improvements; supported from 0.2.0; affected state stores none; remediation restart-required; default patch notes yes; traceability catalog:2026-08-22-keiko-0.3.16-reconstructable-activity-log; review:github-issue-comment:#3247#5380714387
Install on macOS
- Download and unzip; double-click
Keiko.appinside the extracted folder (moving it to
/Applicationsfirst also works — the first start adopts it there). - macOS will say it cannot verify the developer. Open System Settings → Privacy &
Security, scroll to Security, click Open Anyway, and confirm. One time only. - Keiko installs itself to
/Applications, starts, and opens athttp://127.0.0.1:1983.
If a start fails, Keiko now says why in a dialog. Runbook:
macOS first-launch
Install on Windows
Run keiko-windows-x64-setup.exe (SmartScreen: More info → Run anyway), or unzip and start
Keiko.exe.
Checksums (SHA-256)
fbfe765ce7a591656cf41cac169e8fe65a4aa8f3d6986dc67e76c4f7695b460e keiko-macos-arm64.zip
782ae65e3aeb538f248ff83ab6a05ca32ffbeee11c8f41c00a5ec87c33fc6f3f keiko-macos-x64.zip
f865a313d4e3e486e180b791305a07296a59b6a60cbe18d5b2079cfdfa92f312 keiko-windows-x64.zip
9f5b5004e5c4715dbe6606c00d3917e69f42a21512cc5a30cf3a0222a8bafec9 keiko-windows-x64-setup.exe
macOS seal verification: verified (keiko-macos-arm64.zip, keiko-macos-x64.zip).
Built from commit 45045b4 by workflow run 32579975726.