[Feature]: Automatically update T3 Code across connected environments

[ElliotDrel]

Before submitting

• I searched existing issues and did not find a duplicate.
• I am describing a concrete problem or use case, not just a vague idea.

Area

Desktop settings, updater, T3 Connect / remote environments, and server lifecycle

Problem or use case

T3 Code repeatedly asks me to approve application or server updates. This becomes especially frustrating when I use multiple T3 Connect environments.

A remote machine may show that T3 Code itself needs to be updated before I can continue. I then have to access that machine, approve the update, wait for the restart, and reconnect.

I would rather opt in once and have T3 Code remain current automatically on all configured machines.

Proposed solution

Add an Automatically update T3 Code setting.

The setting should work across local and T3 Connect environments so users can keep every configured machine current without approving each routine update manually.

Expected behavior

• Add an Automatically update T3 Code setting.
• Allow the policy to apply to:
  • this environment only; or
  • all configured T3 Connect environments.
• Allow optional per-environment overrides.
• Respect each environment's selected release channel, such as stable or nightly.
• Download and install eligible updates without requiring confirmation every time.
• Never interrupt an active agent run.
• If a restart is required, wait until the environment is idle or until a configured maintenance window.
• Restart the app/server and reconnect automatically when safe.
• Report pending, updating, restarted, current, and failed states for each environment.
• Identify the exact environment that needs attention rather than showing only a generic remote-update notification.
• Preserve environment settings, T3 Connect configuration, threads, and provider configuration across the update.

Settings model

A useful settings structure could include:

• T3 Code automatic updates: Off / When idle / Scheduled
• Apply to: This environment / All connected environments
• Per-environment overrides
• Stable/nightly channel selection
• Optional version pinning or update hold

A simpler MVP could provide one Automatically update T3 Code when idle toggle per environment, plus an action to apply that setting to all configured environments.

Remote environment behavior

From any T3 client, I should be able to see whether each connected environment:

• has automatic updates enabled;
• is current;
• has an update pending until idle;
• is downloading or installing;
• requires a restart;
• restarted successfully;
• failed and needs attention.

The remote client should reconnect automatically after a successful update whenever possible.

Why this matters

T3 Code is used to manage coding sessions across multiple machines, including always-on remote environments. Repeated manual update approvals undermine that workflow and can leave machines on incompatible versions until someone accesses them directly.

An opt-in unattended update policy would let desktops, laptops, servers, and cloud machines remain compatible and available without routine manual intervention.

Smallest useful scope

• One Automatically update T3 Code when idle toggle.
• Store the setting per environment.
• Allow applying it to all configured T3 Connect environments.
• Do not update or restart while an agent session is active.
• Restart and reconnect automatically when safe.
• Show clear pending, success, and failure status for every environment.

Related but distinct issues

• [Feature]: Automatically update supported provider CLIs across connected environments #5517 covers automatically updating the external provider CLIs such as Claude Code, Codex, or OpenCode.
• [Feature]: Let direct/self-hosted web clients discover newer releases #5299 covers discovering newer releases for direct/self-hosted web clients and keeps installation user initiated.
• Add one-click update for remote environment version drift #3598 covers one-click remote server updates after version drift.
• [Feature]: Launch T3 Code automatically at system login #5510 requests launching T3 Code automatically at system login.

Risks or tradeoffs

• Automatic restarts must not terminate active work or corrupt provider-native sessions.
• Nightly releases may be less stable, so the selected release channel and update policy must be explicit.
• Failed updates need recovery, rollback where possible, and an actionable status visible remotely.
• Global settings must not silently override deliberate per-machine version pins.