Docs · Reference

Updates and removal

Requirements, updating the app and the extension, moving to the new version, ways to turn it off and complete removal. Also where Routekeeper keeps its data and where it connects to on its own.

All docs sections

Routekeeper has two parts: the app with the menu bar icon, and the network extension, which runs in the system and applies the rules. They are updated and removed a little differently, so each part is described separately below.

Requirements

Routekeeper comes as the disk image Routekeeper.dmg on the website and on GitHub Releases. The build is signed with a developer certificate and checked by Apple (notarized). The first time you open it, macOS still asks whether to open a program from the internet. Click “Open”. Installation is described step by step in the Quick start.

Updates

The app

The network extension

Starting with version 0.5.0, the extension updates by itself: right after the app updates, Routekeeper installs the extension that comes with it. You don’t need a password or a new approval in System Settings: macOS carries the approval over to the new version. Once the new version is running, you get the notification “Network extension updated to …”.

While the extension restarts, connections through the proxy break, and for a couple of seconds new connections may go direct, around the proxy. This happens once after the app updates. The update window warns about this before you install. Quit the apps that must not go online around the proxy before you update Routekeeper. For details, see Limitations.

If the extension couldn’t update by itself, the banner “A network extension update is available (current: …).” stays at the top of the window, and the menu of the menu bar icon has the Extension Update Available item. Click Update… on the banner, then Update Now. Or, in Settings → Extension, click Update Extension (current: …) in the Status section: this button updates right away, without asking again. In version 0.4.1 and earlier, this was the only way to update the extension.

If the “The network extension isn’t responding” banner appears after the update, click Reinstall Extension. If that doesn’t help, restart your Mac. For details, see Reinstalling and stopping the extension.

From version 0.2.x to 0.3.0, a normal update won’t work: the old version only tells you about the new one and gives a link to the website. How to move to it is described in the next section.

Moving from 0.2.x to 0.3.0

This section is about the version that comes out after 0.2.1. Until it’s on GitHub Releases, you don’t need to do anything.

In version 0.3.0, Routekeeper’s system app identifier (bundle ID) changed from dev.ilyabazenov.appproxy to app.getroutekeeper.mac. For macOS, this is a different app. Permissions, opening at login, notifications and window settings are tied to the identifier, and only the old app can remove the old extension. That’s why version 0.2.x won’t install the new version over itself: it only tells you about it and gives a link to the website.

Steps

  1. If you like, save your rules to a file: Rules → Import and Export → Export…. Usually you don’t need this, since the rules move over by themselves, but this way you’ll have a copy. Proxy passwords aren’t saved to the file.
  2. In the old Routekeeper, open Settings → Extension and click Delete… → Delete. The old extension and its filter and proxy are removed from the system, and the rules stay on disk.
  3. Click the menu bar icon → Quit Routekeeper. Move the old Routekeeper from Applications to the Trash.
  4. Download the new version from the website, drag Routekeeper to Applications and open it from there.
  5. Go through the welcome screen: allow the network extension, network content filtering and the proxy configuration again (how to do it). Allow notifications when macOS asks.
  6. If Routekeeper used to open at login, turn this on again: Settings → General → Open at login.

On first launch, the new extension moves your rules, proxies with passwords and mode settings by itself. If you had apps or services going through a proxy, then after the three permissions the window opens straight to your sections, without the proxy and app steps.

If the old extension is still there

If you skip step 2, the old extension keeps running and handling traffic next to the new one. The rules of the two versions will get in each other’s way. The new version notices this and shows the banner “An extension from an old version of Routekeeper is running”.

You can check whether the old extension is on with a command in Terminal. The line with dev.ilyabazenov.appproxy.extension must not have the [activated enabled] mark.

systemextensionsctl list

What moves over and what doesn’t

Moves over by itselfNeeds to be set up again
Rules, proxies with logins and passwords, the mode, the firewall and network settings, downloaded service listsThe three macOS permissions, opening at login, permission for notifications, window settings: notification switches, automatic update checks, the selected settings tab

The new version deletes the old version’s caches in ~/Library on first launch: traffic map data (about 55 MB) and downloaded service lists. The old version’s window settings file stays, and you can delete it: see What stays on disk.

Details: how the settings move

Versions 0.2.x keep settings in /Library/Application Support/AppProxy, the new version in /Library/Application Support/Routekeeper. On first launch, the new extension moves the files from the old folder to the new one, if the new folder doesn’t have its own settings yet, and deletes the emptied old folder. Rules for Routekeeper itself are switched to the new identifier.

It’s better not to go back to 0.2.x after the move: the old version looks for its settings in the old folder, which no longer exists, and starts with clean settings. If you must go back, export your rules first.

The extension’s identifier changed too: dev.ilyabazenov.appproxy.extension → app.getroutekeeper.mac.extension. The subsystem of the internal log is now app.getroutekeeper.mac.

How to turn it off

There are four ways to “turn off” Routekeeper, and they do different things.

WayWhereWhat happensHow to undo it
The Routekeeper On switchThe menu of the menu bar icon; the panel at the bottom of the window’s sidebarRules don’t apply, and all connections go direct. The filter and proxy stay in the system. The monitor doesn’t record.Turn the switch on.
Quit RoutekeeperThe icon’s menuOnly the window and the icon close. The extension keeps applying the rules. There are no notifications. In Ask mode, no prompts are shown: connections are allowed, and Routekeeper records “For Review” rules.Open Routekeeper from Applications.
Stop…Settings → ExtensionThe filter and proxy are turned off in the system: everything goes direct, and firewall rules don’t apply. The extension and the rules stay.Settings → Extension → Reinstall: the filter and proxy turn on by themselves. The switch won’t bring them back.
Delete…Settings → ExtensionThe network extension and both of its configurations are removed from the system. The rules stay on disk.Go through the welcome screen again: three permissions. The rules come back by themselves.

For an everyday “turn it off for a minute”, use the switch. For more about stopping and reinstalling, see Troubleshooting.

Remove Routekeeper

  1. If opening at login is on, turn it off: Settings → General → Open at login.
  2. Open Settings → Extension, and in the Stopping and Removing section click Delete…, then Delete. Routekeeper’s network extension, filter and proxy are removed from the system. macOS may ask for the administrator password.
  3. Click the menu bar icon → Quit Routekeeper.
  4. Move Routekeeper from the Applications folder to the Trash.

Rules and proxies stay on disk and come back if you install Routekeeper again. To delete them too, see the next section.

If you move the app straight to the Trash without step 2, macOS usually removes the extension by itself, sometimes after a restart. Check with the command from the next section, and check in System Settings → Network that no Routekeeper configurations are left there.

What stays on disk

WhereWhat
/Library/Application Support/RoutekeeperRules, proxies with passwords, settings, service lists for the extension, config.broken-…json backups. Only an administrator can open it. In versions 0.2.x: /Library/Application Support/AppProxy.
~/Library/Application Support/app.getroutekeeper.macThe downloaded service catalog, the servers from the setup wizard, when the license was last checked.
~/Library/Caches/app.getroutekeeper.macTraffic map data (about 55 MB; it appears after you first open the map) and the download cache.
~/Library/HTTPStorages/app.getroutekeeper.macInternal storage for the app’s network requests. macOS creates it.
~/Library/Preferences/app.getroutekeeper.mac.plistWindow settings: notifications, updates, whether you’ve finished the welcome screen.
System Settings → General → Login Items (Login Items & Extensions on macOS 15 and later)Opening at login, if you turned it on.
The keychain, items “Routekeeper license” and “Routekeeper server key”The license and the SSH keys of your servers.

You can delete all of this with commands in Terminal. Run them after you’ve removed Routekeeper with the steps above. Copy and run each command separately.

The first command deletes your rules and proxy passwords for good. If you might need them, export your rules first and save the passwords somewhere else.

Rules, proxies and passwords (macOS asks for the administrator password):

sudo rm -rf "/Library/Application Support/Routekeeper"

Service lists, caches and the app’s internal files:

rm -rf ~/Library/Application\ Support/app.getroutekeeper.mac ~/Library/Caches/app.getroutekeeper.mac ~/Library/HTTPStorages/app.getroutekeeper.mac

Window settings:

defaults delete app.getroutekeeper.mac

Delete the license and the server keys in the Keychain Access app: search for “Routekeeper” and delete the items it finds. Delete the license only if you won’t come back to Routekeeper on this Mac: otherwise you’ll have to enter it again.

Details: leftovers from versions 0.2.x

Versions up to and including 0.2.1 used the old identifier. If you installed them, delete these files too:

sudo rm -rf "/Library/Application Support/AppProxy"
rm -rf ~/Library/Application\ Support/dev.ilyabazenov.appproxy ~/Library/Caches/dev.ilyabazenov.appproxy ~/Library/HTTPStorages/dev.ilyabazenov.appproxy
defaults delete dev.ilyabazenov.appproxy

If a folder doesn’t exist, the command simply does nothing. In that case, defaults delete says that the domain doesn’t exist. This isn’t an error.

Check that the extension is removed

systemextensionsctl list

The output must not have a line with app.getroutekeeper.mac.extension (or with dev.ilyabazenov.appproxy.extension from versions 0.2.x). If there is such a line, marked to be removed after a restart (waiting to uninstall on reboot), restart your Mac.

Data and network

Where the settings are kept

Opening at login

Open at login (Settings → General) is offered on the welcome screen: the checkbox at the bottom is already ticked, and Routekeeper is added to login items when the screen closes. After that, you change it only in Settings. When it’s on, Routekeeper is listed in System Settings → General → Login Items (Login Items & Extensions on macOS 15 and later).

Even without it, after a restart the extension, filter and proxy start by themselves, and the rules work. Until you open Routekeeper, there’s no menu bar icon, no notifications and no prompts in Ask mode, and Routekeeper doesn’t check for updates or a newer service catalog.

Where Routekeeper connects on its own

Nowhere else: no analytics, no telemetry, no crash reports. Routekeeper finds the country and network for the traffic map in a built-in database, without going online. For details, see the privacy policy.

Details: addresses and signatures
  • The list of versions: getroutekeeper.app/appcast.xml over HTTPS.
  • The builds themselves: GitHub Releases. Each build is signed with the update key, and Routekeeper won’t install a file whose signature doesn’t match.
  • Service lists: the file domainsets/v2.json (v1.json in version 0.2.1) from getroutekeeper.app over HTTPS. The file is signed too, and both the app and the extension check its signature.
  • External IP: a GET /json request to ipinfo.io on port 80, through the proxy being checked.

Routekeeper’s own connections aren’t covered by your rules: the app itself has a built-in “direct” rule, and the extension runs the proxy check through the proxy itself.

Checked against the Routekeeper code (version 0.2.1 and the one after it) on October 4, 2026.