diagnostic · one of 36 free, no counter
Environments
What is different between staging and production?
The reason a bug reproduces on staging and not on production is almost always something neither environment lists: a different script version, a header that is set in one place, a token that resolved differently. This captures a reading on one and compares it against a reading on the other, so the answer is a diff rather than two tabs and a memory.
Reach it Press ⌘ + K on any tab and type environments. Ctrl + K on Windows and Linux
in the panel · free, no counter
What this actually is
the same page in two environments, comparedAny time a bug is environment-specific, and before a release as a sanity check that staging is actually the thing being shipped. Both readings are taken by you, on pages you have open - nothing is fetched.
Asked about this diagnostic
4 of themDoes it fetch the other environment for me?
No. The extension holds no permission over any host, so both readings are taken on tabs you have open. That is also why the comparison is honest - each side is the page as it really rendered.
What counts as a difference?
A detected technology and its version, a security header, a resolved design token, a resource that is on one side and not the other. The list is what two readings can be compared on without guessing.
Can I compare two different sites?
Yes, mechanically - nothing stops you. The report is written for two environments of one site, so a comparison of unrelated sites will be mostly noise.
How long are the readings kept?
Until you clear them or take a new one. They are a working comparison, not a history, and nothing accumulates.
how to use environments
- Open the staging page and take a reading from Environments.
- Open production in another tab and take the second reading there.
- Read the diff: stack, headers, tokens and resources come back as differences rather than two lists.
- Clear the stored readings once the question is answered.
70 of these · no host permissions · three free audits