FURINACLANK CHAT ATELIER
DOCUMENTATIONReleases
Browse Guides
STABLE RELEASE

Furina 1.3.1

Furina 1.3.1 remains the recommended stable build. The 1.3.2 Developer Preview is optional and documented separately below.

STABLE · FURINA: CLANK CHAT ATELIER1.3.1

Recommended build · Chromium ZIP package

Download extensionFurina 1.3.1
1.3.1 focuses on making Furina easier to enter.

The Essentials interface provides a wider, calmer, intention-based panel while keeping Full Atelier and the underlying Furina managers available for advanced control.

02
DEVELOPER PREVIEW

Try 1.3.2 before it becomes stable.

This build is available for users who want the newest chat customization and RP interaction tools and do not mind reporting an occasional bug.

DEVELOPER PREVIEW · MAY RECEIVE FIXES1.3.2

Chromium ZIP package · optional test build

Download developer buildFurina 1.3.2 DEV
Atelier Markup

Cards, scene headers, meters, details, tooltips, inline effects, interactive choices and dice inside standard chat.

AaChat presentation

Message skins, composer skins, dialogue presentation, optional speaker nameplates and typing-indicator styling.

Roleplay SFX

Automatic assistant-event detection, custom triggers/URLs, plus manual next-send cues from the composer.

HUD skins

Arcane, Cyber, Gothic, Terminal and Minimal Luxe frames built from code and layered with existing Decor controls.

Developer Preview means exactly that.

1.3.2 may receive bug fixes or small behavior changes while it is being tested. Keep 1.3.1 if you prefer the stable path, and refresh already-open Clank tabs after replacing/reloading an unpacked build.

NEW FEATURES GUIDE

See how the 1.3.2 systems work.

The Developer Preview guide covers Atelier Markup, choices, dice, message/composer skins, Quote to Composer, interface sounds, RP SFX and HUD skins.

03
HISTORY

How Furina got here.

This is a concise release-family history rather than a line-by-line commit log.

DEV PREVIEW1.3.2

Chat performance & interaction

Experimental 1.3.2 work adds Atelier Markup, choices/dice, message and composer skins, Quote to Composer, interface/RP sounds, manual user sound cues and Chat Frame / HUD skins.

Atelier MarkupRP SFXHUD SkinsTesting
STABLE1.3.1

Essentials polish

Added and refined the beginner-friendly Essentials experience while preserving Full Atelier. The current site documents this build.

EssentialsPanel comfort pass1.3 release family
MAJOR1.3.0

The roleplay-tool expansion

Furina grew beyond visual customization with Director, Continuity, Story systems, Response Styles, bookmarks/chapters, alternate interfaces, profile customization, Guidebook work and other major additions.

DirectorContinuityStory ToolsVN / Phantom
FOUNDATION1.2.0

Compatibility and media

Expanded browser and media support while continuing the customization foundation, including the release-family work around Firefox packaging, YouTube and SoundCloud behavior.

MediaCompatibilityLocalization
EARLIER1.1 / 1.0

The Atelier takes shape

Established the stable renderer, theme system, visual customization, stickers, Reader/Focus tools, ambience and the original release-ready browser extension foundation.

RendererThemesStickersImmersion
04
UPDATING

Keep the browser and tab in sync.

1Export anything important

Use the appropriate Theme, Full Setup, Story Bible or Miyabi backup before a major update or install-path change.

2Replace the installed folder's files

For an unpacked Chromium install, keeping the same folder path is the safest way to preserve the same extension identity.

3Reload the extension and Clank tab

Use Reload in the extension manager, then refresh any already-open Clank pages so they receive the new extension context.

4Check your important state

Confirm themes, conversation-specific state and story tools behave as expected before deleting your backup.

Back up important setups before major changes.

Use Theme, Full Setup, Story Bible or Miyabi exports where appropriate. The portability guide explains what each one preserves.

05
DIRECTION

Furina does not need infinite features.

The project direction is to prefer real usage, stability, maintainability and usability over adding features only for hypothetical completeness.

01Fix real problems first

Crashes, broken state, renderer issues and major compatibility problems should beat novelty.

02Keep systems understandable

Essentials and the Guidebook exist because a powerful feature is not useful if nobody understands where to find it.

03Let users drive expansion

Future features should earn their complexity through actual need.

START USING IT

Choose stable or preview.

Use Getting Started for the stable install flow, or open the 1.3.2 guide if you are testing the Developer Preview.