Manage T3 Connect environment names and registrations

[Brechard]

Reposting issue #13057 in Ideas, as requested by the maintainers. The original issue is closed; its comments contain additional reports.

Problem

Environment names come from their host machines, so two Macs can appear with the same name plus a numeric suffix. People need recognizable names such as Personal and Work, including for the environment they are currently using. Forgetting a saved connection locally leaves a stale T3 Connect registration discoverable, even when its original machine has been wiped.

Expected behavior

• Give each T3 Connect environment one account-wide name that appears on signed-in devices, including its own host. Make the current environment’s name easy to edit in Settings → Connections and let people restore its advertised machine name.
• Offer the same rename and restore actions for other saved or discovered environments, including in the T3 Connect account page and mobile profile.
• Let people deregister an environment from T3 Connect even when it is offline or not saved locally. Clearly distinguish that permanent action from removing a connection on one device.
• Refresh names without interrupting active connections or discarding a rename in progress.

Related reports and discussion

• Android: stale, unresponsive environments with the same name as working entries. The report asks for removal where the stale entry appears and enough context to distinguish duplicate names.
• One host, multiple OS logins, one T3 Connect account. Independent environments need recognizable work/personal names while retaining their existing IDs, homes and credentials. That comment also proposes an optional advertised startup-name override; it is a suggestion, not an existing setting.
• Desktop-managed SSH connections using different users on the same host. Those environments also need distinguishable display names.
• Earlier discussion #7017 covers multiple environments sharing a hostname. This proposal also covers account-wide naming and managing stale or offline T3 Connect registrations.

[Brechard]

@juliusmarminge @t3dotgg Could you clarify the preferred direction for environment naming? This discussion has six upvotes, with additional reports in #13057 and discussion #7017.

PR #18924 implements host-owned names across clients; #13058 proposed account-wide names. Would you prefer contributors to consolidate around #18924? A scope decision would help avoid maintaining competing implementations that depend on undeployed relay changes.

[SalzerRefinedLeads]

Note

🤖 Claude Opus 5.5 responding on behalf of SalzerRefinedLeads

+1. I ran into this with two devices on T3 Connect that came up with the same name, so I couldn't tell them apart. The only fix was renaming the machines from the terminal (on Linux the label comes from PRETTY_HOSTNAME / hostnamectl --pretty) and restarting the server.

It would be great to rename devices directly in the app, especially as I add more of them.

Version: T3 Code Desktop 0.1.6-nightly.20261029.3892, Linux x64.

[pierresavary562935]

Please allow renaming environments in T3 settings without changing the OS hostname. A persistent config override would also help for headless servers. I manage two Macs and a VPS and want simple, recognizable names.

T3 Code Desktop 0.1.5, macOS.