NeuralWired’s Technology section covers the developments reshaping how the world builds, deploys, and regulates digital innovation. We report daily on the stories driving global conversation in artificial intelligence, big technology companies, startups and venture funding, cybersecurity, consumer gadgets and devices, and blockchain and cryptocurrency.
Our technology coverage goes beyond product announcements. When a major AI model launches, we explain what it can actually do and where its claims are overstated. When a startup raises a large funding round, we look at whether the business behind it can sustain that valuation. When a cybersecurity breach hits the news, we explain who is affected and what comes next, not just what happened. Each article is built from original research into primary sources, including company statements, technical documentation, regulatory filings, and verified data, and is written by our editorial team rather than generated automatically.
Readers come to this section for daily updates on the technology stories that matter globally, from shifts inside major technology companies to emerging tools changing how people work, communicate, and build. Whether you are a founder, an investor, an engineer, or simply someone trying to understand where technology is heading next, NeuralWired’s Technology coverage is built to keep you informed without wasting your time on hype.
Frontier intelligence for the professionals shaping technology’s future.
Deep analysis. No hype. Actionable insight.
AI Models · Frontier Intelligence · April 2026
Meta Muse Spark: What the Benchmarks Actually Mean, Where It Falls Short, and Who Should Pay Attention
Meta’s first model from its Superintelligence Labs is genuinely impressive on vision, health reasoning, and token efficiency. It’s also not the coding model you want. Here’s the unvarnished picture.
Published: April 9, 2026Reading time: ~14 minutesCategory: AI Model AnalysisPrimary keyword: Meta Muse Spark AI model
On April 7, 2026, Meta released a model it had been building for months inside a newly formed internal unit called Meta Superintelligence Labs. The model is called Muse Spark. It runs Meta AI on the Meta AI app and meta.ai right now, with WhatsApp, Instagram, Facebook, Messenger, and the Ray-Ban Meta AI glasses to follow in the coming weeks.
The launch generated the usual wave of breathless coverage mixed with instant skepticism, which is roughly what you’d expect whenever a company with Meta’s reach announces a new frontier model. But if you’re a developer assessing whether to integrate it, a CTO deciding whether to move budget, or a researcher tracking the competitive dynamics of the frontier model race, the breathless/skeptical binary isn’t particularly useful. You need actual numbers, an honest accounting of where the model fits and where it doesn’t, and some sense of what the broader strategy actually is.
That’s what this piece is for.
The organizational context you need to understand first
Muse Spark didn’t emerge from Meta’s existing AI research pipeline. It came from a new unit, Meta Superintelligence Labs, that was stood up specifically because Mark Zuckerberg was reportedly dissatisfied with the progress of Meta’s Llama program. That’s not a minor footnote. It signals that Zuckerberg looked at where Llama was heading and concluded it wasn’t going to get Meta where it needed to be fast enough.
To lead the new lab, Meta recruited Alexandr Wang, co-founder and former CEO of Scale AI. Shortly before the launch, Meta also invested $14.3 billion in Scale AI for a 49% stake, securing not just Wang’s leadership but a massive data labeling pipeline. That kind of capital commitment tells you something about how seriously Meta is treating this bet. Analyst commentary frames Meta’s total AI spend, including infrastructure and partnerships, somewhere in the $115–135 billion range across the coming years.
There’s one more structural fact worth registering: unlike Llama, Muse Spark is closed-source. Meta says it hopes to open-source future versions, but for now the model is proprietary. That’s a deliberate pivot away from the open-source positioning that made Llama popular with researchers and developers worldwide. Whether that’s a strategic shift or just a temporary posture for the flagship line is an open question, but for anyone who built their stack on the assumption that Meta’s models would remain open, it’s a significant change.
“Small” here is relative, and Meta hasn’t disclosed exact parameter counts. But the design philosophy is deliberate: rather than scaling up a single massive model, Muse Spark uses what Meta’s team calls “thought compression” — a test-time scaling approach where multiple parallel subagents collaborate to solve hard problems. The idea is to spend more compute at inference time without making the base model grotesquely large. Alexandr Wang has framed this as a new scaling regime focused on efficient reasoning rather than brute-force parameter growth, a contrarian thesis relative to the prevailing assumption that bigger models always win.
In practice, this manifests as two modes in the consumer product: an Instant mode for quick answers and a Contemplating mode that spins up the multi-agent reasoning pipeline for harder queries. The latter is where Muse Spark’s reasoning capabilities show up most clearly, and it’s also the mode that carries higher infrastructure cost — something developers will need to account for when thinking about scale.
Natively multimodal means the model was built from the ground up to handle images, not retrofitted with a vision adapter. It can read charts, parse scientific diagrams, analyze product images, interpret health-related visuals, and process visual data in ways that are architecturally integrated rather than bolted on.
The benchmark picture, unvarnished
52
AI Intelligence Index (Artificial Analysis)
58M
Output tokens for Index (vs 157M for Claude Opus)
86.4
CharXiv visual reasoning (beats GPT-5.4 at 82.8)
42.8
HealthBench Hard (leads all models)
Artificial Analysis’s independent evaluation gives Muse Spark a score of 52 on their AI Intelligence Index — a composite measure running across reasoning, coding, multimodal understanding, and knowledge tasks. GPT-5.4 and Claude Opus 4.6 sit around 57-58; Gemini 3.1 Pro falls around 54-55. That 5-6 point gap is real but not catastrophic. The more interesting number is what it costs to get there.
Muse Spark used 58 million output tokens to complete the Intelligence Index evaluation. Claude Opus 4.6 used 157 million tokens for the same run. GPT-5.4 used 120 million. Gemini 3.1 Pro Preview came in at 57 million — essentially tied with Muse Spark. For teams running high-volume inference at scale, this efficiency gap has real cost implications. A model that gets you most of the way there at less than half the token count of its nearest competitor on raw intelligence deserves serious consideration.
Benchmark
Muse Spark
GPT-5.4
Claude Opus 4.6
Gemini 3.1 Pro
AI Intelligence Index
52
~57–58
~57–58
~54–55
Output tokens (Index run)
58M Most efficient
120M
157M
57M
MMMU-Pro (multimodal)
80.5%
~78–79%
~77–78%
82.4% Leads
CharXiv visual reasoning
86.4 Leads
82.8
~80
80.2
HealthBench Hard
42.8 Leads
High 30s–low 40s
Similar band
Slightly lower
GDPval-AA (agentic)
1427
1676 Leads
1648
1320
TerminalBench Hard (coding)
Below leaders
75.1
80.8% SWE-bench
68.5
τ²-Bench Telecom
92% Top tier
—
—
—
CritPT (hard physics)
11% Above Claude, Gemini Flash
—
3%
9%
Sources: Artificial Analysis, LushBinary, Meta AI blog. Competitor figures are approximate ranges from independent sources. All benchmarks reflect April 2026 evaluations.
Muse Spark is the second-most capable vision model we have benchmarked. Agentic performance does not stand out, it scores 1427 on GDPval-AA, behind Claude Sonnet 4.6 and GPT-5.4, but ahead of Gemini 3.1 Pro Preview at 1320.
Artificial Analysis — Independent AI benchmarking, April 7, 2026
The overall pattern is consistent across sources. The New York Times noted that Muse Spark “performed better than Meta’s previous AI models but lags rivals on coding ability.” That framing is accurate as far as it goes, though it undersells the multimodal and health performance story.
Where Muse Spark genuinely leads
Visual reasoning and multimodal understanding
This is the clearest competitive advantage. On CharXiv, a benchmark for reading charts, figures, and scientific diagrams, Muse Spark scores 86.4. GPT-5.4 comes in at 82.8, Gemini at 80.2, Claude Opus at around 80. That’s a meaningful lead, not a rounding error. For any workflow that involves parsing research papers, analyzing dashboards, extracting data from medical imaging reports, or reading technical schematics, Muse Spark has a real edge right now.
On MMMU-Pro, which tests broader multimodal understanding across academic disciplines, Muse Spark scores 80.5%, just behind Gemini 3.1 Pro’s 82.4%, ahead of GPT and Claude. Artificial Analysis labeled it the second-most capable vision model they’ve evaluated, which tracks with these numbers.
The key word is “natively.” Because multimodal processing is built into the architecture rather than added as a separate module, the model handles complex visual inputs with less prompt engineering overhead. Developers building visual Q&A systems, document parsing pipelines, or science-adjacent applications will find this integration practically useful, not just benchmark-impressive.
Health reasoning
Muse Spark leads HealthBench Hard with a score of 42.8, outperforming all major competitors on this evaluation. Meta has explicitly positioned health as a priority, noting that health questions represent one of the top reasons people turn to AI assistants. The benchmark performance backs this up.
Important caveat for builders: HealthBench Hard measures question-answering accuracy, not clinical safety. Deploying Muse Spark in contexts that inform real medical decisions requires regulatory compliance, validation against clinical standards, and guardrails that are entirely beyond what any benchmark measures. The score tells you the model is good at health Q&A. It doesn’t tell you it’s ready for a clinical workflow without substantial additional work.
Token efficiency
The token efficiency picture is one of the most practically significant findings from independent evaluations. At 58 million output tokens to complete the Intelligence Index, less than half of Claude Opus 4.6’s 157 million, and less than half of GPT-5.4’s 120 million, Muse Spark offers a materially different cost profile at scale. If you’re running millions of reasoning queries per day, this number translates directly into infrastructure budgets.
A 5-point gap from the leaders on raw intelligence is meaningful but not insurmountable, especially given Muse Spark’s strong cost-efficiency profile.
LushBinary benchmark analysis, April 2026
Domain-specific reasoning
On τ²-Bench Telecom, Muse Spark scores 92%, placing it among the highest-performing models on telecom-domain reasoning tasks. On CritPT, a hard physics benchmark where every model scores in single or low double digits, Muse Spark reaches 11% against Claude’s 3% and Gemini Flash’s 9%. These numbers are low in absolute terms because the tasks are genuinely hard, but the relative gaps suggest Muse Spark carries an advantage on scientific reasoning that may generalize to other technical domains.
Where it falls short, and why that matters
Coding and software engineering
This is the cleanest weakness in the profile. On TerminalBench Hard, a benchmark that evaluates models on real coding tasks interacting with a terminal environment, Muse Spark trails Claude Sonnet 4.6, GPT-5.4, and Gemini 3.1 Pro. Claude’s performance on SWE-bench Verified, the standard benchmark for software engineering tasks, sits at 80.8%. GPT-5.4 scores 75.1 on Terminal-Bench 2.0. Muse Spark’s specific score hasn’t been consistently reported, but the direction is clear across sources.
For teams building coding copilots, automated code review pipelines, or software engineering agents, this isn’t a minor limitation. The gap is large enough that defaulting to Claude or GPT-5.x for these use cases is the rational choice, not a matter of preference. Muse Spark’s test-time scaling advantage through multi-agent Contemplating mode may close this gap on complex reasoning-heavy coding problems, but on general software engineering tasks, it’s behind today.
Agentic and multi-step work
On GDPval-AA, a benchmark designed to evaluate models on real-world, multi-step office workflows, Muse Spark scores 1427, against GPT-5.4’s 1676 and Claude Sonnet 4.6’s 1648. It beats Gemini 3.1 Pro Preview at 1320, but the gap with the top performers is significant. For anyone building long-running agents that need to orchestrate multi-step workflows, research automation, enterprise task execution, complex data pipelines, the top two are still GPT and Claude.
The irony here is partially structural: Muse Spark’s own Contemplating mode uses multi-agent orchestration. But that architecture is optimized for single complex queries, not for sustained multi-step task execution of the kind GDPval-AA is testing.
Closed-source means lock-in
For organizations that have built their AI strategies partly around open-source models, using Llama as a foundation, running fine-tuned versions on their own infrastructure, controlling data flows and model behavior, Muse Spark’s closed-source design is a structural problem. You can’t fine-tune it, you can’t self-host it, and you’re entirely dependent on Meta’s API access decisions. Meta has said it hopes to open-source future versions, but “hopes to” is not a roadmap commitment.
This is a legitimate concern for enterprises in regulated sectors, for research institutions with data governance requirements, and for any team that has learned to be cautious about single-vendor dependencies. The developer community that embraced Llama explicitly because it was open now faces a different proposition.
Decision framework: who should actually use this
Choose Muse Spark when
Your workloads are vision-heavy or health-adjacent
Parsing charts, figures, scientific diagrams
Health Q&A at scale (with appropriate guardrails)
Document intelligence on mixed text-image content
Cost-sensitive high-volume reasoning inference
Deep integration with Meta’s social surfaces
Stick with GPT-5.x or Claude when
Coding quality and agentic execution are the priority
Open-source flexibility and fine-tuning requirements
Mission-critical agentic workflow execution
Choose Gemini when
Google Workspace integration and search grounding matter
Tight integration with Google Cloud or Workspace
Top-tier MMMU-Pro multimodal score (82.4%)
Factual grounding through Google Search
Token efficiency matching Muse Spark’s profile
The key principle for CTOs making this call: model selection should follow workload composition, not brand affinity. A team with 70% of their AI usage in visual document parsing and 30% in code generation probably wants Muse Spark for the former and Claude for the latter. Running a single model for everything because it simplifies billing isn’t a good enough reason to accept a material performance gap in either direction.
Strategic implications for different stakeholders
For ML engineers and developers
The practical question right now is whether you’re on the API waitlist. Muse Spark is in private API preview for select partners. Broader developer access isn’t confirmed on a timeline yet. That matters for planning, you can evaluate the model’s benchmark profile today, but you can’t build production systems against it unless you’re in the preview cohort.
For teams that do get access, the architecture is worth understanding before you deploy. Contemplating mode’s multi-agent design means per-query costs won’t scale linearly the way they do with a simpler inference call. Building Contemplating mode into a high-frequency pipeline without understanding the token and latency characteristics first is a straightforward way to blow past cost budgets.
For CTOs and CIOs
The most significant strategic signal from this launch isn’t Muse Spark’s specific benchmark scores. It’s the closed-source pivot. Meta is now building a proprietary frontier model alongside Llama, not instead of it. That gives Meta two distinct competitive levers, an open-source community play through Llama, and a proprietary capability play through Muse Spark. Watching how the two coexist over the next 12-18 months will tell you a lot about where Meta thinks the commercial value actually is.
For CTO-level vendor strategy decisions, the practical implication is straightforward: Muse Spark is worth a pilot on visual and health workloads, but not worth treating as a primary strategic dependency until API access is broadly available, pricing is disclosed, and there’s at least 6-12 months of production usage data from early adopters.
For VCs and investors
Meta’s $14.3 billion Scale AI investment, combined with the Superintelligence Labs structure and Alexandr Wang’s leadership, signals a serious long-term capital commitment to personal AI at social scale. The model’s consumer deployment, rolling out across WhatsApp, Instagram, Facebook, and glasses, gives Meta an inference volume that no other frontier lab can match. That volume creates a data flywheel that other closed-source model providers don’t have access to. The strategic moat here isn’t the model itself. It’s the distribution.
For investors evaluating AI infrastructure plays, this matters because Meta is essentially running a 24/7 real-world evaluation of Muse Spark at consumer scale. The feedback signal from billions of interactions on social surfaces will compound over time in ways that benchmark suites can’t capture.
For policy makers and regulators
The health positioning and the multimodal surveillance surface are the two things worth watching most carefully here. A model that leads HealthBench Hard and rolls out across WhatsApp and Meta glasses is, in practice, a health advisory system at population scale. The benchmark performance doesn’t resolve questions about misinformation risk, appropriate medical advice boundaries, or liability when the model gets something wrong in a health context.
The multimodal perception capability combined with glasses deployment creates a different kind of regulatory surface, one that involves real-time visual data processing in the physical world. These aren’t hypothetical concerns. They’re the precise scenarios that existing AI safety frameworks were designed for, and Muse Spark’s deployment timeline moves faster than most regulatory processes can currently track.
How to access Muse Spark today
The simplest answer: use the Meta AI app or meta.ai. Muse Spark powers both right now. You can access Instant mode for quick queries and Contemplating mode for harder questions that benefit from the multi-agent reasoning pipeline.
For API access, the model is in private preview. Meta has indicated that broader enterprise and developer API access will come, but no specific timeline or pricing has been announced. If your organization has an existing Meta partnership or is part of Meta’s developer ecosystem, it’s worth checking whether you qualify for preview access. For everyone else, the path is to watch Meta’s developer blog and the Meta AI technical blog for access announcements.
The model will roll out to WhatsApp, Instagram, Facebook, Messenger, and Ray-Ban Meta glasses in the coming weeks. For most consumer-facing applications, that’s where exposure will initially come from rather than direct API integration.
Frequently asked questions
Muse Spark is Meta’s first model from Meta Superintelligence Labs, announced on April 7, 2026. It’s a natively multimodal, closed-source frontier model designed to be small, fast, and capable at reasoning tasks, particularly those involving images, charts, health information, and scientific content. It powers Meta AI on the Meta AI app and meta.ai, with rollout to WhatsApp, Instagram, Facebook, Messenger, and Ray-Ban glasses coming in the following weeks.
On Artificial Analysis’s AI Intelligence Index, Muse Spark scores 52 versus GPT-5.4 and Claude Opus 4.6 at around 57-58 and Gemini 3.1 Pro at 54-55. Muse Spark leads on visual reasoning (CharXiv: 86.4 vs GPT-5.4’s 82.8) and HealthBench Hard (42.8, best in class). It trails on coding (TerminalBench Hard) and complex multi-step agentic tasks (GDPval-AA: 1427 vs GPT-5.4’s 1676). Token efficiency is a standout: 58 million output tokens on the Intelligence Index versus Claude’s 157 million.
No. Unlike Meta’s Llama models, Muse Spark is closed-source and proprietary. Meta has stated it hopes to open-source future versions, but there’s no confirmed timeline. This is a significant departure from Meta’s previous AI strategy and has direct implications for organizations that relied on Llama’s open-source nature for fine-tuning, self-hosting, or data governance reasons.
Consumer access is available now through the Meta AI app and meta.ai. API access is in private preview for select Meta partners, with broader developer access not yet announced. The model will also roll out across WhatsApp, Instagram, Facebook, Messenger, and Ray-Ban Meta glasses in the coming weeks. No pricing for API access has been disclosed.
Not as a primary coding model. Multiple independent evaluations confirm that Muse Spark trails Claude Sonnet 4.6 and GPT-5.4 on coding benchmarks including TerminalBench Hard. For software engineering copilots, automated code review, or complex software agent workflows, Claude (which leads SWE-bench Verified at 80.8%) or GPT-5.4 are the stronger current choices. Muse Spark may close this gap over time, but as of April 2026 the coding weakness is clear and consistent across sources.
Several things fundamentally distinguish them. Muse Spark is closed-source; Llama is open-source. Muse Spark is natively multimodal from the ground up; Llama’s vision capabilities have been added incrementally. Muse Spark uses a multi-agent Contemplating mode for hard reasoning tasks; standard Llama deployments don’t have this architecture. And Muse Spark comes from an entirely new organizational unit, Meta Superintelligence Labs, while Llama continues under the existing Meta AI research line.
Contemplating mode is Muse Spark’s test-time scaling approach. Rather than running a single large inference pass, it spins up multiple parallel subagents that collaborate to solve hard problems, spending more compute at inference time without making the base model larger. Meta describes this as “thought compression.” The Instant mode is a direct, fast response for simpler queries; Contemplating mode activates the multi-agent pipeline for complex reasoning tasks. Developers should account for higher per-query costs in Contemplating mode compared to Instant mode.
It performs better than competitors on HealthBench Hard (scoring 42.8), which measures health question-answering accuracy. But benchmark performance and clinical safety are different things. Deploying Muse Spark in applications that inform real medical decisions requires regulatory compliance, clinical validation, and guardrails well beyond what any benchmark measures. Policy observers have already flagged concerns about health AI at social scale without adequate safety infrastructure.
Meta has confirmed that API access is available in private preview for select partners, with broader access expected in the future. No pricing, SLAs, or specific enterprise contract terms have been disclosed. Organizations planning integrations should monitor Meta’s developer channels for access announcements and factor in the current access limitations when building 2026 AI roadmaps.
Four primary limitations matter for enterprise decision-making: (1) coding performance trails Claude and GPT-5.4, making it unsuitable as a primary development tool; (2) agentic task execution on GDPval-AA is behind the top two competitors; (3) closed-source design eliminates fine-tuning, self-hosting, and some data governance options; (4) API access is still in private preview with no disclosed pricing or SLAs. For regulated industries, the health deployment at consumer scale also raises compliance and liability questions that enterprises will need to address before adopting.
The bottom line
Muse Spark is a genuinely capable model in a specific and well-defined set of domains. The vision reasoning story is real, CharXiv at 86.4, MMMU-Pro near the top of the pack, HealthBench Hard leading the field. The token efficiency picture is also real and practically significant for anyone running reasoning tasks at scale. This isn’t hype padding. Independent benchmarkers at Artificial Analysis and LushBinary measured it, and the numbers hold up.
The coding and agentic weaknesses are equally real, and equally well-documented. If your primary use case involves writing or reviewing software, or running complex multi-step workflows through an AI agent, Muse Spark isn’t the right tool today. That may change, Meta’s investment trajectory and the “thought compression” scaling philosophy suggest a serious long-term R&D commitment, but it’s the current reality.
The closed-source pivot is probably the most strategically significant aspect of this launch, and it’s gotten less attention than the benchmark numbers. Meta is building a proprietary frontier model for the first time. Whether that ends up being a long-term strategic direction or a temporary posture for the flagship line will shape the competitive dynamics of the model market over the next 2-3 years. Watch for: broader API availability and pricing transparency (likely Q3 2026), Llama’s path forward now that Muse Spark holds the flagship position, and whether any of the health regulatory scrutiny around large-scale AI deployments on social platforms gains legislative traction in the EU or US in 2026.
For your own organizations: if you work with visual data, scientific documents, or health content at scale, put Muse Spark in your evaluation queue now and request API preview access. If your stack is primarily about code and software agents, focus your attention elsewhere for the time being. And if you’re a policymaker or regulator, the combination of health positioning and imminent deployment across billions of WhatsApp and Instagram users probably warrants a closer look than a typical model launch would require.
For ongoing frontier model coverage, benchmarks, and weekly AI intelligence, follow NeuralWired, and share this piece with someone who needs the unvarnished picture.
Disclaimer: This article is based on publicly available benchmark data, independent evaluations, and media coverage as of April 9, 2026. Benchmark scores for competitor models are approximate ranges drawn from independent third-party sources. All figures should be treated as indicative rather than definitive, as evaluation methodologies and model versions vary. NeuralWired has no commercial relationship with Meta, Anthropic, OpenAI, or Google. Nothing in this article constitutes investment, legal, or clinical advice.
Anthropic’s Claude Mythos AI Model Preview: The Locked-Down Weapon Reshaping Cybersecurity in 2026 | NeuralWired
This analysis is published by NeuralWired, frontier intelligence for the professionals who build, fund, and govern technology’s future. For related coverage, see our AI Safety and Cybersecurity verticals.
AI Security
Anthropic’s Claude Mythos AI Model Preview: The Locked-Down Weapon Reshaping Cybersecurity in 2026
The most powerful AI model Anthropic has ever built can find zero-days in every major OS. You can’t have it. Here’s why that decision might be the most consequential thing in enterprise security this year.
Published: April 8, 2026Category: AI Security / Frontier ModelsRead time: 14 minutes
Anthropic’s Claude Mythos AI model preview can find a 27-year-old vulnerability in OpenBSD, a 16-year-old exploit in FFmpeg that had survived five million automated scans without detection, and a multi-flaw chain in the Linux kernel. It can do all of this autonomously. And you cannot have access to it.
That restriction is deliberate. Anthropic announced on April 7, 2026 that Claude Mythos Preview was its most powerful model yet, outperforming every earlier Claude iteration on coding, reasoning, and cybersecurity benchmarks by margins that security practitioners are calling a generational leap. The company simultaneously announced that it would not be releasing the model publicly.
Instead, Mythos has been reserved for a closed network of 11 founding partners and over 40 additional vetted organizations under a new initiative called Project Glasswing. The logic is straightforward and the stakes are extraordinary: a model this capable in the hands of the wrong actor could automate exploitation of critical infrastructure at a scale and speed that no human security team could outrun.
This analysis breaks down what Mythos actually is, what the benchmarks reveal, how Project Glasswing is structured, who already has access, and what every CISO, CTO, and security engineer needs to do before the end of 2026 regardless of whether they ever get near the model.
What is the Anthropic Mythos AI Model Preview?
Claude Mythos Preview is Anthropic’s description of it as “the most powerful AI model we’ve ever developed.” It supersedes Claude Opus 4.6 as Anthropic’s flagship frontier model and was developed with a specific focus on advanced code reasoning, agentic workflows, and cybersecurity vulnerability discovery.
The model operates autonomously across multi-step technical tasks. It can be given a codebase, binaries, or a system specification and it will scan for weaknesses, generate exploit proof-of-concept code, and propose patches without requiring a human to guide each step. That level of agentic capability distinguishes Mythos from earlier language models that could discuss security topics but could not execute against them.
Anthropic first began using Mythos internally in large-scale vulnerability hunts before the April announcement. The results were significant enough to warrant both a formal partner program and a decision not to release the model to the public. According to the Project Glasswing announcement, Mythos has already identified thousands of high-severity vulnerabilities across every major operating system and web browser. Those findings have been reported to software maintainers in a coordinated disclosure process.
The model carries an internal codename of “Capybara” according to community tracking, and details about its architecture first became public in March 2026 through a content management system misconfiguration that exposed pre-release documentation. The official announcement in April aligned with that leaked framing.
“AI capabilities have crossed a threshold that fundamentally changes the urgency required to protect critical infrastructure from cyber threats, and there is no going back.”
Anthony Grieco, SVP and Chief Security and Trust Officer, Cisco
Benchmark Dominance: The Numbers Behind the Hype
Vendor benchmark claims deserve scrutiny, and Anthropic’s case for Mythos rests on a suite of evaluations that covers coding, cybersecurity, general reasoning, and agentic task performance. The numbers, drawn from Anthropic’s Glasswing announcement and confirmed by the Mythos system card summary at NxCode, represent double-digit gains over the previous flagship in most categories.
Benchmark
Mythos Preview
Claude Opus 4.6
Delta
CyberGym (vulnerability reproduction)
83.1%
66.6%
+16.5 pts
SWE-bench Verified
93.9%
80.8%
+13.1 pts
SWE-bench Pro
77.8%
53.4%
+24.4 pts
Terminal-Bench 2.0
82.0%
65.4%
+16.6 pts
SWE-bench Multimodal
59.0%
27.1%
+31.9 pts
GPQA Diamond
94.6%
91.3%
+3.3 pts
Humanity’s Last Exam (no tools)
56.8%
40.0%
+16.8 pts
USAMO 2026
97.6%
N/A
New benchmark
BrowseComp (4.9x fewer tokens)
86.9%
83.7%
+3.2 pts
OSWorld-Verified
79.6%
72.7%
+6.9 pts
The most striking figures are in the coding categories. The 31-point lead on SWE-bench Multimodal and the 24-point jump on SWE-bench Pro reflect Mythos’s capacity to understand and act on code at a level that earlier models could approximate but not reliably execute. SWE-bench Pro targets professional-grade software engineering tasks, which maps more directly to real security work than sanitized benchmark conditions.
The CyberGym score deserves attention specifically because it measures vulnerability reproduction rather than theoretical knowledge. A score of 83.1% means that in four out of every five cases, Mythos was able to independently reproduce a known vulnerability from minimal starting information. At Opus 4.6’s 66.6%, that figure was already impressive for an AI system. The Mythos gap represents a fundamentally different operational posture.
“The window between a vulnerability being discovered and being exploited by an adversary has collapsed. What once took months now happens in minutes with AI.”
Elia Zaitsev, Chief Technology Officer, CrowdStrike
These benchmarks were run by Anthropic on its own infrastructure, which means independent replication has not yet occurred. That is a legitimate methodological caveat. But the case studies accompanying the Glasswing announcement, including the 27-year OpenBSD bug and the 16-year FFmpeg vulnerability, provide concrete evidence beyond benchmark scores. The FFmpeg flaw in particular had survived five million automated scans by existing tools without being flagged.
Project Glasswing and the Partner Coalition
Project Glasswing is the governance structure Anthropic built around Mythos to enable defensive use while limiting offensive exposure. Named after a transparent-winged butterfly, it functions as a vetted-access program that grants qualifying organizations the ability to run Mythos against their own codebases and infrastructure.
The 11 founding partners represent a cross-section of the technology and critical infrastructure landscape:
Amazon Web ServicesAppleBroadcomCiscoCrowdStrikeGoogleJPMorganChaseLinux FoundationMicrosoftNVIDIAPalo Alto Networks
Beyond those 11, more than 40 additional organizations that build or maintain critical software have received access for scanning their own first-party and open-source code. Anthropic has also committed up to $100 million in Mythos usage credits for Glasswing participants and $4 million in direct financial support to open-source security organizations, including $2.5 million to Alpha-Omega and the OpenSSF through the Linux Foundation, and $1.5 million to the Apache Software Foundation.
Partners can access Mythos through four channels: the Claude API directly, Google Cloud Vertex AI, Amazon Bedrock, and Microsoft Azure Foundry. After the credit period ends, pricing is set at $25 per million input tokens and $125 per million output tokens. Anthropic has committed to publishing a formal progress report within 90 days, covering vulnerabilities fixed and security improvements that can be publicly disclosed.
“By giving maintainers of critical open-source codebases access to a new generation of AI models that can proactively identify and fix vulnerabilities at scale, Project Glasswing offers a credible path to changing that equation.”
Jim Zemlin, CEO, The Linux Foundation
Why Anthropic Is Keeping Mythos Locked Down
The decision not to release Mythos publicly is not primarily a product strategy. It reflects a specific risk calculation that Anthropic describes explicitly in the Glasswing documentation: a model this capable at finding and exploiting software vulnerabilities is also a model that attackers would pay to access.
The threat model is not abstract. If a nation-state or ransomware syndicate had access to Mythos-class capabilities, they could automate zero-day discovery across widely deployed infrastructure at a scale that currently requires teams of elite researchers months to replicate manually. The FFmpeg vulnerability that survived 16 years of human and automated scanning is precisely the kind of target that AI-accelerated offense would identify faster than defenders could patch.
Anthropic’s Dianna Penn, Research Product Management Lead, described the decision to CNBC as “a preliminary move to provide numerous cyber defenders with an advantage on a subject that will grow increasingly vital.” That framing matters. The restriction is presented as temporary. Anthropic has indicated it is working on model-level safeguards that would allow a future Opus-class model to incorporate Mythos-level capabilities with guardrails sufficient to permit broader deployment.
What Anthropic is not doing is pretending that access controls alone solve the problem. The company acknowledged in its system card that Mythos presents a risk profile it considers too high for general release under current safety frameworks. That admission is more candid than typical vendor safety language and suggests that the internal debate about releasing the model was significant.
There is also an arms race logic buried in Glasswing’s structure. If defenders do not have access to the best available AI tools, attackers with equivalent or near-equivalent capabilities will find vulnerabilities faster than they can be patched. The partner coalition represents Anthropic’s attempt to get the most capable defenders access to the most capable tools before that gap opens.
The Enterprise Adoption Roadmap: A Five-Step Framework
Most enterprises are not in the Glasswing partner list. That creates a strategic planning question: what should you actually do now, and what should you be prepared for when Mythos-class capabilities become more broadly available?
1
2 to 3 weeks
Threat and asset mapping
Inventory your critical software assets, open-source dependencies, and current vulnerability management stack. Mythos’s documented value is greatest where legacy tools have failed, specifically long-lived bugs in widely trusted components. Without a ranked list of high-impact targets, deploying AI scanning tools generates noise rather than intelligence.
2
2 to 4 weeks
Vendor and access strategy
Engage account teams at AWS, Google Cloud, and Microsoft to understand your eligibility path for Glasswing participation. If direct access is unavailable, identify which existing security partners are integrating Mythos-class capabilities and begin evaluating how those integrations interact with your stack. Document contractual and data residency constraints before any pilot.
3
Parallel, 2 to 4 weeks
Governance and guardrails design
Define explicit policies for what any Mythos-adjacent tool can do within your environment: read-only code analysis, no production credentials, mandatory logging, and human review gates for any exploit proof-of-concept or patch recommendation. Restrict initial access to development mirrors and security sandboxes. Get written policy approved by security leadership before any test deployment begins.
4
4 to 8 weeks
Pilot deployment on high-value targets
Run the model on one to three high-value codebases or attack surfaces. Capture metrics that matter: vulnerabilities found, severity distribution, false positive rate, and time from identification to triage and patch. Compare these numbers against your current SAST, DAST, and bug bounty outputs. If Mythos is not surfacing findings your existing tools miss, the integration cost is not justified at this stage.
5
3 to 6 months
CI/CD integration and scaled automation
Once the pilot validates incremental value, integrate scanning into pre-merge pipelines for critical services. Enforce human code review on all AI-generated patches. Track mean time to remediation, backlog reduction, and exploitable attack surface shrinkage as primary business metrics. Build a cost model against the $25 per million input and $125 per million output token pricing to ensure the economics hold at scale.
Before any of the above steps, verify these prerequisites:
Complete inventory of critical software assets and open-source dependencies
Existing vulnerability management process with ticketing and SLA structures
Data-sharing agreements that permit code analysis by external AI services
IAM policies and network segmentation capable of sandboxing AI model access
Legal and compliance review completed, especially for finance, healthcare, and energy environments
Executive alignment on AI-augmented security as a budget priority for 2026
Risk Matrix: What Could Go Wrong
The “defense-first” framing of Project Glasswing is a policy choice, not a technical guarantee. Four risk categories deserve serious planning attention.
Offensive enablement
High Impact
Attackers gaining Mythos-class capabilities through leaks, competitive model development, or access control failures. The March 2026 CMS misconfiguration that exposed pre-release Mythos documentation illustrates that access controls fail. Mitigation requires strict governance, model-level safeguards, and government coordination, not access controls alone.
Code and data leakage
Medium Impact
Proprietary code or configuration data exposed through API integrations, logs, or vendor infrastructure. Data minimization protocols, redaction pipelines, and strong vendor data agreements are essential before any production codebase is submitted to external AI services. This risk is present today with all cloud-based code analysis tools.
Over-reliance and skill atrophy
Medium Impact
Organizations reducing human security expertise in response to AI capability gains, creating blind spots when the model fails or is unavailable. Mythos should be positioned as a force multiplier for existing teams, not a replacement. Maintain independent red team capacity and human review of all AI security outputs.
Regulatory and liability uncertainty
Medium Impact
Using frontier AI in safety-critical environments may trigger new regulatory duties, particularly in finance, healthcare, and energy under emerging AI governance frameworks. Early legal engagement with NIST, ENISA-equivalent bodies, and sector-specific regulators is preferable to retroactive compliance. The regulatory landscape around Mythos-class models is still being written.
Who It Affects and What They Should Do
The Mythos announcement touches every major stakeholder in the enterprise technology stack differently. The action items are not uniform.
Stakeholder
Immediate impact
Key decision in 2026
Risk of inaction
CISO / CTO
New frontier defensive capability; AI-accelerated threats regardless of access
Whether to pursue Glasswing access and restructure vuln management budget
Increased breach risk from AI-enabled attackers
Security engineers
Access to autonomous vuln discovery that outperforms existing tooling
How to integrate safely into workflows and maintain human oversight
Tool sprawl, misuse, and missed efficiency gains
Cloud / platform teams
Need to offer Mythos-level capabilities through managed platforms
Investment in AI-augmented security product offerings
Competitive loss to providers with better AI-security integration
Open-source maintainers
New funding and AI tooling for security without requiring large security teams
Whether to apply for Glasswing access via Linux Foundation or Apache programs
Continued under-resourced security in widely deployed packages
Policymakers and regulators
Concrete evidence of dual-use danger from frontier models
How to classify, oversee, and export-control Mythos-class capabilities
Regulatory lag and uncoordinated national responses to AI-aided attacks
For open-source maintainers specifically, the Linux Foundation’s Jim Zemlin framed the Glasswing funding as a structural shift: AI-augmented security as “a trusted sidekick for every maintainer, not just those who can afford expensive security teams.” The $2.5 million directed to Alpha-Omega and OpenSSF signals that Anthropic is treating the open-source supply chain as a specific attack surface that requires dedicated attention, which aligns with the FFmpeg and Linux kernel findings. These are libraries that underpin billions of deployments.
For NeuralWired readers who are early-stage founders or investors, the Glasswing structure points toward an emerging category that might be called defensive AI as a platform: the combination of AI-powered vulnerability discovery, automated patch generation, and continuous CI/CD security scanning as a unified product layer. The companies that build on top of Mythos outputs, including automated patch pipelines, attack surface intelligence feeds, and compliance verification tools, represent a significant market opportunity that is only beginning to take shape. For further context on AI investment patterns in 2026, see our AI investment landscape report.
The Skeptics Are Not Wrong
The “defense-only” framing around Mythos should be treated as a current policy position, not a permanent technical guarantee. Several lines of criticism deserve attention before any organization makes strategic decisions based on Anthropic’s assurances.
First, the leakage risk is real and has already occurred once. The March 2026 CMS misconfiguration that exposed Mythos documentation demonstrates that even well-resourced AI companies are not immune to the operational security failures that enable competitive intelligence and capability replication. If the architecture or training methodology behind Mythos-class vulnerability discovery becomes sufficiently well understood, competitive replication by less safety-conscious actors is plausible within two to three years.
Second, the benchmarks, while impressive, are vendor-run. Anthropic’s CyberGym, SWE-bench configurations, and Terminal-Bench evaluations are conducted on internal infrastructure with internal filtering. Independent replication has not yet occurred. That is not a reason to dismiss the findings, particularly given the case study evidence of specific, patched vulnerabilities. But it is a reason to weight the absolute numbers less heavily than the directional signal they represent.
Third, the economic reality of Mythos deployment may constrain its reach more than Anthropic’s access controls do. At $25 per million input tokens and $125 per million output tokens, scanning a large enterprise codebase continuously at the level required to capture long-lived vulnerabilities before attackers do could become expensive quickly. Organizations that lack the engineering maturity to integrate AI scanning into CI/CD pipelines will not realize the value, regardless of access.
Finally, community discussion in spaces like r/Anthropic has raised alignment concerns about a model with Mythos-level offensive capability that is deliberately kept from broad safety review. The 244-page system card indicates Anthropic’s internal risk assessment is thorough. Whether it is sufficient is a question that independent researchers and regulators will need to answer over time.
None of these objections invalidate the core strategic reality: AI-accelerated exploitation is coming regardless of what Anthropic does with Mythos. The question for every security-conscious organization is not whether to engage with AI-augmented defense. It is how to do so without creating new vulnerabilities in the process. For a broader view of how AI is changing the threat landscape, see our ongoing coverage at NeuralWired Cybersecurity.
The realistic timeline runs roughly as follows. From 2026 through 2027, Mythos remains restricted to the Glasswing coalition while Anthropic develops the model-level safeguards intended to enable a broader Opus-class release. From 2027 through 2028, Mythos-level capabilities, whether from Anthropic or from competitive models, will become more widely available with better governance frameworks. Over a five to ten year horizon, AI-augmented vulnerability discovery becomes standard in large enterprises and the offense-defense balance shifts to whoever deploys these capabilities more effectively and more responsibly.
Frequently Asked Questions
What is the Anthropic Claude Mythos AI model preview?
Claude Mythos Preview is Anthropic’s newest and most powerful frontier AI model, optimized for advanced coding, reasoning, and cybersecurity tasks. It can autonomously identify and exploit complex software vulnerabilities, outperforming the earlier Claude Opus 4.6 on benchmarks including CyberGym, SWE-bench Verified, and Terminal-Bench. Anthropic describes it as the most powerful model they have ever built and is currently limiting access to vetted organizations through Project Glasswing.
Why is Anthropic restricting access to the Mythos AI model?
Anthropic is keeping Mythos in a closed preview because the model can find and exploit software vulnerabilities with an effectiveness that creates serious dual-use and cyberattack risks if widely released. As outlined in the official announcement and follow-up reporting, the company plans to develop stronger model-level safeguards before considering broader deployment. The decision reflects a specific risk calculation, not a product strategy.
How is Claude Mythos different from Claude Opus?
Compared to Claude Opus 4.6, Mythos delivers double-digit gains across software engineering and cybersecurity benchmarks. On SWE-bench Pro, the gap is more than 24 percentage points; on CyberGym, more than 16. Mythos also demonstrates stronger agentic coding capabilities, autonomously discovering long-standing vulnerabilities in widely used systems like OpenBSD, FFmpeg, and the Linux kernel without human guidance at each step.
What is Project Glasswing?
Project Glasswing is Anthropic’s cross-industry initiative to use Claude Mythos Preview to secure the world’s most critical software. It brings together 11 founding partners including AWS, Apple, Microsoft, Google, and Cisco, plus more than 40 additional institutions, to scan and harden essential software and open-source infrastructure. Anthropic has committed up to $100 million in usage credits and $4 million in direct funding to open-source security organizations as part of the program. Full details are at anthropic.com/glasswing.
Which companies have early access to Claude Mythos Preview?
The 11 founding partners are Amazon Web Services, Apple, Broadcom, Cisco, CrowdStrike, Google, JPMorganChase, the Linux Foundation, Microsoft, NVIDIA, and Palo Alto Networks. More than 40 additional organizations that build or maintain critical software infrastructure also have access for defensive security work. The full partner list has not been made public beyond these named organizations.
Can the public use the Claude Mythos AI model?
No. Anthropic does not plan to make Claude Mythos Preview generally available. Access is restricted to vetted organizations through Project Glasswing and select cloud platforms including Google Cloud Vertex AI, Amazon Bedrock, and Microsoft Azure Foundry. Even Glasswing participants are expected to use the model exclusively for defensive cybersecurity purposes.
How does Claude Mythos help with cybersecurity?
Mythos can scan codebases and binaries autonomously to detect previously unknown vulnerabilities, generate exploit proof-of-concepts, and propose patches, often identifying issues that traditional automated tools and human researchers miss. Anthropic reports it has already found thousands of high-severity issues, including long-standing bugs in every major operating system and web browser, with specific documented cases in OpenBSD, FFmpeg, and the Linux kernel.
What are the risks if a model like Mythos is weaponized?
If attackers gain access to Mythos-class capabilities, they could automate zero-day discovery and exploitation across widely deployed software at a speed and scale no human security team could match. This is the primary reason Anthropic has restricted access and is working with governments on oversight frameworks. As CrowdStrike’s CTO noted, adversaries will inevitably seek equivalent capabilities, making governance as important as the access controls themselves.
Is Claude Mythos available on Google Cloud or AWS?
Yes, but only for vetted Glasswing participants. Claude Mythos Preview is available in private preview on Google Cloud Vertex AI and is being used within AWS security operations as part of the Glasswing program. This access is invitation-only and limited to organizations focused on defensive cybersecurity use cases. General-purpose access through these platforms is not currently available.
What benchmarks does Claude Mythos achieve?
According to Anthropic’s documentation and the Mythos system card summary, key scores include: CyberGym 83.1%, SWE-bench Verified 93.9%, SWE-bench Pro 77.8%, Terminal-Bench 82.0%, GPQA Diamond 94.6%, and USAMO 2026 97.6%. These are vendor-run benchmarks and have not yet been independently replicated, but specific vulnerability case studies accompany the claims as corroborating evidence.
What the Glasswing Moment Actually Means
The pattern across what Anthropic has revealed about the Anthropic Mythos AI model preview points to a more significant structural shift than a single model announcement. The combination of autonomous vulnerability discovery, agentic code analysis, and cross-industry partner governance represents the first serious attempt to operationalize frontier AI as critical security infrastructure rather than as a productivity layer. The distinction matters enormously for how organizations plan, budget, and staff their security functions over the next three years.
Anthropic’s choice to restrict Mythos rather than release it broadly is not a setback for defenders. It is a recognition that the offense-defense balance in AI-augmented security is genuinely fragile and that deploying the most capable tools requires proportionally capable governance. Every organization that waits for the public release before engaging with this question will find itself two or three cycles behind when that release arrives.
Watch for three developments that will define the next phase. First, Anthropic’s 90-day Glasswing progress report, which will be the first empirical evidence of what Mythos deployment at scale actually produces in terms of patched vulnerabilities and prevented exposure. Second, competitive responses from OpenAI, Google DeepMind, and open-source model developers, who will face pressure to match Mythos-class capability in their own security-oriented offerings. Third, the regulatory response in the United States and European Union to the category of intentionally withheld frontier models, which will shape how future access restrictions are governed and what disclosure obligations apply.
Organizations that build the governance infrastructure, vendor relationships, and internal competency to work with AI-augmented security tools now, before the market matures and the regulatory environment solidifies, will hold a durable advantage. Those that treat Glasswing as a story to monitor rather than a signal to act on will find themselves reacting rather than leading when the next wave arrives.
For more on how frontier AI models are reshaping enterprise risk frameworks, see the NeuralWired Enterprise AI Risk series and subscribe to The Neural Loop for weekly frontier intelligence delivered to your inbox.
Disclaimer: This article is based on publicly available information from Anthropic’s official disclosures, partner statements, and third-party press coverage as of April 8, 2026. Benchmark data cited reflects vendor-reported figures that have not been independently verified. This article does not constitute financial, legal, or cybersecurity advice. NeuralWired has no commercial relationship with Anthropic or any Project Glasswing partner referenced in this piece.
Intel Joins Musk’s Terafab: What 1 TW/Year Really Means | NeuralWiredNeuralWiredBreakingAPR 07, 2026 | AI INFRASTRUCTURE
Intel × Terafab — April 7, 2026
Intel Joins Musk’s Terafab: What 1 TW/Year Actually Means for AI’s Future
NeuralWired Staff·April 7, 2026
Intel’s surprise partnership with SpaceX, Tesla, and xAI pushes the world’s most ambitious chip factory from moonshot to credible threat. Here’s the technical reality, the strategic stakes, and the honest risk assessment every CTO and investor needs.
