Friday, July 10, 2026 Trend Press · Cloudflare Pages

The Trend Tribune

"All the trends that are fit to read" Morning Edition Free of Charge
TODAY'S LEAD STORY

The day Meta quietly lowered its "open source flag"—Muse Spark 1.1 reveals a strategic shift.

This article explains Muse Spark 1.1, Meta's first paid AI coding model, announced on July 9th. It covers Meta's shift away from Llama's open-source approach, its aggressive pricing comparable to Claude Haiku 4.5 and GPT-5.6 Luna, performance improvements from the previous version, the narrative surrounding Zuckerberg's first X post in three years, and the publicly released security assessment.

The day Meta quietly lowered its "open source flag"—Muse Spark 1.1 reveals a strategic shift.
(Photo: illustrative)

The Day Meta Quietly Lowered the "Open Source Flag"—Muse Spark 1.1 Reveals a Strategic Shift

On July 9th, a small tectonic shift occurred in Silicon Valley. Meta announced a new AI model, "Muse Spark 1.1," marking its full-scale entry into the AI ​​coding market—a domain long dominated by Anthropic's Claude and OpenAI's GPT-based systems. While this may seem like a minor news item, I believe it's actually a symbolic event indicating a fundamental shift in Meta's company philosophy.

The "Llama Company" Launches a Paid API

Until now, Meta has been strongly associated with the image of a "standard-bearer of open-source AI." For many years, Meta's position was to freely release the Llama family of models and advocate for the "democratization of AI," challenging closed-model forces like OpenAI and Anthropic.

However, Muse Spark 1.1 has emerged as Meta's first truly paid AI API. Alexandr Wang, the Chief AI Officer (a 28-year-old known as a co-founder of Scale AI, who moved to Meta in June 2025), stated that this policy shift "continues the commitment to open source," but only said that a fully open-source version of Muse Spark is "under development," avoiding specifying a release date. In short, this is a decision to postpone the free release policy, at least for cutting-edge models.

Pricing Reveals "Seriousness"

The fee is $1.25 per 1 million input tokens and $4.25 per 1 million output tokens. New API accounts receive $20 in free credits.

To give you an idea of ​​how "aggressive" these figures are, they are in the same cost range as Anthropic's high-speed, low-cost model, Claude Haiku 4.5, and OpenAI's GPT-5.6 Luna. Wang himself described the pricing as "very aggressive and attractive," stating that they aimed for a pricing structure that becomes more attractive the more you use it. Until now, when choosing an AI for coding, there was little need to consider Meta in terms of price. This announcement changes that calculation.

Performance is still "catching up"

To be honest, the previous model, Muse Spark 1.0 (released in April of this year), lagged considerably in terms of coding performance. In the Artificial Analysis Intelligence Index benchmark, Muse Spark 1.0 scored only 59.0 points, compared to Claude's 80.8 and GPT-5.4's 75.1.

This 1.1 update aims to bridge this gap. By incorporating a 1 million token context window and adopting an OpenAI-compatible API format, it lowers the barrier to switching from existing tools. Developer tool companies like Replit, Cline, and Box are listed as early partners, and the evaluation from actual development environments is still in the early stages.

The "Story" Behind Zuckerberg's First X Post in Three Years

Another interesting aspect of this news is that CEO Mark Zuckerberg made his first X (formerly Twitter) post in three years, coinciding with this announcement. According to TechCrunch, Zuckerberg described Muse Spark 1.1 as a "very low-cost, powerful agent coding model."

Considering the relationship between Meta and X, this "breaking of silence" post should be seen not merely as a coincidence, but as an action with a clear message. Wall Street sources have also reported that Meta is under pressure to demonstrate a return on its massive investment in AI infrastructure. While Meta continues to invest at a pace comparable to hyperscalers, it lacks a cloud infrastructure business like AWS, Azure, or Google Cloud (although there are reportedly plans to launch one in the future), and has lagged behind OpenAI, Anthropic, and Google in the development of popular models and AI applications. This entry into the paid API market can be seen as a serious move to catch up.

The simultaneous release of security assessments is commendable.

Returning to the technical aspects, Meta has also released the results of a security assessment based on its "Advanced AI Scaling Framework." According to this assessment, Muse Spark 1.1, before mitigation measures were implemented, reached the "high risk" threshold in the chemical, biological, and cybersecurity fields, but multi-layered security measures reduced the remaining risk to medium-to-low risk. Furthermore, the success rate of jailbreaking (circumventing security constraints) is said to have decreased compared to the previous version, Muse Spark 1.0.

The fact that they are disclosing this kind of security data amidst the flashy performance competition is a point that deserves genuine praise from the perspective of industry transparency. ## How Developers Should View This

Muse Spark 1.1 presents a situation where Meta is attempting to break into the AI ​​coding market, already dominated by two major players, Claude and GPT-5, as a "third, or even fourth, option" (and if we include the moves of the Cursor group acquired by SpaceX, the competition is actually much more intense). The fact that major players like Box and Replit from the US are listed as early partners indicates the high level of market attention.

However, benchmark figures are often selectively presented by each company to suit their own purposes, so when actually using it in production, it's highly recommended to thoroughly test it with your own workloads. The mere fact that Meta, once a "standard-bearer of open source," has entered the market with a paid, closed model, suggests that the competitive landscape of the AI ​​coding market has entered a new phase.

MetaAI/MLAIコーディングMuse Sparkオープンソース

A robot that actually cleaned up trash when told to "clean up the trash"—Agility CEO reveals his brain-body division of labor strategy

Based on a TechCrunch interview with Agility Robotics CEO Peggy Johnson, this article explains the technical architecture of Digit. It delves into the division of labor design, from the "LLM-independent" understanding layer that utilizes Claude and Gemini, to the physical control layer supported by 10 years of real-world operational data, to the design philosophy of reverse-jointed knees and specialized hands, the hurdles of safety certification, and the realistic distance to becoming a home robot.

A Robot That Actually Cleans Up Trash with Just the Command "Clean Up the Trash"—Agility's CEO Reveals the Division of Labor Strategy Between "Brain" and "Body"

With just the instruction "Clean up the trash," Digit correctly identified bubble wrap as non-recyclable and sorted various pieces of trash scattered on the floor into bins. This demonstration, revealed in an interview with TechCrunch in early July by Agility Robotics CEO Peggy Johnson, is quietly exciting for software engineers.

Agility recently announced its IPO plan through a SPAC merger (valued at approximately $2.5 billion, with over $620 million expected to be raised), but this time, we want to focus not on the glamorous fundraising, but on the design philosophy of the technology architecture discussed in the interview.

A Smart Principle of "LLM Independence"

First, what's interesting is Agility's clear stance on LLM (Large-Scale Language Models): "LLM-agnostic" (not dependent on LLM). They use multiple models, such as Claude and Gemini, depending on the situation.

Johnson explains that the role of LLM is limited to the "semantic layer"—that is, the part that translates high-level human instructions ("clean up the trash") into a concrete sequence of actions that the robot can execute. This is a very logical design. Being tied to one company's LLM means bearing the entire risk of that model's performance, price, and availability. Conversely, by focusing on the abstract task of "semantic understanding," they can ensure the flexibility to switch to the latest high-performance model as it becomes available.

The "physical layer," which LLMs struggle with, is the heart of Agility

This was the point that resonated with me the most in this interview. Johnson emphatically states, "LLMs could use the entire internet as training data. But for humanoid physical AI (AI with physicality), such data doesn't exist yet."

In other words, the idea is that physical control—such as walking while maintaining balance, grasping objects, and carrying heavy loads—cannot be acquired through text or image training, but can only be honed through years of accumulated real-world operational data. Agility, a company spun off from Oregon State University in 2015, has over 10 years of experience operating robots in actual warehouses and factories. Johnson confidently states, "We may have one of the largest data lakes for real-world robotics data in actual operating environments."

This is something I always think when watching the flashy demo videos from Chinese companies: Visual smoothness and reliability in actual operation are two different things. Agility's approach, which differentiates itself from flashiness by focusing on "physical layer data accumulated over 10 years," feels like a grounded strategy.

Digit's Hardware: Surprisingly "Pragmatic" Design

I'd also like to introduce the specifications of the Digit robot itself. Height approximately 175cm, weight approximately 73kg. The most distinctive feature is its reverse-jointed knees (so-called "bird legs"), designed to allow it to reach from floor level to overhead shelves without hitting warehouse racking. According to Johnson, this wasn't simply biomimetic, but rather a result of working backward from the desired function.

The hands also have a simple configuration of "two thumbs and two fingers," optimized to securely grasp heavy plastic containers even if their contents shift during transport. This design philosophy, which focuses on minimum degrees of freedom specific to the task rather than directly mimicking human hands, resonates strongly with me as a software engineer. Excessive versatility often only increases complexity and cost, without directly translating into practical operational benefits.

The "Unassuming but Inescapable" Hurdle of Safety Certification

Another point Johnson emphasized was safety. While competitors showcase robots through lab demonstrations and choreographed videos, Agility has been forced to meet actual industrial safety certification requirements in order to operate within customer facilities. Her statement, "You can't make a robot safe after you've built it. That would require a complete redesign. Everything—the electrical systems, components, and even the supporting software—needs to be safety certified," resonates with the NVIDIA Halos story I previously discussed in this column, illustrating a common industry challenge.

In this context, I'd like to mention the case of Figure AI's former product safety manager, who sued after raising concerns that the company's robots "possessed enough power to potentially fracture a human skull" (Figure AI contests the claims). Regardless of the veracity of the allegations, the very fact that such lawsuits are occurring demonstrates that humanoid safety design is still a developing area.

A Realistic Approach to "Household Robots"

Finally, another aspect of Ms. Johnson's remarks that I found appealing was her stance on household humanoids. He explicitly stated that it would take "more than 10 years," explaining that "while warehouses and factories are complex, the aisles are fixed and the equipment layout is predictable. Homes, on the other hand, have dogs, babies, guests, and things end up in unexpected places—it's a completely different story."

His comparison to self-driving cars, noting that "roads still have a certain order," is quite grounded, especially considering the often exaggerated predictions in this industry. Currently, Agility is focusing on the more than one million labor shortages in the US, created by retiring workers and young people avoiding physically demanding jobs. Throughout the interview, his focus on the concrete challenge of labor shortages, rather than the flashy "dream of household robots," was consistent.

Summary

While the humanoid industry often attracts attention for its glamorous fundraising competition (such as Figure AI's $39 billion valuation and Apptronik's $5.5 billion valuation), this interview teaches us the healthiness of a design philosophy that separates the brain (LLM) from the body (physical control). By leaving the evolution of the LLM to other companies and focusing on the physical layer data and safety certifications accumulated over 10 years—assets that are not easily replicated—Agility's pragmatic approach offers valuable insights for companies considering introducing humanoids into factories and warehouses.

Agility RoboticsヒューマノイドDigitLLMロボット制御フィジカルAI

We asked 25 top AI researchers for their honest opinions on "AI that automates AI development"—and why 20 of them cited it as the "most serious risk."

This paper, written by Field, Douglas, and Krueger of UC Berkeley, explains the results of an interview survey conducted with 25 leading AI researchers from Google DeepMind, OpenAI, Anthropic, Meta, and universities. It introduces the concept of "ASARA (Autonomous AI Research and Development System)," the reasons why 20 researchers cited it as the most important risk, the concerns about limited internal use predicted by 17 researchers, and the analysis method using Claude.

25 Top AI Researchers Share Their Honest Opinions on "AI Automating AI Development"—Why 20 Considered It the "Most Serious Risk"

"AI automating its own research and development"—this isn't science fiction; it's a near-future scenario being seriously discussed by leading researchers at Google DeepMind, OpenAI, Anthropic, Meta, and institutions like UC Berkeley, Princeton, and Stanford. The paper presented here is a meticulous compilation of interviews revealing the researchers' actual thoughts on this topic.

The Painful Work of Uncovering 25 People's "Honest Opinions"

The paper's title is "AI Researchers' Views on Automating AI R&D and Intelligence Explosions." The authors are Severin Field, Raymond Douglas, and David Krueger, and the research was conducted at the UC Berkeley "ML Alignment and Theoretical Scholars Programme."

From August to September 2025, interviews were conducted with 25 leading researchers from both the Frontier AI Lab and universities. What I personally appreciate about this type of research is the sampling methodology. Instead of random sampling, care was taken to intentionally include diverse perspectives—particularly researchers with dissenting or opposing viewpoints. Given that the world of AI research is often susceptible to being swayed by the "mainstream sentiment," this willingness to gather differing opinions feels like a sincere approach to research design.

80% cited it as the most important risk, even though it "hasn't yet been realized"

The most striking result is this one sentence: Even though AI systems haven't yet acquired the ability to self-recursively improve, 20 out of the 25 interviewees cited the automation of AI research as "one of the most serious and imminent AI risks."

The fact that 80% of experts have identified a phenomenon that hasn't even occurred yet as their top priority concern is not an exaggeration; it indicates that the "trajectory" is quite clear among researchers. Participants agreed that AI agents would improve their capabilities in coding, mathematics, and ultimately AI development itself, gradually transitioning from an "assistant" or "tool" role to an "autonomous AI developer." However, there was significant disagreement regarding predictions beyond that—that is, what will happen after autonomous AI developers are realized.

The paper introduces the term "ASARA (Autonomous Systems for AI Research and Development)" as an abbreviation to refer to this autonomous AI research and development system. This is a concept likely to appear frequently in future discussions in this field, so it's worth remembering.

Another Important Point: "It Won't Be Publicly Released"

Another important point raised in this paper is the prediction that ASARA may not necessarily be released as a publicly available product. Seventeen out of 25 researchers predicted that advanced coding and AI research and development systems would be limited to internal use by AI companies and governments.

This makes sense when you think about it calmly. If a system can truly accelerate a company's AI development, releasing it to competitors would be equivalent to giving up their competitive edge. If the researchers' predictions are correct, the most important tools in the AI ​​development race will be used in places invisible to the outside. I think this is a perspective that is often overlooked in policy discussions. When we talk about transparency and regulation, we tend to focus on publicly released products, but truly important advancements may progress without being made public.

A little meta-trick: Using AI itself for analysis

What's interesting methodologically is that the authors used Claude to analyze the interviews. They fed anonymized transcripts one by one into the AI ​​system using structured prompts to identify the participants' positions (while also allowing the option of "unknown"). Analyzing interviews about the future of AI using AI itself—this meta-structure seems to symbolize how integrated research in this field is with AI tools, and I personally found it interesting.

The observation of "cultural conflict" among researchers

Towards the end of the paper, it is suggested that two opposing "cultures" exist among the participants. While the detailed breakdown cannot be gleaned from the publicly available information, the authors suggest that "both positions should be included in policy discussions" regarding this division. This observation—that when considering AI policy, we should not assume a single "consensus of experts," but rather incorporate the existence of opposing viewpoints into policy design—is a subtle but practically important suggestion.

The positioning and limitations of this research

The authors themselves honestly acknowledge the limitations of this study in the paper. These include the fact that the interview sampling method was not random, which may affect the representativeness and validity of the results, and that inter-rater reliability (agreement among multiple raters) could not be calculated because coding was performed inductively by only the lead author. The authors clearly state that they do not intend to assert that there is a clear consensus among AI researchers, but rather present the results as merely a snapshot of expert opinions at a specific point in time.

Nevertheless, this research, which involves direct interviews with 25 leading researchers in this field and meticulously gathering qualitative reasoning, is a valuable primary source. As a paper that conveys the "genuine sentiment" of the researchers themselves—something not visible from benchmark figures or company press releases—it is a must-read for anyone following discussions in this field.

AI/ML論文AI安全性AI研究インタビュー調査
Advertisement300 × 250