How is a Site Pack different from a built-in adapter?
Built-in adapters may contain site-specific TypeScript for complex behaviors. Site Packs are declarative JSON. Built-in adapters take priority and cannot be overridden by a Site Pack. Selector-only fixes for configured built-in adapters use the signed patch channel instead of a Site Pack.Are community packs official Ophel code?
Registry packs are community-contributed manifests reviewed and published through the Ophel registry workflow. They use the same validator and signed distribution chain, but their supported capability set may be narrower than a built-in adapter. The management page shows the pack source and declared capabilities.Why does the extension request access to another domain?
Ophel needs optional host permission before it can register content scripts on a Site Pack origin. The request is limited to the pack’s referenced HTTPS origins. Denying it rolls back the installation or binding operation.Can one pack support self-hosted instances?
Yes. A pack can use an emptymatches list so it never activates on its own. Bind each HTTPS origin to the pack from Settings → Site Packs → Custom sites.
Ophel stores each instance under a key derived from pack ID and origin, so settings, themes, reading history, and conversations do not mix between two deployments of the same pack.
Do registry packs update automatically?
Registry-origin packs participate in the remote registry update flow. The client checks the signed index, version compatibility, immutable package hash, and runtime schema before applying an update. A failed or invalid download does not replace the last-known-good state. Local imports do not update automatically. Import a higher-version local JSON file when you want to replace one. The default check interval is 24 hours.What happens when I disable or uninstall a pack?
Disabling keeps the manifest but stops it from activating. Uninstalling removes the manifest and its registration references. User settings and conversation data are retained. An origin registration is removed only when no enabled pack or custom binding still references it.Can a Site Pack run arbitrary JavaScript?
No. Site Packs intentionally reject scripts, expressions, executable callbacks, remote resources, and unrestricted CSS. Complex integrations that require imperative code must be implemented and reviewed as built-in adapters. There is no remote-executable plugin mechanism in the current product.What page data is sent to the registry?
Installing or updating a registry pack performs static CDN / GitHub GET requests for the signed index and package JSON. Those requests do not include conversation content, prompts, cookies, or page DOM. The optional AI selector-draft helper in the wizard also performs no automatic upload: it creates a bounded structural prompt only when you copy it, and you choose whether and where to share it.Is a local JSON import safe?
Local imports still pass the Site Pack validator, so unknown fields and unsafe declarative values are rejected. They are not authenticated by the signed community registry, however. Review the target domains and capabilities and import only from a source you trust.A selector stopped working. What should I do?
- Confirm the pack is enabled and the origin still matches.
- Check for a registry update if the pack came from the online library.
- For self-hosted packs, confirm the custom origin binding is still correct.
- If the latest pack still fails, open a GitHub issue with the site URL, Ophel version, pack version, and failed selector names.
- Remove account details and private conversation content from the report.
Does Ophel auto-detect self-hosted domains?
No. The current design uses explicit origin binding. Packs with emptymatches stay inactive until you add an exact HTTPS origin under Custom sites.