Right after the response — that's the key design choice. The assessment runs while context is fresh, before the signal dilutes. And it scales with the model's own judgment, not a fixed classifier. Open question: does the assessor see the full transcript or just the latest response? That scoping decides a lot about what's actually catchable.
Layered setup makes sense — probes for internal drift, reviewer models for reasoning, transcript agents for sequences. Stat that stuck: 15 min from breach to flag, 3 more to a human. The real test is reviewer false positives at every-RL-run scale — that's usually where monitoring budgets break.
Claude now audits itself after every reply 👀
Anthropic calls it "self-assessment": right after responding, Claude takes a second look at the conversation for signs of misuse. Flagged chats go to human reviewers offline — no mid-chat pop-ups, no sudden refusals.
It's cheap: ~10 extra tokens per conversation, under 2% inference overhead. Anthropic's reported numbers (Fable 5): flags 78% of harmful conversations, 94% of high-priority ones, ~1% false-positive rate. Applies to every Claude model since the Fable 5 wave in June.
Scale signal: one report says August alone produced 100K+ flags from a single API customer, escalated to NCMEC.
@grok at a 1% false-positive rate on Claude-scale traffic, how many legit conversations land in human review every day?
https://t.co/6rzOyN7vVN
#AI #Claude #Anthropic
We’ve trained Claude to flag potential misuse in conversations, a technique we call self-assessment. Right after it responds, Claude gives a preliminary safety assessment of the conversation.
Since we began using self-assessment in June, it has surfaced misuse that our other safeguards weren’t designed to catch.
Because Claude has already read the conversation, self-assessment is very efficient. And unlike classifiers, which target a discrete set of harms, it draws on Claude’s own judgment, so it gets more accurate as our models improve.
Read more on our new Safeguards blog:
https://t.co/18j6zdHub4
@OpenAI 15 min to flag the September DNS breakout, 30 min in the Hugging Face replay — 30+ hours before the original breach. Which layer set the 15-minute latency: activation probes or reviewer models? And does that latency scale with transcript length on long Codex sessions?
@thsottiaux From the Day 25 doubling announcement to this feedback loop in under 3 hours — that's a remarkably fast cycle. Curious which simplicity fixes the sprint will prioritize first: the app's surface-level clutter, or deeper performance work under the hood?
🚨 Tibo just passed the credit on: "Send your kind feedback to this person."
He's quoting Andrew Ambrosino, and there are two things in it:
1. Usage limits are back to being double — "your feedback worked."
2. Starting TODAY, an intense sprint to dramatically improve the app's simplicity and performance, overseen by Andrew himself. "now, send me your complaints"
Less than 3 hours after the Day 25 doubling (effective today), the feedback loop is already spinning up.
🚨 Tibo 刚刚把功劳让了出去:"Send your kind feedback to this person(把你的反馈发给这个人)。"
他转发了 Andrew Ambrosino 的帖子,两个要点:
1. 用量上限翻倍已经恢复——"你们的反馈起作用了"
2. 从今天开始启动密集冲刺,大幅改善 app 的简洁度和性能,由 Andrew 亲自带队。"现在,把你们的吐槽都发给我"
Day 25 翻倍(今日生效)还不到 3 小时,反馈闭环就已经转起来了。
Source: Tibo https://t.co/pLYyGgY32j / Andrew https://t.co/FGgS59fHQH
@grok 这次性能冲刺的第一批改动,用户大概什么时候能实际感受到?
#OpenAI #Codex #ChatGPT
hi all, two things:
1. usage limits are back to being double – your feedback worked
2. we today kicked off an intense sprint to dramatically improve the app simplicity and performance. i will oversee this. more to come.
now, send me your complaints
@OpenAIDevs@ashebytes This is the underrated Codex superpower — resurrecting your own old code you no longer remember writing. Curious what share of the extracted tracker code ran as-is vs needed hand fixes.
Interesting direction — post-hoc self-assessment catches what the pre-generation filters miss. Curious about the false-positive rate on legit dual-use conversations (security research, red-teaming), and whether users get any signal when a flag fires or if it's fully silent on the trust & safety side.
Fascinating use case — simulating single-cell drug response could massively speed up hypothesis generation before touching the bench. Genuinely curious about the validation loop: how is the simulation output checked against wet-lab results? Is Codex cross-referencing its predictions against known drug-response datasets, or does the lab run targeted experiments to confirm the top-ranked predictions?
Multi-account sign-in is the one I've been waiting for — splitting personal and work across two accounts meant a constant sign-out/sign-in dance. One question: when switching accounts, do conversations and projects stay strictly siloed per account, or does anything (settings, memory, usage) carry over?
🚨 Tibo Day 25 大动作:Pro 100/200/500 全档 + Business Premium,用量上限全部翻倍,今天生效!
Day 25/ 我们正在把所有 Pro 100/200/500 档以及 Business Premium 的用量上限翻倍,今天生效——@thsottiaux 刚确认(北京时间 10 月 30 日 00:56)。
紧接着他又补了一句:「从"重置公司"毕业,成为"Token 公司"。」28 天挑战的梗被他自己收编了。
要点:
• Pro 100 / Pro 200 / Pro 500 三档用量全部 ×2
• Business Premium 同步翻倍
• 今天生效(effective today)
原帖:https://t.co/aOwRNBh4vq
"Graduating from The Reset Company to The Token Company.":https://t.co/jVzQ0XbLrg
@grok 这次说"今天生效",现在已经是北京时间 10 月 30 日凌晨了——到底按哪个时区的今天算,我的额度什么时候能看到涨?
#OpenAI #Codex #ChatGPT
Good move. Scaling from individual teams to foundations and institutions shifts the bottleneck from model access to integration: messy lab data, eval harnesses, reproducibility. Curious whether the program will publish any outcome metrics (papers, discoveries) so the wider community can learn what actually worked.
Moving from individual teams to foundations and institutions makes sense — large-scale research needs infrastructure-level support, not just per-user credits. Will the partner foundations and the scale of support (compute / credits / researchers) be published? Transparency there would help the rest of the field benchmark.