KonX 0.27.1

KonX 0.27.1 — KonX-AI and Saved Provider Keys

2026-10-23. The contextual assistant is now KonX-AI, with improved encrypted provider-key management.

Changes

• Rename Copilot to KonX-AI throughout current panels, tool actions, menus, status messages and guides. Existing conversations, evidence, reviewed outcomes and workspace references remain compatible.
• Retain provider API keys in the local encrypted store, reuse saved keys for requests and connection tests, and provide a clear deletion control for the selected provider.
• Preserve a newly entered key when validation or saving fails, and protect unsaved connection changes when closing or switching providers. Refresh an open KonX-AI panel after settings change so its test controls reflect the saved connection.
• Flush encrypted settings before publication, preserve the previous saved configuration on write failure, and retain ownership of pending temporary files or handles for cleanup retry. Pending cleanup blocks an update and keeps the window available if closing fails; key changes are rejected during shutdown.

The investigation found that the prior settings form cleared an entered key even when saving failed, and an already open contextual panel could retain stale connection status. Existing encrypted-key reuse was already implemented; these findings do not establish that a successfully saved key was deleted from the user's profile.

Read the KonX-AI guide, provider setup 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 Windows profile remains in use.

Validation

Full suite: 1,073/1,073 passed. Windows packaging verified 157 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.27.1.

A focused three-process Electron regression uses the real renderer, main-process provider client and Windows encryption with a synthetic Nyquest transport. It covers failed-save retry, repeated successful and rejected connection tests without re-entering or rewriting the key, independent provider settings, panel reopening, restart reuse, deletion with unsaved replacement edits, and a second restart confirming deletion. Native publication checks cover existing destinations, changed sources, Unicode paths and failure without an overwrite fallback.

Coverage

Tests use isolated profiles, synthetic API keys and responses, and owned loopback peers. No live Nyquest or paid-provider request is made. Live-provider response quality, physical equipment and an elevated installed upgrade remain unverified. Executables remain unsigned. Terminal commands in answers remain manual; editor actions do not save or upload automatically.