OpenAI’s new reasoning technique alarms AI safety experts
OpenAI’s new Astra model will use “recurrent depth,” a technique that allows the model to operate outside of the sequential thinking that characterizes most.
By Dillip Chowdary • Sep 03, 2026 • Source: TechCrunch
What happened
OpenAI has introduced a new artificial intelligence model named Astra that utilizes a novel reasoning technique known as recurrent depth. This architectural shift departs from the sequential thinking patterns that define traditional reasoning models in the industry today. By allowing the system to process information outside of a rigid linear sequence, the technique represents a fundamental change in how neural networks compute responses. However, this departure from established sequential processing mechanisms has raised significant concerns among artificial intelligence safety experts who
OpenAI’s new Astra model will use a reasoning technique called “recurrent depth” that allows it to operate outside of the sequential thinking that characterizes most reasoning models, The Information reported on Tuesday. This technique, also called “opaque recurrence,” will likely make the model’s chain of thought more difficult to monitor — and that has AI safety experts rattled.
How it works

While Astra’s use of the technique is reportedly limited, its emergence has still raised significant concerns among AI safety experts. “I am extremely concerned by the reporting that Astra uses opaque recurrence,” wrote Redwood CEO Buck Shlegeris in a post after the news broke.
Advertisement
Tech Pulse Daily
Get tomorrow's pulse first
Join engineers who read Tech Pulse before stand-up. Free, weekday mornings.
Why it matters
“I don’t know whether Astra is much less CoT monitorable than previous models. See the full write-up from TechCrunch via the source link for quotes and complete context.
Who is affected
Read the original coverage at TechCrunch via the source link above for the complete details and primary quotes.
What to watch next
Cross-check release notes and official docs before changing production systems based on early reporting.
Developer Action Items
- ☐ Map where OpenAI sits in your stack (SDK, API key, billing, data-processing addendum).
- ☐ Hold non-urgent migrations until the integration or use-of-proceeds roadmap is public — day-one coverage is not a ship signal.
- ☐ If you are mid-contract or mid-POC, ask the vendor what changes for existing customers this quarter.
- ☐ Write the single decision this forces: stay, dual-source, or exit.
Author
Dillip Chowdary
Writes Tech Bytes coverage of AI, engineering, and the tools that actually ship. Editor of Tech Pulse Daily.
Related on Tech Bytes
Over 3 Million WordPress Sites Affected by Migration Plugin Vulnerability
Read →
Cisco Warns of Unpatched Secure Email Flaws, Patches Critical Switch Vulnerabilities
Read →
Microsoft Teams, Outlook fail to launch on ARM-based Windows PCs
Read →
Claude Code skill: no emdashes
Read →
Today's Tech Pulse briefing
Full briefing →
Advertisement