Support

Install the extension

The Chrome Web Store listing is in preparation. Once it is approved, this will be the only step needed: install from the store and let the browser keep it up to date.

Installing from the package

In the meantime, or if you are working with an internal build, the extension loads unpacked:

1. Unzip the package you received into a folder that will stay put — if you move it, the browser loses it.
2. Open chrome://extensions or edge://extensions.
3. Turn on Developer mode.
4. Click Load unpacked and pick that folder.
5. Reload any tabs you already had open: the old interceptors stay active until the page reloads.

Requirements

• Google Chrome or Microsoft Edge 114 or newer, which is when the side panel arrived.
• Any desktop operating system those browsers run on.
• Nothing else: there is no server to configure and no account to create.

First steps

1. Click the extension's icon. The side panel opens, which is the full interface; it also exists as a DevTools panel if you would rather keep it there.
2. Add the site you are working on to the scope. Out of the box the scope is restricted and the extension acts on no page: this is the step people forget, and reason number one for an empty capture list.
3. Turn on the master switch.
4. Reload the page. Calls start appearing in the capture list.
5. From any capture you can create a rule, and from there mock the response, patch a field or edit the request.

Keyboard shortcuts

Three shortcuts belong to the browser, which is why they work with the panel closed. You can change or remove them at chrome://extensions/shortcuts.

The rest of the shortcuts live inside the panel and the full list is in the interface's own help.

Common problems

The capture list is empty

In order of likelihood: the site is not in the scope, the master switch is off, or the page has not been reloaded since you changed one of those two.

Some calls never show up

The page layer intercepts the document's fetch and XMLHttpRequest calls. It does not see the navigation itself, images and stylesheets, or service worker traffic. That is what deep mode is for — it reaches all of it, at the cost of the browser's debugging notice (why it needs that permission). Keep the general rule in mind: a call missing from the list is not proof it did not happen.

Deep mode will not attach

A browser allows one debugger per tab. If DevTools is open on that same tab, close it and try again. The error shown in the settings is the one the browser returned, untranslated, exactly so it can be searched for.

My captures disappeared

Captures are deleted when you close the tab that produced them. This is deliberate — it is explained in the privacy policy. If you need to keep them, export the HAR before closing.

A rule does not fire

The rule editor includes a diagnosis that tells you why: the pattern does not match, the method does not, a condition is unmet, or another rule covers it first. Start there before rewriting the pattern blind.

I changed the configuration and the page behaves the same

Changes apply live, but the interceptor already inside a page is not replaced: if you reloaded the extension from the extensions page, reload the tabs as well.

Network rules are not being applied

The panel's status bar reports when the browser rejects the network rule sync or when a rule was dropped for exceeding the quota. If something in the network layer has no effect, that notice is the first place to look.

Report a problem

Write to jesusandrescorreal@gmail.com. These five things usually pin a problem down without further back and forth:

1. Extension and browser versions.
2. What you expected to happen, and what happened.
3. The smallest set of steps that reproduces it.
4. If the rule involved can be shared, its export.
5. Console errors, if any: both the page's and the extension process's.

Contact

Jesús Andrés Correal Ortiz — jesusandrescorreal@gmail.com.

Support is handled by one person, so there is no committed response time; reports with clear steps to reproduce are the ones that move first.