The name behind the noise
If you have seen “Tibo” repeatedly in this week’s AI discussions, the short answer is probably not that a new OpenAI model has suddenly acquired a public co-author. It is that one public account has become a useful signal for a different OpenAI product: Codex.
Tibo—identified in public references as Thibault Sottiaux, posting as @thsottiaux—is closely associated with conversations about Codex usage limits and reset timing. That association has become its own small information market: community pages now track his public activity and turn it into “reset radar” updates. Once GPT-6 Astra entered the conversation, the existing Codex audience gave the name a ready-made distribution channel.
That explains repeated mentions better than a confirmed Astra connection does.
What Astra actually confirms
OpenAI’s official model documentation describes GPT-6 Astra as its most capable model for difficult end-to-end work, including reasoning, coding, computer use, research, and document creation. The page lists a 1,050,000-token context window, up to 128,000 output tokens, image input, tool support, and pricing of $10 per million input tokens and $50 per million output tokens. It also says that requests above 272K input tokens receive different pricing. This is a live model reference rather than a dated launch post; the Article metadata uses the public indexed entry date, not a date printed on the page.
Those details are primary evidence about the model’s documented interface and economics. The page does not identify Tibo, connect him to Astra’s training or engineering, or cite his social account. That absence does not prove he has no connection; it means the public documentation does not establish one.
The same distinction applies to social posts. A post that appears shortly before a rollout, hints at a quota change, or uses language that sounds like an internal codename can be interesting evidence about what a community is watching. It is not, by itself, evidence of employment, authorship, privileged access, or knowledge of a model’s architecture.
Why the rumor sticks
There is a simple feedback loop here. Codex users want early information about availability and limits. Tibo’s account is already treated as relevant to that problem. A new model announcement creates uncertainty. Readers then reinterpret familiar Codex signals as possible Astra signals, while trackers and reposts make the association more visible. Visibility becomes mistaken for confirmation.
The safer reading is narrower: Tibo may be an early community signal for Codex-related changes, and his posts may influence how people discuss OpenAI releases. That is different from saying he built Astra or speaks for OpenAI.
If you are tracking the story, keep three tabs separate: OpenAI’s official model documentation for capabilities and pricing; Tibo’s original account for what he actually says; and community trackers for how the audience interprets it. Do not collapse the second and third into the first. Until an official source or an attributable statement makes the connection, “Tibo is related to Astra” remains a rumor, not a product fact.