OMG Mythos bro, Fable one shotted these amazing block buildings. Designers are cooked. 3js developers are worthless. We are dealing with AGI! It's def not hard coded by a developer so you all do their advertising for them.
Codex clears
@0xDesigner Don’t delete your old rules and systems, they will not let us peasants use it much longer, when our free Twitter advertising is done they will revoke it for their corporate donors
Day 3 of trying to win codex 10x, tile planning tool, might not use measurements exactly but imported tiles from Home Depot and helped me plan cuts. Will try the tiles tonight or tomorrow
Day 4 of trying to win codex 10x
Update:
Vibe tile laying is hard, kept shattering near the pipe. Codex taught me there is a wheel on the cutter and was able to recover. Will grout tomorrow
I have a new kind of big button that I can press for Codex. Over the next 100 days, we will select one person per day who does impressive or incredibly useful work with Codex and give them 10X usage limits for a month to see what they can do with it.
First one tomorrow.
OpenAI is reportedly considering drastic token price cuts to pull customers away from Anthropic, per WSJ. This follows rising complaints from enterprise customers about AI costs, while Anthropic has been gaining traction with Claude Code.
The message is clear: @OpenAI does not want Anthropic to own the developer market. A real AI price war may be starting.
We’re rolling out changes to make Fable 5’s safeguards for frontier LLM development visible.
Starting this week, flagged requests will visibly fall back to Opus 4.8—the same as our safeguards for cyber and bio. You will see this every time it happens. On the API, any flagged requests will return a reason for their refusal (coming to server-side fallback in the next few days).
We wanted to deploy Fable 5 to our users quickly and safely. Visible safeguards can be probed, so they have to be robust, which takes time to get right. Invisible safeguards can be targeted more narrowly, allowing us to ship quickly with very few false positives. We went with invisible safeguards for this reason—and that was the wrong tradeoff. You should have visibility into the safeguards we have in place, and why. We’re sorry for not getting the balance right.
Making the safeguards visible makes them easier to work around, so keeping them robust to jailbreaks will unfortunately mean more false positives while we improve the classifiers. We're also tuning our bio and cyber classifiers to trigger less often on harmless requests. We know this is frustrating and we’ll do our best to keep this period as short as possible.
If you think a request has been mistakenly flagged: run /feedback in Claude Code, click thumbs-down on the fallback in https://t.co/LtktniD5HY or Cowork, or file the safeguard appeal form for API requests. Your reports help us tune these classifiers and we appreciate your feedback.
https://t.co/TDAAYRGqDt