Docs Settings and safety

Manage AI assistant tokens and connected tools

Check which AI tools, tokens and machines can reach your Relia account, and disconnect or revoke the ones you don't use.

AI tools (Claude Code, Cursor, Codex…), scripts and the relia-sdk CLI reach Relia as you. This page shows where to see them all and how to cut off the ones you don't use. A good habit: check once a month.

Open your Profile

Click your name at the bottom of the sidebar. Two cards matter here: Use Relia in your AI assistants and CLI tokens.

Connected tools (sign-ins)

When you set up your AI tools with:

npx -y relia-sdk@latest mcp install

each tool asks you to sign in to Relia the first time. No token is copied anywhere.

Every tool you signed in from is listed under Connected tools, with:

  • its name,
  • the projects it can see (all projects, or how many you chose),
  • when it was last used.

To remove one, click Disconnect. There is no confirm step: it is removed at once, and that tool loses its access. If you disconnect every tool, the Connected tools list goes away. Need a tool back? Set it up again and sign in.

Tip: watch Connect Claude Code, Cursor and Codex to Relia (MCP setup) (2 min).

Tokens for CI and scripts

For a script, CI, or a tool that can't sign in, open Use a token (CI and scripts) on the same card.

  • Create a token: give it a name (for example CI) and click Create a token. Copy it right away: Relia shows it only once. Use it with --token or as RELIA_MCP_TOKEN.
  • Your tokens are listed under the form: each shows its name, its last characters and when it was last used.
  • Revoke: click it next to a token you don't recognise or no longer need. Again, it is gone right away.

Keep tokens private, like a password. Relia stores only a fingerprint of each token, never the token itself.

Projects created before account-wide tokens may also have older one-project tokens. Find and revoke them in the project's Settings → Advanced → Integrations.

CLI tokens

CLI tokens are the machines where you ran npx relia-sdk@latest init, plus the upload-only tokens it made for source maps (RELIA_TOKEN). Each shows the machine, when it was last used and when it expires.

  • A setup token can only set up projects and services. It can't read your data.
  • An upload-only token can only upload source maps for one project.
  • Click Revoke next to any you don't recognise.

When tokens expire on their own

Kind Expires after
CLI setup token 30 days without use
Upload-only token for source maps 180 days without use
AI assistant token (CI and scripts) 90 days without use
AI tool sign-in 90 days without use

Each use pushes the expiry forward.

What an AI tool can do with access

It reads: what needs you, incidents, fix plans, dashboards, requests, logs and more. Anything that writes (marking a fix, acknowledging an alert, recording a deploy, creating a project) needs your confirmation first and is written to the project's audit log. It can't change settings, delete data or see passwords.

If you think someone else has access

  1. Disconnect every tool and revoke every token you don't recognise.
  2. On your Profile, click Sign out everywhere. It ends every browser session and every CLI token.
  3. Change your password if you think it leaked. A password reset also signs you out everywhere.

Your Profile's Recent account activity lists sign-ins, including failed attempts.

Next

Last checked against the product: 1 Nov 2026