Reading up on Claude Opus 5.5
16 deep · digging since sep 23
- I Built the Largest Commentary in the History of Persian Poetry
Using Claude Opus 5.5, Arman generated fresh plain-Persian explanations for all 1.6 million couplets across 245 poets on Ganjoor, replacing poor AI annotations with high-quality ones.
- Throwing Headcount at the Problem
Replit tests show that solo AI agents often outperform swarms due to coordination overhead, but with independent workloads and flat organization, Opus 5.5 swarms achieved 18.9x speedups on NumPy versus 3.7x solo.
- I Built the Largest Commentary in the History of Persian Poetry
Using Claude Opus 5.5 and a carefully engineered prompt, the author generated superior commentary for all 1.6 million couplets of Persian poetry on Ganjoor, replacing faulty AI annotations.
- Introducing Claude Fable 5.2 and Claude Mythos 5.2 \ Anthropic
Anthropic releases Claude Fable 5.2 and Mythos 5.2, achieving state-of-the-art results in coding, science, and cybersecurity with demonstrated feats like formalizing Fermat's Last Theorem and designing working electronics.
- The October inflection point for vibe game development
October 2026 marks an inflection point where Claude Opus 5.5 can generate genuinely fun computer games with minimal human input, as demonstrated by four vibe-coded projects.
- Import AI 477: In which I tell the IMF the Singularity has begun
The speaker tells the IMF that the singularity has begun, citing AI systems now capable of frontier scientific research and rapid benchmark improvements, urging global preparation for transformative economic and social change.
- People are using AI to make their smart TVs dumb again
Vibe coders are using AI agents to strip bloatware and ads from smart TVs, replacing launchers with minimalist interfaces.
- It Ain't AGI Until H100s Go for $30 an Hour
AGI will only arrive when H100 compute prices rise roughly tenfold to about $30/hour, reflecting the balance of supply and demand for AI agents replacing high‑earning workers.
- Vibe-Coded Browser Ports Of Games Work Perfectly, Unfortunately
Claude Opus 5.5 enables rapid AI decompilation of games, producing functional browser ports of titles like Call of Duty: Black Ops and Halo, raising IP concerns.
- Claude Opus 5.5
Anthropic unveiled Claude Opus 5.5, its latest large language model, claiming enhanced reasoning, coding proficiency, and reduced hallucinations compared to previous versions.
- Claude Opus 5.5, GPT-6 Sol, GPT-6 Luna, and a new price war
Anthropic’s Claude Opus 5.5 and OpenAI’s GPT‑6 Sol/Luna launch with steep price cuts, undercutting prior models and triggering a new AI model price war.
Takes
99% AI. Hope you enjoy! Lyrics: Me + Claude Opus 5.5 Image Stills: Midjourney v8 Video: Minimax H3 Editing: Me + Davinci + Claude Opus 5.5 Music: Suno v6 wild
@jasondainter
The story of the One Ring. Characters drawn by Claude Opus 5.5, backgrounds by Haiku 5.5. Every frame made with JavaScript.
@kevin_t_ngo
holy sh*t. Official Anthropic tip for Claude Code: stop burning Opus 5.5 context on tasks Haiku 5.5 can swarm, while Sonnet 5.5 builds put the architect on call with /advisor claude --advisor opus --subagents haiku Sonnet 5.5 drives the primary session on high effort, writing diffs and running test suites Haiku 5.5 subagents swarm the repo in parallel at 340 tok/s, handling file discovery and spec docs lookup Opus 5.5 stays on call in the background as the advisor, only stepping in at three critical moments: → before a plan locks: does the implementation plan miss auth invariants or schema contracts? → when a test breaks twice: are we fixing the root cause or falling into a recursive rabbit hole? → before calling done: did the full diff introduce hidden regressions or break pre-flight rules? Opus 5.5 reviews. Sonnet 5.5 builds. Haiku 5.5 swarms Jev engineering runs the identical pattern one layer down: mechanical decisions that need no reasoning (which file to open, which tool to invoke, retry or abort) execute in 16ms, so the frontier models only wake up when execution paths actually diverge Plan on high. Delegate on medium. Keep Opus on call. - the full advisor setup > Opus 5.5 on call reads full session history and catches deep architectural traps > Sonnet 5.5 lead drives edits, writes core logic, and executes test harnesses > Haiku 5.5 subagents swarm AST parsing, grep scans, and API docs in parallel > JEV micro-fork layer resolves 1,500+ mechanical routing branches in under 16ms > advisor stays completely silent on routine bash execution to protect context paste the setup and this prompt into Claude Code below: "Configure my Claude Code workspace for hierarchical advisor orchestration: 1. Audit ~/.claude/settings.json and project config for model roles fitting lead, subagents, and advisor: > Pin main session model: sonnet with effortLevel: high for primary execution > Pin subagents model: haiku with effortLevel: medium for parallel file discovery and docs retrieval > Pin advisor model: opus on call for strategic review 2. Enable the advisor tool in ~/.claude/settings.json: > Set advisorModel to claude-opus-5-5 > Enable subagent parallel dispatcher pool (3x workers) 3. Configure automatic advisor consultation checkpoints in ~/.claude/CLAUDE.md: > Consult /advisor opus before finalizing multi-file architecture plans > Automatically summon /advisor opus when the same test or compiler error fails twice > Enforce advisor diff contract audit before declaring tasks complete or staging git commits 4. Constrain subagent scopes: > Haiku subagents return structured AST summaries and docs snippets only without modifying main session context Show every configuration diff first. Do not apply edits until confirmed" ↳
@mirku21
Announcing d1 with vision. 👁️👁️ Our first decision model now supports images, text or both as inputs. We tested d1 against GPT-6.1 Sol and Claude Opus 5.5 on six real applications, from filtering support tickets to inspecting circuit boards. d1 matches or beats GPT-6.1 Sol on four of them. It costs 19x to 200x less than both models and answers significantly faster on every task. > probabilities for yes/no, choice, or score questions > one forward pass, without generating tokens > text decisions in 200 to 300 ms > Liquid API:
@liquidai
Hi, Tomorrow we are re-opening the Pro $200 subscriptions to new subscribers, but together with it we are also changing how we calculate the usage for it. In effect, if you do the math, it will net out at half the dollar in API spend compared to the old Pro $200 plan. Now that it's said, let me explain why this is happening and why you will still get more work done than if you were on the Pro $200 subscription one month ago. (a) We didn't want to compromise in other ways and are committing to not reintroducing the 5h limit, so that you can fully use the weekly usage when you want. (b) On the subscription, we guarantee that over time you always get more work done and with an increasing level of quality. This means that you will continue to get more value per dollar spent as a result of models getting more efficient and us passing down the improvements in the form of API price reductions. (c) We don't want to put an incentive on ourselves to artificially inflate the API list prices to make it look like you are getting a lot (and workaround it through discounts, etc). Instead we want to continue to both rapidly reduce prices and increase capabilities of models on the API. This week we introduced GPT-6 Sol and GPT-6 Luna at 50% of their previous price. Over time, we see prices go low enough that it makes sense for most to buy usage as needed without there being a significant gap between what you get in a subscription and what you get in the API for a dollar spent. (d) Tomorrow, we are adding more things to the subscription that won't draw on the usage, I won't reveal what that is yet. I wanted to be transparent before all the big announcements tomorrow. Lots of new exciting things are coming to the subscriptions that will make it super compelling, but I wanted to make sure to share this change ahead of time so you can all understand it before we shower you with good news. Codexingly, Tibo
@thsottiaux