browser extension auth and limits
the browser extension uses the user's hold your voice account and related api routes to bring voice checks closer to where writing happens.
quick answer
extension behavior depends on auth, account plan, and supported browser state.
use this for
- extension setup support
- debugging extension sign-in
- explaining what the extension can and cannot do
steps
- install the supported extension build.
- sign in or approve the extension connection.
- open a supported writing surface.
- run the available check or suggestion action.
- return to the app for deeper document and profile management.
details to know
- extension routes share product concepts with the app: analysis, memory, suggestion events, and api key self-management.
- the extension should respect the same voice profile and plan rules as the core product.
- browser support should be stated plainly when a browser is not ready.
limits and edge cases
- do not imply public store approval before it exists.
- extension auth problems should not be solved by sharing api keys in the browser.
- large document management still belongs in the app.
ready to use the product instead of reading about it?
open app