Why linking lives in the web app, not tCode

Linking and unlinking a connector both happen entirely inside the tAI web app's Settings, never inside tCode itself. This is a deliberate architectural choice, not an oversight or a missing feature.

Connector access is fundamentally an account-level permission, granted once through each provider's own genuine login flow, Gmail through Google's OAuth screen, GitHub through its own, the same flow the browser composer already relies on.

It applies identically whether you are searching from the browser composer or from a terminal running tCode. Revoking access in Settings takes effect immediately everywhere at once, including any machine currently signed in and mid-session.

This centralization is what makes revoking access actually meaningful as a security control; if linking lived separately per surface, revoking it in one place would leave a false impression of having cut access that another surface still had.

It also means there is exactly one place to check the status of every connector at once, tai.artfical.com's Settings, rather than needing to audit each surface tCode runs on individually to confirm what is actually still linked.