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
Tabby can currently be enabled or disabled globally, but users need more precise control. Some apps are sensitive, incompatible, or already have important Tab behavior, so globally disabling Tabby is too blunt.
Goal
Allow users to disable or re-enable Tabby for specific applications while keeping the global autocomplete setting intact.
Proposed Scope
Add a menu bar action for the current frontmost app, such as Disable Tabby in This App.
Add a Settings section that lists explicit per-app rules.
Persist app rules by bundle identifier, not display name.
Make the suggestion pipeline respect per-app disabled state before generating or showing overlays.
Show a clear user-facing reason when Tabby is disabled for the current app.
Acceptance Criteria
Users can disable Tabby for the current app from the menu bar.
Users can view, remove, or modify app-specific rules in Settings.
Disabled apps do not trigger generation, overlay rendering, or Tab acceptance.
The menu bar state explains when Tabby is disabled by an app rule.
Rules survive app restart.
Open Questions
Should there be both allowlist and blocklist modes, or only a blocklist for now?
Should per-app rules also disable future context features such as clipboard, AX tree context, screenshot context, and personalization?
Activity
[-]Allow Enable/Disable on per application basis[/-][+]Add per-app enable/disable controls[/+]Merge pull request #1 from mc-hamster/codex/fix-ci-test-teardown