Built by the same team as tAI

tAI, the models underneath tCode, is developed by Artfical, the same team responsible for tCode itself. The two are not built as a first-party product and a third-party client bolted onto it afterward; they are developed together, which is why the model side and the terminal side stay in step with each other.

In practice this means an improvement to how the underlying model reasons about code, or how well it holds up over a long agentic session, lands directly in tCode's own behavior. There is no separate integration layer sitting between the two that a change would need to be ported across or that could fall out of sync.

This is also why account, memory, and billing are unified rather than parallel systems: signing in to tCode is signing in to the same tAI account you already have, not creating a second, tCode-specific identity to manage. See Accounts and API access for exactly how that plays out.

It is also why tCode's own security posture, described in full in Security, is built on the same foundations as the rest of the tAI product rather than a separate, bolted-on set of protections specific to the terminal surface.

In practice this means tCode is treated internally as a first-class way of using tAI, not a side project maintained separately from the core product. Feature parity and security review both follow from that, rather than needing to be requested or negotiated separately for the terminal surface.