INVALID_TOKEN

What triggered it

The agent backend got a request from your browser, but the session token attached to it didn’t pass validation. There are three usual reasons:

• Your session expired. Sessions are short-lived (rolling 7 days) so a stolen cookie can’t ride forever.
• You signed out in another tab, and this tab is still trying to use the old token.
• A new server build invalidated the signing key. Rare, but it happens during a deploy.

Your bots are fine

INVALID_TOKEN is a session problem, not a bot problem. Anything you’ve already deployed keeps running. You just need to re-authenticate to talk to the dashboard.

What to try

1. Sign back in. Go to the app and sign in with Discord. You’ll be back where you left off in seconds.

2. Hard-refresh after sign-in. If the error keeps showing after sign-in, hit Ctrl/Cmd+Shift+R to clear cached state.

3. Check your clock. Token validation depends on the system clock. If your machine’s clock is way off, sign-in can fail silently.

Open the app

When to contact support

If you’re seeing INVALID_TOKEN repeatedly even after signing back in:

• Drop a screenshot in Discord
• Or email support@vibecord.dev with your account email and the time it happened

We can check the auth logs and tell you exactly what got rejected.