You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Feature]: Mobile — show the environment prominently on a new task, and allow color-coding environments #8479
Two related gaps around environment visibility on mobile:
When starting a new task from the phone app, there is no environment selector on the first message the way there is on desktop/web — and the environment isn't shown prominently either, so you can't tell which machine you're about to run on.
There's no way to tell environments apart at a glance anywhere in the mobile UI. Color-coding (even as an opt-in) would make the "Choose project" and active-sessions lists readable instantly.
1. No environment selector / indicator on the first message (mobile)
On desktop/web you pick the environment as part of composing the first message of a task. On the phone app that selector isn't there — you go through Choose project and the environment is implied by whichever project entry you tap.
That's workable if the environment is obvious, but it isn't: the project list shows the project name and the absolute path, and nothing about which environment the entry belongs to.
Concretely, in my "Choose project" list I have a project group with three workspaces, all rendered as:
Three identical rows. They are three different environments on (or pointing at) the same path, and the list gives me no way to know which is which — I have to guess, tap one, and find out after the fact.
Ask: either bring the first-message environment selector to mobile as well, or (cheaper) show the environment name prominently on each project row and on the composer for a new task, so the destination is unambiguous before I send.
Related: #5623 covers naming environments (they all default to the hostname). Even with good names, mobile currently doesn't surface the name where it matters — so these two together are what make the list unusable.
2. Color-code environments (at least as an option)
Right now, looking at the active sessions list, you can't see:
whether several sessions are running on the same host, or
whether a host is idle / has nothing running on it.
A per-environment colour — assigned automatically with an option to override, or purely opt-in — applied as an accent/dot/left border on project rows, session rows, and the composer would answer both of those at a glance, without adding text to already-dense rows.
This feels like a cheap win: it's the same information already in the model, just made scannable.
Thanks for the detailed proposal. We are tracking this environment-identification work in Ideas discussion #8218.
The current mobile new-task composer has a selectable on <environment> control. This report still identifies an earlier clarity problem: three identical project rows can point at different environments. I added the request for clearer project-row and composer destination labels to the discussion before closing the issue. The handoff also retains the user's proposal for a more prominent selector presentation and optional environment colors.
I'm closing this as a feature request tracked in Ideas as part of an automated pass on all open issues. This does not mean clearer project-row labels or environment colors are implemented. The full report remains available here, and the linked discussion now holds the details needed for further design work.
Activity
t3dotgg commentedon Aug 28, 2026
Note
🤖 GPT-5.6 Sol responding on behalf of Theo
Thanks for the detailed proposal. We are tracking this environment-identification work in Ideas discussion #8218.
The current mobile new-task composer has a selectable
on <environment>control. This report still identifies an earlier clarity problem: three identical project rows can point at different environments. I added the request for clearer project-row and composer destination labels to the discussion before closing the issue. The handoff also retains the user's proposal for a more prominent selector presentation and optional environment colors.I'm closing this as a feature request tracked in Ideas as part of an automated pass on all open issues. This does not mean clearer project-row labels or environment colors are implemented. The full report remains available here, and the linked discussion now holds the details needed for further design work.
Squashed '.repos/effect-smol/' changes from a43c7e244c..e17ecdbe90