You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit a3d4846
Browse filesBrowse the repository at this point in the historyBrowse files
* feat(notifications): add version-filtered upgrade nudge for legacy extension users
Add extensionVersionBelow field to KiloNotification to allow targeting
users by extension major version. Update the notifications API route to
extract the client version from X-KiloCode-Version / User-Agent headers
and pass it into generateUserNotifications for server-side filtering.
Add a new notification that shows only to kilocode-legacy users (version
< 7), directing them to upgrade to the latest Kilo Code extension.
Co-authored-by: kiloconnect[bot] <240665456+kiloconnect[bot]@users.noreply.github.com>
* fix(notifications): use type import for NextRequest to satisfy lint
Co-authored-by: kiloconnect[bot] <240665456+kiloconnect[bot]@users.noreply.github.com>
* fix(notifications): update legacy EOL notification with accurate messaging and correct URL
Co-authored-by: kiloconnect[bot] <240665456+kiloconnect[bot]@users.noreply.github.com>
* fix(notifications): treat missing extension version as legacy and parse opencode UA
The legacy extension's notification fetch sends only Authorization + Content-Type, so it has no version header. The prior logic hid version-gated notifications when the version was unknown and only parsed X-KiloCode-Version / Kilo-Code UA, neither of which the current extension sends. Result: legacy users (the target) never saw the EOL nudge, and the current extension (opencode-kilo-provider/<version>) also resolved to undefined.
Now parse the opencode-kilo-provider User-Agent so >=7 clients are correctly excluded, and treat an unknown version as an old/pre-versioning client that IS shown the notification.
* refactor(notifications): target legacy EOL notice by axios User-Agent
The legacy extension calls the notifications endpoint with axios, sending User-Agent: axios/<version>, while the current extension/CLI use the shared Kilo gateway headers (opencode-kilo-provider/...). Detecting the axios UA is a precise, positive signal for the legacy extension, replacing the version-gating heuristic that treated absent version data as old.
* docs(notifications): reword legacy EOL notice for 5.x and upgrade-in-place
Both the old and new extension are the same Kilo Code marketplace extension, so reference the 5.x versions and tell users to upgrade to the latest version rather than switch to a different extension.
* Update apps/web/src/lib/notifications.ts
Co-authored-by: Joshua Lambert <25085430+lambertjosh@users.noreply.github.com>
* refactor(notifications): scope legacy UA helper name to notifications
Address chrarnoldus review: an axios User-Agent is not a general 'legacy extension' signal (axios is a generic HTTP client also used for LLM calls). Rename isLegacyKiloExtensionUserAgent -> isLegacyKiloExtensionNotificationsUserAgent to make clear the heuristic is only meaningful for the notifications endpoint.
---------
Co-authored-by: markijbema <624143+markijbema@users.noreply.github.com>
Co-authored-by: kiloconnect[bot] <240665456+kiloconnect[bot]@users.noreply.github.com>
Co-authored-by: Joshua Lambert <25085430+lambertjosh@users.noreply.github.com>
//If you need to check or personalize the notification, see examples at the bottom of this file
40
56
//if you just want a simple straightforward global message, add it here.
57
+
{
58
+
id: 'legacy-upgrade-june-2026',
59
+
title: 'Kilo Code 5.x: End of Life July 31, 2026',
60
+
message:
61
+
'Kilo Code extension version 5.x reaches end of life on July 31, 2026. After that date, it will no longer receive updates, bug fixes, or security patches. Upgrade to the latest version for continued support.',
0 commit comments