Support diagnostics

Written by , founder at Vibe Typer

Know which diagnostics help support investigate issues and what sensitive data you should not send manually.

Vibe Typer includes diagnostic tools for troubleshooting recording, insertion, authentication, and subscription issues.

Create a diagnostics bundle

Use the in-app diagnostics bundle when support asks for more detail. The bundle collects the app version, platform, logs, and configuration details that help diagnose issues.

Do not create or send diagnostics unless support asks for them.

What not to send manually

Do not manually send:

  • Raw audio recordings.
  • Transcript history or copied transcript text unless support specifically asks for a small redacted example.
  • Clipboard contents.
  • Passwords, OTP codes, access tokens, refresh tokens, or API keys.
  • Full authenticated URLs, WebSocket URLs, or request headers.
  • Payment card details.

If support needs an example, redact names, addresses, account numbers, access tokens, private messages, and any other sensitive content first.

Useful context to include

When reporting an issue, include:

  • Operating system and version.
  • Vibe Typer app version.
  • Whether the issue affects recording, insertion, sign-in, billing, or AI commands.
  • The target app where insertion failed, if relevant.
  • Whether the issue started after an update, OS permission change, or device change.