Add one "Update all" action for T3 Code, connected backends, and providers

[lenard-d]

Problem

When I open T3 Code to work, I can have several separate updates waiting: the desktop app, connected T3 Code backends, and provider CLIs such as Codex or Claude Code. I have to start each update separately and wait for each result. In my setup, this can mean five individual updates before I start the task I opened the app for.

I want one action to bring the supported components up to date across my connected environments.

Proposed solution

Add an Update all action that includes:

• The T3 Code desktop app.
• Connected T3 Code backends that support remote updates.
• Supported provider CLI installations on each connected environment.

Before starting, show the components and environments that will update. One confirmation should start the full process without further routine approvals for each component.

T3 Code should handle the update order and reconnect after required restarts. If one update fails, show the result for each component and offer one action to retry the failed updates.

Optional automatic mode

The same process could support an opt-in Automatically update all when idle setting. It should use each component's configured release channel and defer updates that would interrupt active work. Offline environments should show as pending and be checked when they reconnect.

Manual Update all would be a useful first version. Automatic execution can follow later without requiring a separate update process.

Scope and safeguards

• Do not interrupt active agents or terminal commands. Defer updates that require an unsafe restart until the environment is idle.
• Respect version pins, update holds, configured release channels, and externally managed installations.
• Show components that require a manual update or additional system permission instead of silently replacing them.
• Preserve provider paths, accounts, authentication, settings, and saved threads.
• Verify the resulting versions and connections before reporting success.

Related requests

• Issue #2993 requested automatic provider updates and was declined because silent updates can break pinned or enterprise-managed installations. A manual Update all action keeps explicit user control and respects those exclusions.
• Discussion #12611 requests a manual Update all providers action across environments.
• Discussion #6890 requests automatic T3 Code app/server updates across environments.
• Discussion #6893 requests automatic provider CLI updates across environments.

This request is for one coordinated update process across the app, connected backends, and providers. In particular, #12611 would reduce repeated provider updates, but would still leave separate app/backend and provider update actions. The goal here is one action and one result view for the full process. It can build on those requests rather than replace them.

[juliusmarminge]

Note

Grok responding on behalf of Julius.

Closing as a duplicate of #12611 ([Feature]: Add "Update all" for providers across all environments).

Settings already has a manual Update all for T3 Code across connected environments; #12611 is the open ask for the matching providers bulk action. A single coordinated "Update all" that also folds in app/backends is useful composition detail — please continue there rather than tracking a parallel Ideas thread.

Related but not the same feature (left open):

• [Feature]: Automatically update T3 Code across connected environments #6890 — automatic T3 Code app/server updates across environments
• [Feature]: Automatically update supported provider CLIs across connected environments #6893 — automatic provider CLI updates across environments
• [Feature]: Update remote instance #6870 — one-click remote instance update (narrower)
• Extend the server-update notice pattern to remote provider updates #10318 — remote provider update notices (not a bulk Update all)
• Optional "Restart and Install Automatically" after working threads are finished #9286 — restart-and-install after idle threads

#2993 (auto provider updates without asking) stayed closed: silent updates conflict with pins / enterprise-managed installs; manual Update all keeps user control.