This video shows an example of how to select and load an archive:
This will open a new tab which makes no network requests and instead uses archived responses instead.
The archive loader extension uses the Chrome Debugger Protocol, so you'll see a "DebugBear Archive Loader is debugging this browser" message.
Not right now, please email firstname.lastname@example.org if you're interested in this.
Since the loaded page may depend on a certain set of login data, cookies are set to what they were when the archive was captured. They are reset to the normal state when you finish using the archive.
This means that if you're logged into example.com and then load an example.com archive you will be temporarily logged out of your normal account.
You could avoid this problem by creating a separate Chrome Profile to load the archive in.
Some reasons why loading an archived page may not work correctly:
The request interception feature used by the Chrome extension isn't fully stable yet, so in rare cases you may run into problems.
If you can't close the tab click the "Cancel" button in the "DebugBear Archive Loader is debugging this browser" message. This will detach the archive loader extension and reset the login state.
If the normal page is loaded instead of the archive try restarting your browser. This can happen if you recently created the Chrome profile you're running the extension in.