Help / connect in three steps

Support

Effective and last updated August 21, 2026

Recommended for @TeslrBot · no token management

Connect Teslr in three steps

  1. Connect X. Open the Teslr connection page and sign in with the X account you will use to tag @TeslrBot.
  2. Connect Tesla. Sign in through Tesla and approve the requested permissions. Teslr links that Tesla authorization to the verified X account for you.
  3. Add the virtual key. Pair it from your phone for each vehicle you want Teslr to control. The key is optional for read-only questions and required for supported vehicle commands.

That's it. There is no Teslr token to copy, paste, save, or post for the @TeslrBot flow.

Start the 3-step connection →

Optional for @TeslrBot history

Add Tessie to your X connection

After connecting X, choose Tessie on the connection page and enter your Tessie access token there. Do not post or message the token. Teslr validates it with Tessie, stores it encrypted, and uses Tessie for that X account's vehicle requests, including recorded trip and FSD mileage. Your Tessie plan and limits apply.

Remove it from the same Tessie row to fall back to a linked direct Tesla connection. Removing it from Teslr does not revoke the token at Tessie; rotate it with Tessie if it may have been exposed.

Never send support a secret

Do not post or message a Tesla credential, legacy Teslr or Tessie token, VIN, plate, PIN, invitation link, exact location, or trip history. Teslr support will never ask for one.

Unlink X and vehicle providers

  1. Return to the Teslr connection page.
  2. Choose Unlink.
  3. Sign in with the same X account to confirm.
  4. Optionally remove Teslr's virtual key from each vehicle in the Tesla app.

Unlinking removes the X-to-Tesla pairing, encrypted Tesla authorization, any encrypted X-linked Tessie token, management session, and private account-level activity record. The vehicle's virtual key must be removed separately in Tesla if you no longer want it paired.

Compatibility option

Using Bankr or another AI

The original private-token connection remains available for Bankr and compatible assistants. It is separate from the recommended @TeslrBot connection above.

  1. Start the Bankr-compatible Tesla connection from Teslr.
  2. Approve the requested Tesla permissions.
  3. Copy the one-time token into your assistant's secure settings as TESLR_FLEET_TOKEN.
  4. Pair the Teslr virtual key for each vehicle you want to control.
  5. Refresh the Teslr skill and ask it to list your vehicles.

Disconnect Bankr or Tessie

For the Bankr-compatible path, move to a clearly private assistant conversation, ask it to disconnect Tesla from Teslr, confirm the request, and delete TESLR_FLEET_TOKEN from its secure settings. You may also remove Teslr from Tesla's third-party app access and remove the virtual key from each vehicle.

For a Bankr or compatible-assistant Tessie connection, removeTESSIE_API_TOKEN from the assistant and revoke or rotate it through Tessie. These header-based compatibility requests remain stateless; only a token deliberately added on the signed-in X connection page is stored by Teslr.

If a compatibility token may be exposed

Stop sending commands. For Bankr or another compatible assistant, disconnect the Teslr connection and remove TESLR_FLEET_TOKEN. For Tessie, remove and rotate TESSIE_API_TOKEN. Reconnect only after the old credential is invalid.

Common setup messages

  • X connection failed: return to the connection page and retry from the same browser.
  • X account not linked: complete the three-step connection with the same X account that tags @TeslrBot.
  • Virtual key not paired: open the pairing link on the phone with the Tesla app and approve Teslr for that vehicle.
  • Scope required: reconnect from the connection page and approve the requested Tesla permission.
  • Command service unavailable: wait and try later; do not repeatedly send a command whose outcome is uncertain.
  • Rate limited: wait for the retry window rather than changing providers or repeating the request.
  • Command outcome uncertain: check the real vehicle state before any retry.

Contact

Contact @TeslrBot on X with a generic error code and approximate time only. Do not include vehicle identity, location, provider response data, credentials, or account linkage in a public post or direct message.