How a plan change is reflected

If your account's plan changes in any way, an upgrade, a downgrade, a change in which models are available to you, that change is reflected in tCode the very next time it checks, through either /usage or /model.

Nothing needs to be manually reconfigured locally on any machine for this to take effect; tCode always reflects the current, live state of the account it is signed in with rather than a cached view of it from whenever you first logged in there.

Signing in through tCode does not create a separate identity or profile distinct from the one you already have; it is the exact same account, immediately recognizable in the tAI web app's own account settings, with no separate management surface specific to tCode logins to keep track of.

This applies to a downgrade the same way it applies to an upgrade; if a plan change removes access to a model you had been using, /model reflects that immediately, showing only what is currently actually available rather than a stale list from before the change.

None of this requires any action on your part beyond normal use; there is no separate step to "sync" tCode with a plan change, checking /usage or /model the next time you happen to use them is sufficient to see the current state.