Support MacOS Tab Recognition

Discord username (optional)

No response

Describe the bug

I guess Warp is using your own tab implementation, and not the one provided by macOS. It's better that either having to add Accessibility API information to your tab model, or switching to the standard tabs, so that other App can see your tabs and iteract with it like Chrome or Finder, iTerm2, Terminal tabs are being interacted with.

To reproduce

Any app switcher that supports tabs can't see your tabs instead of the current tab

Expected behavior

No response

Screenshots

No response

Operating system

MacOS

Operating system and version

MacOS 12, 13, 14

Shell Version

No response

Current Warp version

No response

Regression

No, this bug or issue has existed throughout my experience using Warp

Recent working Warp date

No response

Additional context

No response

Does this block you from using Warp daily?

Yes, this issue prevents me from using Warp daily.

Is this a Warp specific issue? (i.e. does it happen in Terminal, iTerm, Kitty, etc.)

Yes, this I confirmed this only happens in Warp, not other terminals.

Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e

None

No source file or test is identified in the issue. Start by locating Warp's macOS tab implementation and checking how its tabs are exposed to app switchers; compare the behavior with Terminal, iTerm2, Chrome, or Finder. Done means supported macOS app switchers can recognize and interact with Warp's tabs.