T3 Connect: environment display name defaults to hostname — how to distinguish multiple environments on one machine?

[yashaka]

Setup: one machine running the desktop app plus three isolated web instances (npx t3@nightly start --base-dir ~/.t3-<slot> --port 3151x --no-browser, one per account slot). All four are linked to T3 Connect (t3 connect link --base-dir ...) and show up in the mobile app — which is exactly the multi-instance use case T3 Connect shines at.

Problem: all four environments display as the same name (the machine hostname), making the list indistinguishable. I found no rename affordance in the mobile app, and no --name/label flag on t3 connect link or t3 start (swept the --help surfaces on 0.0.33-nightly.20260807).

Question: is there an existing way to set a per-environment display name (env var / config key I missed)? If not — consider this a feature request: e.g. t3 connect link --name <label>, or defaulting to something derived from --base-dir when it isn't the default dir. With per-slot base-dirs the stem (t3-automician, t3-claudex, …) would already disambiguate nicely.

[Artem-B]

I think there are two parts that need to be addressed.

First is being able to specify environment name explicitly when we start t3 server. Second is being able to assign a meaningful name to existing instances. Those could be different entities -- immutable instance ID, and user-friendly user editable display name.