browser extension
the browser extension connects outside writing surfaces to hold your voice. it uses extension auth, analysis, memory, tracking, and key-revoke routes.
quick answer
use this page for extension-facing product behavior, not public store copy.
use this for
- explaining extension auth
- checking backend route expectations
- reviewing privacy behavior before launch
steps
- install the extension build for the browser.
- start the extension auth flow.
- approve access from the hold your voice web flow.
- analyze text from the extension surface.
- send suggestion events back to voice memory when supported.
- self-revoke extension keys when access should end.
details to know
- extension routes include auth approval, free analysis, tracking, memory, suggestion events, and rest-key self revoke.
- real-browser qa is still required before public launch.
- safari may need extra onboarding decisions depending on identity flow.
limits and edge cases
- extension docs should say if a browser is not yet publicly supported.
- do not imply store approval before it happens.
ready to use the product instead of reading about it?
open app