No separate setup inside tCode itself

None of the four connectors require any special configuration inside tCode itself beyond being linked once in tAI Settings at the account level.

There is no separate API key to paste into a config file, no extra sign-in flow specific to tCode's use of a given provider; the same account-level connection the web app already relies on is exactly what tCode reads from.

This mirrors how account authentication itself works, covered in Accounts and API access: one login, reused everywhere, rather than a separate credential per surface.

This absence of setup is a direct consequence of connectors being an account-level feature rather than a tCode-level one; there is nothing tCode-specific to configure because tCode is not the thing holding the connection in the first place.

It also means there is nothing extra to install or update on a given machine when a new connector becomes available; the moment it is linked at the account level, it is usable from tCode on any machine already signed in, with no separate rollout step.