AISubHub/AI news
Developers

News brief · About 2 min read

Tibo reports OpenCode recovery and refunds of affected API credits

An October 19 post describes help for OpenCode users who also use the OpenAI API, plus applications for defensive Daybreak Blue access.

Published here
Source published
Source checked

Original X post

Author and role: @thsottiaux · OpenAI Codex team; described as Codex lead in OpenAI’s May 2026 event

Identity evidence () · Source published:

Tibo’s complete public post card, showing his name and handle, the displayed time of 12:12 PM on October 19, 2026, and public views and interaction rows.

The displayed original-post card omits the left navigation. Visible counts are a snapshot at capture time, not independent AISubHub statistics.

A reviewed screenshot of the public original post, shown as editorial evidence. Rights remain with the original rights holders; this does not imply a reuse licence.

Screenshot captured:

In an October 19 post, OpenAI Codex team member Tibo (@thsottiaux) said his team had worked with OpenCode to restore service for its users who were also OpenAI API customers and refund credits the attack may have consumed. This is an attributed account of that earlier incident, not confirmation that any particular customer has received a refund.

Listen to the news

Read this article aloud or keep listening to the news.

Tibo reports OpenCode recovery and refunds of affected API credits

Preparing the reader…

Device voice

Speech is handled by your browser or device. AISubHub does not send the text to an audio API. Voice availability and playback with a locked screen vary by device.

Resuming may repeat a short phrase.

What the author said · editorial paraphrase

  • The statement concerns the overlap between OpenCode users and OpenAI API customers. It gives no attack mechanism, affected amount or account list.
  • Tibo also invited applications for Daybreak Blue, describing it as a cyber-permissive setup for defense. An invitation to request access does not establish universal availability.

AISubHub analysis

Our reading: an incident-related API-credit adjustment is different from a subscription usage-limit reset or a refund for cancelling a purchase. The defensive-access invitation is a separate part of the same post.

Limits and availability

The post does not give detailed refund eligibility, regional coverage, approval rules or refund and access-delivery timings. We have not checked private accounts, restored service or credited balances. No guarantee of approval, general access or a new subscription entitlement follows from it.

Sources and evidence

Tibo (@thsottiaux) · original product post

Source published: · Source checked:

AI-assisted editorial articles checked against linked primary sources. Vendor claims are attributed; inclusion is not endorsement.