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
[Bug]: Claude update results omit the configured release channel #30611
apps/server and apps/web (desktop uses the web client)
Steps to reproduce
Use a native Claude Code installation with "autoUpdatesChannel": "stable" in Claude's settings.
In T3 Code, run an offered Claude update. This can either install a newer stable release or find that a fresh provider check is already current.
Read the completion message and update notification.
Expected behavior
The result identifies the configured channel, for example Already up to date on the stable release channel. The web notification preserves that explanation.
Actual behavior
The server reports Already up to date. or Provider updated. without identifying the channel. The web success notification replaces the server's message with New sessions will use the updated provider.
This leaves users unable to tell whether T3 checked the stable or latest release. The original report on Linux bmax, T3 Code 0.1.6, produced Update command completed, but T3 Code still detects an outdated provider version. with Claude 2.1.311 installed, native stable 2.1.311, and latest 2.1.317. The user wondered whether systemd or T3 needed a restart.
Scope
The earlier version-detection defects are tracked in #26400 and #27942. Current main already resolves native Claude versions from its configured release feed. This report concerns the remaining result-message and notification explanation.
Version and environment
Original report: T3 Code 0.1.6, Linux x86_64, native Claude Code 2.1.311 on the stable channel.
Message behavior inspected on main at 7c22e24e3fa1a3bb3a95f27aea000067f198fe7f. The affected files are unchanged on 647bd148b3fbd7c8b57a10fd41ae6d5fc7b35cc1.
Impact
Minor bug. The update outcome lacks the channel context needed to interpret it.
Verification
A regression case reproduces the missing channel in the server result, and another reproduces the successful notification discarding the server explanation. A focused fix is prepared.
Proposed fix
Draft PR #30612 carries Claude's configured release channel into completion messages and preserves those messages in web/desktop success notifications.
Closing this follow-up after reviewing the existing work linked from #26400.
Merged PR #27958 addresses the original false “still outdated” result by comparing native Claude installations with their configured native release feed. The earlier stable-channel proposal, PR #26518, was closed without merging.
The additional channel wording proposed here and in PR #30612 is an incremental clarity improvement. We are withdrawing this separate proposal and closing both the issue and PR.
Activity
juanda2222 commentedon Nov 4, 2026
Closing this follow-up after reviewing the existing work linked from #26400.
Merged PR #27958 addresses the original false “still outdated” result by comparing native Claude installations with their configured native release feed. The earlier stable-channel proposal, PR #26518, was closed without merging.
The additional channel wording proposed here and in PR #30612 is an incremental clarity improvement. We are withdrawing this separate proposal and closing both the issue and PR.