[Feature]: Update remote instance

[mbeckenbach]

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

Not sure

Problem or use case

Situation: When a t3code remote instance is configured the local app checks the t3code version at the remote machine.

UX Issue:
It only instructs to update the remote machine and which version to use.

Proposed solution

The warning message should have a button to trigger a self-update and restart at the remote machine.

Why this matters

User Experience. It's annoying that i need to connect to the remote machine myself somehow just to update t3code there.

Smallest useful scope

A simple cli command to update t3code through a simple ssh session, so that i can update all my t3code instances with a chron job for staying in sync.

Alternatives considered

No response

Risks or tradeoffs

Running agent sessions must not be disrupted. Either continue in background or simply wait with update until all sessions have completed.

Examples or references

No response

Contribution

• I would be open to helping implement this.

[justisabelll]

+1. I have the same issue with an always-on Mac running the T3 desktop app through T3 Connect.

A CLI command like:

t3 desktop update

would solve this cleanly by allowing:

ssh my-mac 't3 desktop update'

Ideally it would use the desktop app’s configured update channel, install the update, and relaunch T3. This is especially useful on nightly, where version skew is frequent.

I don’t think any additional remote-management UI is necessary for the initial implementation.

[sguergachi]

This is very much needed!