Skip to content

v0.6.0

Latest
Latest

Choose a tag to compare

View all tags
@legetdev legetdev released this 01 Oct 12:46
· 2 commits to main since this release
v0.6.0
2257b71
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Klyk 0.6.0 hardens local computer control and client setup while preserving the existing MCP tool interface.

  • Generated launch configurations exclude the workspace from Python module lookup. Existing standard Codex/Grok settings can migrate without discarding comments, environment overrides or tool restrictions.
  • Control handoffs refuse while input delivery or cleanup is active. Cancellation and the emergency latch release held keys and buttons; target checks reject reused process IDs and stale window identities.
  • Visible cross-app drags verify the actual accessible process and selected window at both endpoints before mouse-down. Covered or unverified targets refuse without sending a drag.
  • Native file-picker paths use scoped accessibility controls, exact path readback and verified dialog ancestry. Uncertain effects stop the operation rather than triggering speculative typing or confirmation.
  • Diagnostic logs omit request payloads, redact more credential formats and bound retained output. Screenshots remain scoped to the requested window, with private-file and image-memory limits.
  • Configuration replacement checks the original file snapshot, and package publication separates build activity from the short-lived PyPI publishing permission.

After upgrading an existing 0.5.x installation, run a fresh klyk doctor --fix from that installation, then restart your AI clients when ready. Explicit custom import paths remain trusted overrides; customized TOML launch commands are preserved for manual editing.

Klyk controls a real Mac on behalf of a trusted agent. Confirmation guidance does not enforce user consent, screen/OCR content can be forwarded by the chosen client, and the emergency latch is process-local. These boundaries are described in SECURITY.md.

Release verification covers all48 tools and48 independent native outcomes on both supported MCP SDK majors on macOS26, plus Chrome/Electron workflows, fresh installation,486 portable checks per SDK and exact prepared-package checks. Accurate OCR and Chromium delivery are not qualified on the hosted macOS27 VMs. Physical emergency-shortcut acceptance remains a separate manual check; these results do not imply compatibility with every app or hardware configuration.

Assets 2
Loading