Accounts and API access
tCode signs in with your regular tAI account, the same one you already use at tai.artfical.com in the browser. There is nothing separate to create or configure: the models you talk to through tCode are the same models, on the same account, as the ones you would reach by opening tAI in a browser tab.
- Signing in through a short device-code flow
- Usage and limits, the same plan as the browser
- Why API keys are a different surface entirely
- Why the two are easy to conflate
- How memory carries over between browser and terminal
- Logging out, per machine, not per account
- Why there is no alternate login path
- How a plan change is reflected
Signing in
Signing in happens through a short device-code flow: tCode opens auth.artfical.com in your browser and asks you to enter a code back in the terminal to link the two.
Usage and limits
Because tCode uses your existing account rather than a separate license or key, usage through tCode counts against whatever plan that account is already on, and any limits that apply to your account in the browser apply the same way here.
API keys are a different surface entirely
If you are not using tCode itself but instead building your own tool or integration that calls tAI models directly, API keys and usage tracking for that are managed separately at console.artfical.com.
Why the two are easy to conflate
These two things are easy to conflate because they both ultimately reach the same underlying tAI models, but they solve different problems.
How memory carries over
Your memory, saved instructions and preferences tAI remembers across conversations, carries over automatically between the browser and tCode, since both read from the same account.
Logging out
Logging out with /logout only affects the current machine.
Why there is no alternate login path
An account can only be signed in through the normal device-code flow; there is no alternate way to authenticate tCode itself with a console.artfical.com API key in place of a real login.
How a plan change is reflected
If your account's plan changes, an upgrade, a downgrade, a change in which models are available, that change is reflected in tCode the next time it checks, through /usage or /model, without anything needing to be reconfigured locally; tCode always reflects the current state of the account it is signed in with rather than a cached view of it from when you first logged in.