Projects, import & export

Projects

Projects group rules and act as a master switch: disabling a project disables all of its rules. Rules match in order — projects top to bottom, rules within a project top to bottom — and the first enabled hit wins. Drag rows to reorder (disabled while a filter or search is active).

Switches, in priority order

• Global switch (popup or panel top bar) — off suspends every rule in every project.
• Project switch — off suspends that project’s rules.
• Rule switch — off suspends that rule only.
• A rule is dimmed in the list when any of the three is off or when the plan quota trims it; a rule that cannot be compiled into a network request rule is tagged Inactive instead. Hover either for the exact reason.

Export

Export (panel top bar) saves every project — rules, conditions, responses, JS code and sequence steps — as a single JSON file. Use it as a backup before uninstalling, before a big refactor, or to share a scenario with a teammate.

Import

Import reads a Mockrew export, an OpenAPI / Postman document or a cURL command. For a Mockrew file you choose Replace (wipe current projects first) or Merge (add to what you have, replacing same-id projects in place). Importing a file that contains JS code shows a trust warning — only import files from sources you trust.

The importer always reads the whole file first. On the Free plan what actually gets written is trimmed to the available quota at the moment you confirm — Replace fits the first 2 projects and the first 20 rules in file order, while Merge only takes what is left after your current projects (a project with the same id is replaced in place, freeing its quota). Whatever is trimmed is reported right after the import, so you can upgrade to Pro or split the file and import it in parts.

Storage

Everything lives in chrome.storage.local, which Chrome caps at 10 MB per extension. Response bodies, JS code and sequence steps all count. When the limit is hit, the panel says so explicitly and asks you to export a backup before trimming — it never silently drops a rule.

Network request rule budget

Chrome caps declarativeNetRequest dynamic rules at 5,000 per extension. Headers and Redirect rules each take one rule; Mock and Rewrite rules do not. The panel warns from 4,500 used rules, because past the cap Chrome rejects the whole batch — which would disable every network request rule at once.