Kody v2026.08.22
Kody v2026.08.22
This release is about resilience and control. Kody stops treating transient platform hiccups as permanent failures — scheduled jobs, sandbox execution, storage reads, and package rebuilds all retry gracefully now — while the OAuth connect page gets a proper scope picker and provider chooser so you always know what you're granting. Memory auto-surface also gets sharper: compact one-liners that stick around, with duplicates collapsed.
New
-
OAuth scope picker and provider chooser. You can now visit
/connect/oauthwhile signed in and pick from your enabled services and saved connections, choose exactly which scopes a connection requests, and see what you're granting before you connect. When an agent needs more access than the current token has, the integrations page shows a copy-prompt to reconnect with wider scopes instead of leaving you to guess. The chooser scrolls and filters once the list grows past six options. (#1633, #1641) -
Smarter memory auto-surface. Kody now injects compact one-liners for your top stored memories — subject and summary only, no clutter — and keeps showing them even as your conversation grows or compacts, so preferences like "draft, don't send" don't vanish mid-chat. Duplicate memories that share a dedupe key collapse into a single slot so both auto-surface slots aren't wasted on the same thing. (#1646, #1649)
Improved
-
Social login buttons are now icon-only with full accessible labels — no more doubled "X" or an oddly sized Discord mark. (#1630, #1632)
-
The follow checkmark stays on the same line as the username on community package pages and profiles instead of dropping underneath. (#1637)
-
Republishing a package no longer silently disables scheduled jobs you already turned on — manifest
enabledis the create-time default, not a live override. (#1622) -
Docs for repos, run records, and memory usage now describe how the system works today, with soft "in v1" phrasing trimmed away. (#1652)
Fixed
-
Transient platform blips no longer fail your jobs or packages. When the platform evicts or resets a running instance mid-call, scheduled jobs retry the same occurrence, sandbox execution gets one more drain-delayed attempt, storage-estimate reads stop stacking abandoned calls, and package artifact rebuilds survive transient database faults — instead of recording a permanent failure or blaming your code. Stale running rows are now classified as platform interrupts, not user-authored errors. (#1636, #1629, #1639, #1638, #1615, #1627, #1640, #1643)
-
Expected community publish preconditions (private packages, non-MIT licenses, missing READMEs) and package scope denials no longer trigger Sentry noise that looks like a platform bug. (#1635, #1631)
-
The two-factor setup flow no longer flakes when page hydration lags behind visible buttons in end-to-end checks. (#1628)