How ReturnFast works
ReturnFast watches the context you move through, keeps that trail on your Mac, and lets you walk backward or forward through it with global shortcuts.
Last updated
1. Capture the current location
ReturnFast notices when the frontmost app changes and periodically checks for an in-app move, such as changing a browser tab or editor file. It asks the adapter for that app to describe the current location.
Depending on the app, an entry can contain an app and window title, a browser URL, an editor file path and line, or a Finder folder path. Details are collected only when the app and macOS expose them.
2. Build one Back/Forward trail
New locations enter one ordered history, regardless of which app they came from. Repeated observations of the same location update the existing entry instead of creating duplicates.
- The current implementation keeps up to 250 locations in memory.
- The trail belongs to the current run of ReturnFast and clears when the app quits.
- Going Back moves the current position earlier in the trail.
- Going Forward moves later in the trail.
- Visiting a new location after going Back removes the old forward branch.
This is why ReturnFast behaves like navigation history rather than a list of recently used applications.
3. Restore the best available context
When you choose Back, Forward, or an item in the visible trail, ReturnFast locates the app and gives the saved entry to its adapter. If the app is running, the adapter selects a matching tab, opens a known file or folder, or raises a matching window. If the app is no longer running, ReturnFast can relaunch the app, but cannot guarantee that the former in-app context will be recreated.
See the supported-apps matrix for the precise restore level and limits of each app family.
Default shortcuts
| Action | Default | Behavior |
|---|---|---|
| Back | ⌥⌘[ | Move one location backward. |
| Forward | ⌥⌘] | Move one location forward. |
| Return from detour | ⌥⌘R | Return to the work location saved before an interruption. |
You can replace these shortcuts in ReturnFast settings.
Automatic detours
When you leave an editor or terminal for a different app, ReturnFast can remember that work location as a detour anchor. The detour shortcut returns to that anchor and then clears it. This is separate from stepping through the full Back/Forward trail.
Permissions and network use
- Accessibility: used to read focused window information and raise the intended window.
- Automation: used by supported browsers, terminals, and Finder to read or select app-specific context.
- Network: navigation entries are not sent through the licensing API. A network connection is used to purchase, activate, and revalidate a license.
The privacy page separates local navigation data from license and website data in detail.
Current limitations
- Restore depth varies by app and by the information available at capture time.
- A Chromium tab must still be open at the exact captured URL.
- Editor file and line restoration is best effort.
- Terminal restore is window-level and does not recreate a closed shell or command.
- Chat apps such as Slack use window-level restore, not thread-level restore.
- Relaunching a closed app does not guarantee its former context will return.