Kala 0.4.3
Downloads for 0.4.3
- Portable Host
- CJS · Node.js 22+POSIX manager
- Windows
- Portable PowerShell manager
Copilot sessions require the official Copilot CLI, installed separately by the operator on the Host machine.
Already installed? Use the verified stable bootstrapper to update the Portable installation.
Release overview
These are the published notes for v0.4.3, not a cumulative feature list. For the preceding release, see v0.4.2 below.
- 2 improvements and 4 fixes in this release
- Full changelog since v0.4.2
Improvements
- The opt-in unified Settings layout groups configuration and administration by authority, with versioned conditional writes, explicit effective-state feedback, and restricted Operator maintenance.
- Session lists use stored summaries and bounded restored-event replay to improve initial readiness without changing Session ownership or organization scoping.
Fixes
- Mobile user-message timestamps and metadata remain in normal layout flow instead of overlapping message text.
- Session operation feedback no longer overwrites the authoritative Agent status.
- Dedicated native SILO Console launch, explicit Owner credential handoff, and authenticated WebSocket forwarding work through the retained and direct ingress paths without Dashboard fallback.
- Public release promotion explicitly refreshes the website, so workflow-token publication does not leave the download page on the preceding release.
Known boundaries
- Unified Settings remains an installation-controlled rollout through KALA_SETTINGS_LAYOUT=unified; existing installations retain the legacy layout until deliberately enabled.
- Expanded PostgreSQL schemas require Operator-run migrations and a schema-compatible rollback build. Do not restore pre-expansion binaries or downgrade the schema.
- Native SILO Console keeps its separate administrator login. Credential handoff is explicit and Owner-gated; proxy access does not itself authenticate the native application.
- Private Cloud lifecycle support remains preview-only; fresh installs require external OIDC, the postgres-s3 profile, and evaluation and backup acknowledgements.
Full changelog · v0.4.3
Compare v0.4.2...v0.4.3 on GitHub · 8 commits
Show all 8 commits
- Fix Devbox attachment handling and prepare v0.4.2
- Implement unified Settings and authoritative configuration
- Fix Dedicated native console access and WebSocket proxying
- Improve Dashboard mobile layout and Session list performance
- Prepare v0.4.3 release and refresh published downloads
- Stabilize release test scheduling and expose image scan failures
- Keep scanner fail-closed assertions aligned with diagnostics
- Record approved v0.4.3 exact vulnerability risk acceptance
Verification files
Kala 0.4.2
Improvements
- No user-facing improvements are recorded for this build.
Fixes
- Dedicated and Private Cloud Runtime now retain the attachment transfer capability advertised by current Devbox Executors, so Session attachment saves no longer incorrectly request an Executor upgrade.
- Failed tool calls show their actionable diagnostic without generic duplicate explanations; attachment saves rejected before dispatch no longer claim that a transfer may have occurred.
- The Windows Portable download command verifies the release signature and manager checksum before installing and starting Kala.
Known boundaries
- External Workspace Executor upgrades and authenticated production console interactions require separate device-level acceptance.
- The Windows Portable command requires separately installed Node.js 22+ and Cosign from trusted sources.
Full changelog · v0.4.2
Compare v0.4.1...v0.4.2 on GitHub · 1 commits