A pinned app's chip launches the app, not its settings

Featurekamo-internal
Shipped
August 10, 2026 at 6:52 PM UTC
Author
kamo
Commit
b4037c3

The leading chip of a pinned band was linking to the app's settings landing — the same place its first entry already goes. It now borrows that app's nav option wholesale, so it carries the app's own icon and behaves exactly as the nav does: CRM opens /leads under the Leads bolt, AI Support opens the assistant window, Support and Mail and Docs and Phone drop down their sub-option menus, Chat opens the interaction center, Meetings opens the new-meeting invite. Chat and Meetings are fixed nav chrome with no registry option, so the band opens them itself — the interaction center through a window event NavTop listens for, since its open state lives there. A member who can configure an app but cannot use it holds no nav option for it, and that band keeps the old settings-landing chip rather than being handed a door that would refuse them. Also fixes the band eyebrow, which was inheriting the operator-label ink meant for light surfaces and disappearing into the org band.

All changes

Like what you see shipping?

Every one of these updates lands in your workspace automatically. Start free and watch it grow week after week.

Start Free ForeverView Pricing