Repository navigation
KonX 0.26.0
KonX 0.26.0 — Investigation Copilot
2026-10-23. KonX adds device, topology, event, site, incident, runbook and change-validation evidence to Copilot.
Changes
- Attach explicitly selected device facts and complete command output, snapshot changes, topology nodes or links, and retained event messages.
- Combine selected site references, incident evidence, completed runbook steps and change-validation records in one reviewed conversation.
- Keep original source references, collection times, manual decisions and uncertainty distinct. Attaching does not connect sessions, collect from devices, open referenced files or execute maintenance.
- Serialize incident reads with saves, retain ownership after cleanup failures, and protect incident work during shutdown and updates. Incident and Change Validation file replacement now retries transient Windows sharing errors within a bounded interval, rechecking both file identities and versions before each attempt.
Read the Copilot guide and user guide.
Downloads and upgrading
Windows x64: installer, portable, and checksums.
Installed 0.6.2+ and portable 0.6.0+ can use Update KonX. Installed 0.6.0/0.6.1 requires one manual upgrade. Save drafts, stop listeners, and disconnect before restarting; the existing profile remains in use.
Validation
Full suite: 1,033/1,033 passed. Windows packaging verified 151 source files and 9 runtime dependencies. Packaged SSH passed 28 negotiation and 16 key-format checks; serial passed 27 synthetic checks. Unpacked and portable builds passed isolated save/restart smoke checks. Executable product versions match 0.26.0.
Coverage
Automated checks use isolated profiles, synthetic provider credentials and responses, offline data, and owned loopback peers. Live-provider answer quality, physical equipment, and an elevated installed upgrade remain unverified. Executables remain unsigned. Answers display after complete redaction, even for streaming transports. Redaction recognizes configured credentials and known formats; arbitrary sensitive text still requires review.
Earlier isolated runs encountered intermittent Windows EPERM during Incident and Change Validation saves. This release removes overlapping incident reads and adds bounded, identity-checked replacement retries. Twenty real Electron storage cycles completed 60 replacements without a failure; deterministic tests cover sharing errors, changed targets, cleanup failure and retry. The cause of the original external sharing errors remains unproven, and persistent locks still produce a visible error rather than overwriting an unexpected file.
A separate Electron stress probe reproduced intermittent failures after initial hard-link publication and removal of its temporary alias, with no tracked handles open. The native cause remains unknown; 0.26.0 does not claim to eliminate that publication-related failure. A save error must be resolved before retrying work, and pending outcomes remain owned rather than being reported as saved.
The first portable smoke run stopped when a new Change Validation record did not advance to Baseline; its assertion did not retain the underlying UI error, so that cause is unconfirmed. The assertion now retains that error, and the next complete portable run passed. The original failed evidence is retained. Four older isolated UI fixtures also needed the newly imported investigation modules copied into their test directories before the full suite could run successfully.