Problem
The automatic iTerm2 tab name for Every Code sessions does not update often enough and frequently does not describe the current work in a useful way.
When several Every Code tabs are open, the auto-generated names are hard to distinguish and can become stale or confusing.
Desired behavior
- Generate concise tab names that describe the current task or repository context in a way that is useful at a glance.
- Update the tab title when the active task meaningfully changes, instead of leaving stale names behind.
- Avoid noisy or overly generic names such as raw command fragments, vague session labels, or outdated task summaries.
- Preserve manual/user-controlled terminal titles when appropriate, if the terminal integration already supports that distinction.
- Make the behavior reliable in iTerm2 and document any terminal-specific limitations.
Notes
This probably belongs near the same terminal title/status integration that drives iTerm2 tab indicators. The implementation should consider multi-session workflows where tab names need to remain short, stable, and easy to scan.
Problem
The automatic iTerm2 tab name for Every Code sessions does not update often enough and frequently does not describe the current work in a useful way.
When several Every Code tabs are open, the auto-generated names are hard to distinguish and can become stale or confusing.
Desired behavior
Notes
This probably belongs near the same terminal title/status integration that drives iTerm2 tab indicators. The implementation should consider multi-session workflows where tab names need to remain short, stable, and easy to scan.