Something broke. What exactly?
Choose the symptom below for the shortest first-pass checklist. If that does not solve it, the deeper sections explain what to inspect next.
- Confirm the extension is enabled in your browser.
- Confirm you are on a supported Clank chat route.
- Reload the Clank tab.
- If you just reloaded or updated the extension, reload the tab again so the page gets the new extension context.
The browser cannot load Furina.
When you use Load unpacked, choose the extracted Furina folder itself — not the directory above it and not the ZIP file.
Chromium's Load unpacked workflow expects normal extension files on disk.
After replacing files, use the browser extension page's reload control and then reload the Clank tab.
The normal chat launcher is intentionally tied to supported chat routes rather than appearing everywhere on the site.
The launcher exists, but Furina feels stale.
Useful for a one-off UI state issue.
Rebuilds Furina against the current page DOM.
Use this after updating files or when the extension context was invalidated.
An already-open page cannot automatically use a content-script context that was destroyed by an extension reload.
Reload the browser extension, then refresh the affected Clank tab. The message is about the extension runtime context, not automatically evidence that your saved Furina data was erased.
If one conversation looks different from the rest, check Theme Scope before assuming the theme failed to save.
Image or live wallpaper problems.
A webpage URL that merely contains an image is not the same thing as the image file itself.
Sites can block hotlinking, require authentication or return HTML instead of a playable media file.
Short videos whose first and last frames are visually compatible tend to produce the least noticeable loop transition.
A heavy overlay can hide grading and parallax. Extreme blur can also make movement difficult to notice.
The player is there, but there is no sound.
Browsers can restrict autoplay until a user gesture has occurred.
Make sure the source is loaded, the player is not paused and volume is above zero.
Direct audio, SoundCloud and YouTube use different playback paths.
If the external source is unavailable or embedding is blocked, Furina cannot make that source playable.
Furina can request playback, but browser media policies still decide whether audio is allowed to start without interaction.
Visual Novel or Phantom looks incomplete.
Visual Novel Mode builds its local sequence from the current conversation source rows. Upstream DOM changes or unusual message structures can affect parsing.
Group-scene portrait matching depends on speaker names and scene-member information Furina can resolve.
The alternate interface may need to rebuild its local representation after the source chat changes.
Furina deliberately relies on the real composer/send flow. If Clank's own composer is unavailable, the alternate composer cannot safely bypass it.
When the simple fixes are not enough.
Use Furina's diagnostics when you need to inspect what the extension believes it can see on the current Clank page.
Theme, Full Setup, Story Bible and Miyabi profile exports exist so you can preserve useful state before destructive troubleshooting.
Know what Furina cannot promise.
When troubleshooting rendering or alternate-interface behavior, returning to the native chat is the best way to distinguish a Furina presentation issue from the underlying conversation state.
Check what changed between versions.
The release page keeps the documented version and current download in one place.