# feat\(web\): show which profile a browser tab is running in · pingdotgg/t3code

[View on GitCafe](https://git.cafe/pingdotgg/t3code/commit/0a9e51f57240bdf89035205f9bfee0940dfefec7)

Repository: [pingdotgg/t3code](https://git.cafe/pingdotgg/t3code)

Visibility: public

Requested revision: 0a9e51f57240bdf89035205f9bfee0940dfefec7

Requested commit: 0a9e51f57240bdf89035205f9bfee0940dfefec7

Commit: 0a9e51f57240bdf89035205f9bfee0940dfefec7

Tree: f3f804f0565af4f246a0248ff94556c743a3d04c

Author: Julius Marminge

Committer: Julius Marminge

## Message

```
feat(web): show which profile a browser tab is running in

A tab's profile was only discoverable by opening the three-dot menu, which is
a poor place for something that changes what you are logged into.

The chrome row gains a leading slot before the URL bar, and the preview names
the tab's profile there. Only when it differs from the default: labelling
every tab "Default" would be noise on the common case, while a tab running in
another profile is exactly what needs calling out.

Also gives the three-dot menu's profile heading a `MenuGroup` ancestor —
`MenuGroupLabel` reads Base UI's group context and throws without one, which
took the app to its error boundary as soon as the menu opened.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

```

## Parents

- [2fbfa0e2554702e765f72baff8bbf5a646fbc934](https://git.cafe/pingdotgg/t3code/commit/2fbfa0e2554702e765f72baff8bbf5a646fbc934?format=markdown)

[Source at this commit](https://git.cafe/pingdotgg/t3code/tree/0a9e51f57240bdf89035205f9bfee0940dfefec7?format=markdown)