Skip to main content

Manage Connected Apps

Last updated November 5, 2026

Everything about your connections stays under your control on the Connected Apps page, in your account menu: what each one has done, whether it is still working, and how to end it.

Recent activity

The Recent activity table at the bottom of Connected Apps shows the 100 newest events, with When (US Eastern), What, App or client and Result (Done or Failed). It covers what happens to the connections themselves and what they do with your account:

  • Connections: App connected, Permissions changed, App disconnected, Account limits changed, App signed itself out, API access revoked after a sign-in change, App signed out after a sign-in code was used twice, App signed out after a sign-in token was used twice, Confirmation attempt (a passkey or authenticator check that did not pass), and for API clients API client created, API client suspended, API client re-enabled, API client deleted and API client secret replaced.
  • Bots: Bot created, Bot settings changed, Bot disabled, Trading paused, Bot enabled, Trading resumed, Approval requested, Request approved, Request rejected and Approved request carried out. The last six appear when an app or client turns a bot on, resumes trading or asks for your approval.
  • Backticks: Backtick created, Backtick cloned, Backtick settings changed, Backtick position added, changed or deleted, SweepTick created, SweepTick changed, Backtick run requested, Backtick run scheduled, Backtick scheduled run ended, Backtick run cancelled, Backtick moved to another section, Backtick moved to the trash, Backtick restored from the trash, Backtick permanently deleted and Backtick position converted to a bot.

A bot change made by a connection is shown to you again when you turn that bot on.

The notices you receive

The notices about connected apps and API clients are in the API/MCP category under Alerts on the Notifications settings page. New App Connected, API Client Created, API Client Secret Replaced and API Client Re-enabled are required, and their delivery choices are locked on. A New App Connected notice always arrives as an alert, and by email for the first connection of an app in an hour, so approving the same app again within the hour shows the alert without a second email. An API Client Created notice always arrives by alert and email, and so does an API Client Secret Replaced or API Client Re-enabled notice. The other three (a bot changed by a connected app, an approval needed, an action completed) have the same delivery choices as any other notification.

Status badges

An app's card shows a badge only when the connection is not simply active. An API client's card always shows one, Active when nothing is wrong. The other badges are:

  • Suspended after a change to your sign-in methods: see After you change your password below.
  • Paused: requires an eligible plan: your plan no longer includes API access. The connection comes back by itself when a plan covers the API again; there is nothing to click.
  • Ended: a sign-in token was reused: a used-up sign-in token was presented again, which is treated as a copied token, and the connection was signed out. Connect the app again if it was yours.
  • Suspended: an API client you suspended yourself. It works again when you select Re-enable.

When a connection stops working

An assistant's sign-in to tradeSteward lasts one hour and is renewed on its own while the connection is in use. A connection that has not been used for 30 days has to sign in again. To sign in again:

  • In Claude or ChatGPT, open the connector in settings and reconnect.
  • In Claude Code, run /mcp, choose tradesteward and sign in.
  • In Codex, run codex mcp login tradesteward.

If the consent page offers Replace the connection from an earlier date, choose it: the new connection gets the same permissions and limits, keeps access to the bots the old connection created, and the old connection is disconnected for you.

After you change your password, a passkey or two-factor settings

Changing your password, adding or removing a passkey, or turning two-factor authentication on or off ends the sign-in of every connected assistant and suspends every API client, because they were all signed in under your old sign-in methods. Recent activity shows API access revoked after a sign-in change. Each assistant only has to sign in again, as above; nothing else about its connection changes. An API client stays off until you select Re-enable on its card. See Account Security for the sign-in settings themselves.

Disconnecting and deleting

Select Disconnect on a card under Connected apps and the app loses access to your account right away. It can ask to connect again later, and you choose its permissions again when it does. Some assistants sign themselves out when you remove the connector on their side (Recent activity then shows App signed itself out), and others do not, so disconnect on Connected Apps when you want to be sure.

API clients are suspended or deleted, never disconnected. Suspend keeps a client, its permissions and its secret until you select Re-enable. Rotate secret stops the old secret right away and shows a new one once. Delete ends a client for good; it cannot be restored. Use the tradeSteward API From Your Own Code explains how your code uses one.

Bots a connection created stay in your account after it is disconnected or deleted. Backticks it ran stay in the API/MCP tab of the Library until they move to the Trash.

Related