Skip to content

Support custom chat launchers and independent inbox identity secrets - #22

Open
lhr0909 wants to merge 2 commits into
mainfrom
feat/custom-chat-launcher
Open

Support custom chat launchers and independent inbox identity secrets#22
lhr0909 wants to merge 2 commits into
mainfrom
feat/custom-chat-launcher

Conversation

@lhr0909

@lhr0909 lhr0909 commented Sep 8, 2026

Copy link
Copy Markdown
Member

Captioner needs to launch support from an editor toolbar while retaining the same conversation across navigation. renderLauncher now exposes the button props, open state, and unread state, including focus restoration for portalled controls. Existing floating launchers remain compatible. Packages are versioned together at 0.4.0.

The API also accepts dedicated IDENTITY_SIGNING_KEY_<inbox ID> secrets, so adding Captioner does not require replacing SubPorter’s existing secret map.

Validation: pnpm ready, npm build/consumer/tarball checks, and the API suite after the dedicated-secret change (32 tests). The React suite covers custom toolbar opening, Escape/close focus restoration, and the existing default launcher behavior (35 tests).

Rollout: SDK 0.4.0 is published to npm and dedicated inbox-secret support is deployed at https://api.respondkit.dev. Captioner is live using the custom launcher and its independent inbox secret. Production session checks verify accepted Captioner identities and rejected invalid signatures.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant