Support
For help or bug reports, email arman.hilmioglu@gmail.com. Include the extension version, Chrome version, steps to reproduce, and an example using non-sensitive test URLs. Remove tokens, personal information, and private request details from screenshots.
Getting started
- Open the website you are testing and enable the extension’s master switch.
- Reload the page, open the extension, and view Requests from this tab.
- Add an exact HTTP/HTTPS request URL, choose URL redirect, Respond with a local file (version 2.1), or Block request, and save.
- Reload the page to exercise the rule. Remove the rule in Existing rules when finished.
Troubleshooting
Rules apply to the active tab in the last focused window and require an exact URL match, including the query string. Chrome restricts interception on protected browser and store pages. Redirects remain subject to browser security restrictions. In version 2.1, local-file responses require Chrome 125 or later and use the required debugger permission. Choose a file no larger than 2 MiB, then save the rule and reload the test page. Chrome displays a debugging banner. Cancelling it pauses monitoring; close DevTools or competing debuggers and explicitly enable traffic to resume. Files are stored snapshots: select the file again to update it. Removing a local-file rule deletes its saved contents; removing the last local-file rule detaches the debugger. Local responses use status 200 and the file MIME type. Browser security restrictions still apply. Response-header editing, status-code editing, and timeout rules are not supported.