Check the environment first.
Reload the extension, refresh the YouTube tab, and confirm you are on a desktop watch page instead of Shorts or mobile YouTube.
Public support route
Use GitHub Issues for support and bug reports.
ScriptLens uses a public support path so extension behavior, transcript recovery questions, and release issues can be tracked in one place. Include the exact YouTube URL and the surface where the issue appeared.
Inline widget
Popup
Side-panel workspace
Include the exact video URL.
Support is fastest when the issue includes the YouTube link, the Chrome version, the extension version, and the visible error text.
Say whether recovery was enabled.
Transcript-availability issues are easier to triage when you note whether the build was the local-only store release or a custom recovery-enabled build.
Run the short checklist.
- Reload the extension from
chrome://extensionsand refresh the YouTube tab - Confirm you are on a desktop
youtube.com/watchpage - Try the inline button first, then use the workspace if you need more detail
- If the issue involves transcript recovery, note whether this build was local-only or had a custom recovery service configured
Give support the exact reproduction context.
- The full YouTube URL
- Whether the issue appeared in the inline widget, popup, or side panel
- The extension version and Chrome version
- Any visible ScriptLens error text or transcript-quality warning
Why does ScriptLens say the transcript is unavailable?
Some videos expose limited transcript data or block transcript text on the page. ScriptLens keeps the inline experience transcript-first. If local transcript recovery fails and you are using a custom recovery-enabled build, the extension can try that path before it reports that the transcript is unavailable.
Where this release works
This Chrome Web Store release is intentionally scoped to desktop youtube.com/watch pages. It is not a generic website detector and it is not designed for Shorts or m.youtube.com.
Hosted or self-hosted recovery
The recovery backend is optional and separate from the store package. The Chrome Web Store release is designed to stay local-only, while open-source deployments can use a compatible hosted or self-hosted backend for stronger transcript recovery on harder videos. The detector release does not depend on a public community workflow or posting surface.
When to open a new issue
Open a new issue when a stable watch-page flow regresses, when a transcript-rich video repeatedly fails, or when a release build behaves differently from the public privacy and support documentation.
Need the policy too?
Support and privacy should stay aligned.
The public policy and support pages are part of the same Railway-hosted site so Chrome Web Store reviewers and users see one consistent product story.