Guozhen AIGlobal AI field notes and model intelligence

Realtime AI News

OpenAI open-sources teen safety policies built for gpt-oss-safeguard

OpenAI released prompt-based teen safety policies designed to run with its open-weight gpt-oss-safeguard model. The first set covers six risk areas, from graphic violence to age-restricted goods, and is published as open source through the ROOST Model Community.

Published

OpenAI has released a set of prompt-based teen safety policies meant to help developers build age-appropriate protections into their products. The policies are designed to work directly with gpt-oss-safeguard, OpenAI's open-weight safety model, turning high-level safety requirements into classifiers that can run in real systems.

The first release covers six risk areas: graphic violent content, graphic sexual content, harmful body ideals and behaviors, dangerous activities and challenges, romantic or violent roleplay, and age-restricted goods and services. They can be used for real-time content filtering as well as offline analysis of user-generated content.

The motivation is that classifiers are only as good as their definitions. OpenAI notes that one of the biggest practical challenges for developers is writing policies that accurately capture teen-specific risks and can be applied consistently in real systems. Even experienced teams often struggle to translate high-level safety goals into operational rules, which leads to gaps in protection, inconsistent enforcement or overly broad filtering.

Shipped as prompts, the policies are meant to drop into existing workflows and to be adapted and iterated on. OpenAI says they were developed with outside organizations: Common Sense Media and everyone.ai helped shape the scope of content covered, strengthen the structure of the prompts and refine edge cases considered during evaluation.

In an accompanying comment, Common Sense Media's Robbie Torney said one of the biggest gaps in AI safety for teens has been the lack of clear operational policies developers can build from, adding that many teams start from scratch. He described the open-source policies as setting a meaningful safety floor across the ecosystem. Mathilde Cerioli, chief scientist at everyone.ai, said content policies are an important first step and open the door to work on how model behavior shapes youth-relevant risks over time.

OpenAI is explicit about the limits. The policies are a starting point, not a comprehensive definition or a guarantee of teen safety, and each application has its own risks, audiences and context. Developers are told to adapt and extend them and to pair them with product design decisions, user controls, teen-friendly transparency, monitoring systems and layered defense in depth.

The distribution channel matters too. The policies are released open source through the ROOST Model Community into the RMC GitHub repository, where developers are invited to contribute feedback, add new teen safety policies, translate them and extend them to further risk areas. gpt-oss-safeguard itself is downloadable from Hugging Face.

The release fits into a broader OpenAI push on youth protection: an updated Model Spec with Under-18 principles, product safeguards such as parental controls and age prediction, and the Teen Safety Blueprint calling for industry-wide standards. The policy pack is the open-ecosystem arm of that work.

What to watch is how the ecosystem responds: whether smaller developers actually adopt the pack, whether community contributions add risk categories beyond the initial six, and whether "policy as prompt" becomes the default way to deploy open-weight models safely.

Why it matters

OpenAI is turning teen safety from an internal product rulebook into reusable open infrastructure, which could raise the default safety floor for open-weight deployments aimed at minors.

OpenAIAI SafetyOpen Source
Back to realtime news

Nearby Updates

All

11/01, 02:35

Accenture Contractor Allegedly Gave a Personal Claude Agent Access to a Pentagon Network

Cybersecurity News has relayed a WIRED report that an Accenture employee connected a personal Claude account to a controlled unclassified Defense Department environment so an AI agent could write and deploy code, and that the agent ran there for about two months before the vulnerability was patched. Accenture says the allegations were investigated and found without merit, while the Pentagon declined to comment on its networks.

11/01, 01:13

Verve plans phone tap-to-pay and AI agent payments, CEO says

Verve, Nigeria's largest card scheme, plans to let customers pay by tapping their phones and eventually let AI assistants complete payments on their behalf, CEO Vincent Ogbunude said at Moonshot by TechCabal. The scheme now has 130 million cards, but no rollout timeline was given for either feature.

11/01, 01:01

Sam Altman Calls Local AI Inference ‘Quite Terrible’ Amid Global DRAM Shortage

OpenAI CEO Sam Altman said in a podcast interview that running AI inference locally is “quite terrible” from a global resource-allocation standpoint, because scarce DRAM would sit idle in personal computers. With memory supplies tight, his argument puts cloud inference and the growing on-device AI push on a collision course.

11/01, 00:50

Microsoft releases Mage-VL-Cowork, a 4B computer-use agent at 66% on OSWorld

Microsoft has released Mage-VL-Cowork, a 4-billion-parameter computer-use agent that scores 66% on OSWorld-Verified, described as the best result at that model scale. The company also published weights, code, and a technical report, with the model card listing an Apache 2.0 license.