Karmas Coder 0.2.2 release notes.
What changed in Karmas Coder 0.2.2 (Jun 14), including Your Karmas Coder profile has more personality, Deleted threads get a safer recovery window, Live composer edits stay visible per turn, Release checks are steadier.
Release 0.2.2· Jun 14
Karmas Coder 0.2.2
Your Karmas Coder profile has more personality — Profile settings now include richer identity details, activity stats, and a cleaner editing flow so Karmas Coder feels more like your own workspace.
This release adds profile stats aggregation, profile settings UI polish, activity heatmap refinements, avatar/profile editing updates, and focused coverage for the new profile data paths.
Deleted threads get a safer recovery window — Thread deletion now keeps soft-deleted data around long enough to avoid accidental loss while still letting cleanup happen predictably.
Karmas Coder now tracks thread retention state explicitly, covers soft-delete cleanup behavior with server tests, and keeps deletion/recovery semantics more predictable for early WIP data.
Live composer edits stay visible per turn — Composer changes made while a turn is running now stay attached to the right turn, reducing confusing stale text or hidden edits during active work.
The chat route and composer state handling were tightened so live edits remain visible in the correct turn lifecycle without bleeding into unrelated transcript updates.
Release checks are steadier — The release test path now avoids known teardown and child-process timing traps, making full validation less likely to stall after tests have passed.
Effect ACP child-process fixture tests now have explicit timeouts, and the server test script runs its Vitest files serially so the root Turbo test gate exits cleanly during release validation.
Updated with every release. See releases on GitHub.
Download Karmas Coder