Active trigger areas
Choose where SwiftBiu is allowed to respond inside an app so sidebars, canvas edges, games, or other sensitive areas can stay quiet.
Per-app context rules
Let the same Mac gesture mean something different in each app
Global shortcuts are useful until every app needs the same behavior. SwiftBiu app configurations can inherit the global defaults or override toolbar actions, triggers, drag routes, and active trigger areas for Safari, Xcode, Finder, or another app.
Quick answer
Quick answer
SwiftBiu supports per-app configuration on macOS. An app can inherit global behavior, expose its own toolbar actions, override copy or gesture triggers, change file drag routes, or restrict where triggers are active inside that app.
Verified 2026-08-12
What per-app rules can override
Toolbar actions
Control whether the toolbar appears, which actions are available, and their order for a specific application.
Gestures and drag routes
Override copy triggers, gestures, shortcut combinations, quick triggers, and file drag directions per app.
Useful app-specific workflows
1
Keep browsing actions in Safari
Use an app rule to prioritize translation, search, link handling, or another browsing-oriented action set without changing the global configuration.
- 1. Create a Safari rule
- 2. Choose toolbar and triggers
- 3. Leave other apps on global defaults
2
Use a different action set in Xcode
Give an editor or development app its own selected-text actions or shortcuts while preserving a different workflow in browsers and chat apps.
- 1. Create the app override
- 2. Assign editor-specific actions
- 3. Use the same trigger in Xcode
3
Give Finder its own drag routes
Configure file drag directions and default file actions specifically for Finder while other apps inherit the global drag behavior.
- 1. Open the Finder app rule
- 2. Set file drag routes
- 3. Drag files using Finder-specific behavior
App configurations expose routing controls directly
SwiftBiu Preferences includes app-specific configuration so routing decisions live in a visible rule system instead of hidden one-off automation scripts.
Read the App configurations section in the guide →
What to know about per-app rules
- info An app override can intentionally replace the global configuration, so unexpected behavior in one app should be checked against that app rule first.
- info Active trigger areas are designed to reduce accidental triggers; overly broad or overly narrow areas can change how responsive the app feels.
- info The actions available in an app still depend on the current input context, enabled actions, plugin compatibility, and required macOS permissions.
Per-app rules on Mac FAQ
Yes. App configurations can override relevant copy triggers, gestures, shortcut combinations, and quick-trigger behavior for a specific app.
Yes. Active trigger areas let you control where SwiftBiu is allowed to respond inside an app, which can help avoid accidental triggers in specific regions.
Yes. File drag directions and default file actions can be customized per app, including Finder.
Only where you choose an override. An app can inherit global defaults or replace selected behaviors with its own configuration.
Go deeper
Make SwiftBiu fit the app you are actually using
Start with global defaults, then add app-specific rules only where the toolbar, gestures, active areas, or file routes need to behave differently.