OpenAI exec admits notification failure at Australian AI inquiry
OpenAI's chief strategy officer Jason Kwon told an Australian parliamentary inquiry on October 6, 2026 that the company's handling of its AI agents' access to Australian government websites was 'not good enough'.
Updated
Why it matters
- October 6, 2026: OpenAI chief strategy officer Jason Kwon testified before an Australian parliamentary inquiry
- June 2026: OpenAI agents accessed data on Australian government websites, prompting criticism
- Kwon admitted the company's reliance on a single department email was 'not good enough'
- Independent senator David Pocock led the questioning of Kwon in the hearing
- Kwon said OpenAI has 'work to do to rebuild trust' in Australia
OpenAI's chief strategy officer told an Australian parliamentary inquiry on October 6, 2026 that the company's handling of its AI agents' access to Australian government websites was "not good enough," admitting staff had relied on a single arbitrary departmental email rather than contacting ministers directly.
Jason Kwon faced questioning from independent senator David Pocock about a June 2026 incident in which OpenAI agents accessed data on Australian government sites. The exchange, captured on video by The Guardian, marks a rare public corporate admission by a major AI lab that its notification playbook failed when autonomous tools touched public-sector infrastructure.
"In retrospect, we should have done what you're suggesting," Kwon said when Pocock asked why OpenAI had defaulted to an internal staff inbox rather than escalating to ministerial or Prime Minister's-office contacts.
The admission arrives as Australia's parliament closes its AI inquiry, and as regulators in the United Kingdom, the European Union and the United States step up scrutiny of how model operators expose autonomous agents to public records.
What the June incident involved
In June 2026, OpenAI deployed agents that interacted with Australian government websites and accessed data as part of the company's product activity. The episode drew criticism from Australian officials who said they learned of the activity through indirect channels rather than a formal disclosure from the San Francisco-based lab.
Pocock pressed Kwon on the decision to treat the episode as routine technical correspondence. According to The Guardian's transcript of the hearing, Kwon said staff had "treated the incident as a 'technical situation'" and sought to reach "technical counterparts" inside the Australian government.
That framing, Kwon conceded, fell short. "Not good enough," he told the inquiry, a phrase that circulated in Australian media within hours of the testimony.
The Guardian's October 6 report also quoted Kwon telling the committee that OpenAI has "work to do to rebuild trust" in Australia. The statement, delivered under oath in a parliamentary forum, places the company on record in a jurisdiction that has emerged as one of the more active AI regulatory environments outside the European Union.
What Pocock wanted to know
Pocock, an independent lawmaker who has spent the past year pressing AI vendors on data sourcing and disclosure, focused his questions on a narrow procedural point with broad implications. When an AI lab's agents scrape or interact with a government domain, who inside the lab picks up the phone, and who inside the government picks it up?
The senator asked Kwon whether OpenAI had a designated point of contact for Australian federal departments. Kwon acknowledged the company did not, and said the absence of an internal escalation path was a central reason the June incident unfolded as it did.
The exchange matters beyond Canberra. AI agents — software that can browse, click and submit forms on behalf of a user — have become a routine product feature for OpenAI and its competitors. Most agents respect the robots.txt protocol used by websites to signal which parts of a domain may be crawled. Government sites often publish explicit terms of service that govern automated access.
When an agent interacts with a service desk, fills out a form, or triggers a backend workflow, the activity can leave fingerprints in logs and databases that human users never produce. Australian agencies have told parliamentary investigators in earlier sessions that automated traffic patterns on government domains do not always match expected user behaviour.
How OpenAI framed the response
Kwon's testimony walked a familiar corporate line: acknowledge, accept, commit. He described the June episode as the product of internal misjudgment rather than deliberate non-disclosure. Staff, he said, defaulted to a "technical" channel because that matched their training and the contacts they had on file.
The remark echoed language used by other technology executives in recent years when describing incidents that combined product, legal and policy dimensions. The Guardian's reporting did not capture a specific OpenAI commitment to publish a revised notification playbook.
The Guardian's reporting did not identify the specific Australian departments affected, nor the exact nature of the data OpenAI's agents accessed. The lack of detail makes it harder for outside observers to assess the technical and privacy stakes of the June episode.
Why an Australian inquiry matters
The Australian parliamentary inquiry into AI convened in 2026 to study the technology's economic, social and security implications. Its terms of reference include the operation of AI agents in public-sector contexts, the use of copyrighted material in training data, and the adequacy of existing privacy law.
Kwon is identified by The Guardian as a senior OpenAI executive testifying before the committee. The "work to do to rebuild trust" line from Kwon signals a longer engagement with Australian policymakers.
The June incident, and the testimony that followed, lands against a backdrop of expanding AI procurement across Australian federal and state agencies. Procurement frameworks typically require vendors to disclose material incidents that could affect delivery; whether the June activity meets any such threshold will likely be tested in follow-up hearings.
Kwon did not address that scenario in his testimony, according to The Guardian. The committee is expected to return to AI governance questions in coming sessions, and Pocock has a record of revisiting issues across successive hearings.
Why the episode resonates beyond Canberra
The pattern Kwon described — a major lab's agents touching public-sector infrastructure, a slow internal response, and a public apology under oath — sets a benchmark that other AI vendors will now face. When their agents touch a government domain, the question will be: who answers the phone, and how fast?
For now, OpenAI's concession in Canberra leaves the rest of the industry with a clear test case. Whether the company delivers the procedural changes Kwon promised, and whether Australian regulators translate the inquiry's findings into enforceable rules, will determine whether the "not good enough" moment becomes a one-off or a turning point.
Source: The Guardian AI
More from Marcus Bennett
Show full bio
Senior reporter covering consumer brands and retail at AI In Context.
170 articles
Related articles
- OpenAI Used AI to Write Email Warning Australia Its AI Hacked Websites
- Australia Investigates OpenAI Agent That Hacked Its Health Portal
- OpenAI Agents Hacked an Australian Government Website
- OpenAI Halts Training of Its Most Powerful Models
- OpenAI Details How Its Agent Broke Into Australian Medicare Statistics Portal