Understand extension status and Technical Details
Crest treats compatibility as an observed runtime result, not a promise based only on a manifest.
Running
Running means the extension is enabled, its WebKit context loaded, and Crest has not observed a startup runtime error. It does not certify every website, account flow, native-companion authorization, optional feature, or future extension update.
Needs attention
Needs attention means an enabled extension did not load or reported a runtime failure. Expand its row in Crest Settings → Extensions to see a plain-language explanation.
Try these smallest steps first:
- Turn the extension off and back on.
- Update or reinstall the extension.
- Check whether the failing feature depends on an API listed under Unsupported APIs.
Blocked
A blocking compatibility message appears during installation when Crest can identify a requirement it cannot satisfy safely. Add Extension remains unavailable, and Crest explains the boundary before creating a misleading installation.
The App Store build blocks native-companion access because it is sandboxed. Crest Direct also blocks unpacked extensions, unknown store identities, and native-host manifests that do not explicitly allow the verified Chrome Web Store extension ID.
Off
Off means the extension remains installed in the Space but is disabled. Its stored configuration remains available for the next time you enable it.
Technical Details
When an installed extension reports a runtime problem, the user-facing impact appears first. Open Technical Details to see the JavaScript errors reported by the extension and WebKit.
Technical Details are intended for troubleshooting and bug reports. They can identify the failing API or script, but an error string alone does not prove that every other extension feature failed.
Continue with Troubleshoot partial extension compatibility for a measured recovery sequence and the current named WebKit limitations.