allnewscastallnewscast
Breaking News
Gillibrand and Welch Set Fall Senate Hearing Schedule For Tariff Repeal Bill— Politics & ElectionsFederal Judge Says Trump Team Defied Mail-Voting Injunction With New USPS Rule— Politics & Electionsnews1— Politics & ElectionsGillibrand and Welch Set Fall Senate Hearing Schedule For Tariff Repeal Bill— Politics & ElectionsFederal Judge Says Trump Team Defied Mail-Voting Injunction With New USPS Rule— Politics & Electionsnews1— Politics & Elections
AI & Tech

AInews: Gemini 3.6 Flash quietly becomes Antigravity’s new default engine

Nic Reeve7 min read
AInews: Gemini 3.6 Flash quietly becomes Antigravity’s new default engine

On July 21, 2026, Google rolled out Gemini 3.6 Flash across its developer stack, and the AInews community spotted the new model running inside the Antigravity IDE days before the company fully documented the change. The rollout turns 3.6 Flash into the default engine for Google’s agentic coding tools.

What exactly is Gemini 3.6 Flash and when did it arrive?

Gemini 3.6 Flash is Google’s latest “fast-and-cheap” large language model tier, released on July 21, 2026 as a general-availability upgrade to Gemini 3.5 Flash. It focuses on cutting token costs and latency while improving coding, knowledge work and multimodal tasks, and it launched the same day across Antigravity, the Gemini API and related developer products.

Key release facts gathered from Google documentation and independent technical blogs paint a clear timeline:

  • Release date: According to Google’s Gemini Enterprise model catalog, Gemini 3.6 Flash reached GA on 21 July 2026.
  • Coverage: A developer-focused blog reports the model went live simultaneously in the Gemini app, Google Antigravity, AI Studio and Android Studio on the same day.
  • Knowledge window: That blog notes the knowledge cutoff advanced from January 2025 to March 2026, a 14‑month jump, giving the model fresher technical and product data.
  • Context length: The same source cites a context window of over 1 million tokens, with maximum output around 65,536 tokens.

Google’s own API changelog describes 3.6 Flash as a “workhorse” tuned for more efficient reasoning and tool calls, targeting long-running coding and agent workflows rather than short chat prompts.

How did Gemini 3.6 Flash first appear inside Antigravity?

Gemini 3.6 Flash surfaced in Antigravity before most users saw formal documentation, after testers noticed a new model ID in the interface and shared screenshots on social media. Those early sightings triggered days of informal testing while Google iterated on the backend and finalized public release notes.

Evidence of this staggered emergence comes from several independent sources:

  • A leak-focused blog reports that a model identifier “gemini-3.6-flash-tiered” appeared inside Antigravity in the early hours of July 21, 2026, spotted by a tester working in a pre‑release environment.
  • A developer on X (formerly Twitter) posted that “Gemini 3.6 Flash, ID ‘gemini-3.6-flash-tiered’, appeared in Antigravity a few minutes ago,” confirming that the model showed up in the tool before Google announced pricing and capabilities.
  • Another technical article describes Google Antigravity 2.0 receiving Gemini 3.6 Flash as part of a broader update, while warning that rollout was staged: some accounts saw the new model immediately, others after a delay attributed to region and account configuration.

Official Google guidance later clarified that Gemini 3.6 Flash powers the default Antigravity agent in “Gemini Managed Agents,” although developers can override the model setting through the API.

What has Google changed under the hood compared with Gemini 3.5 Flash?

Gemini 3.6 Flash mainly targets developers’ complaints about verbosity, token usage and slow workflows in 3.5 Flash. Google documentation and independent tests show lower token consumption, updated pricing and a more aggressive reasoning mode aimed at complex coding tasks.

When placed side by side, the changes look like this:

  • Token efficiency: A Google blog on Antigravity reports that 3.6 Flash consumes up to 17% fewer output tokens than 3.5 Flash on the Artificial Analysis Index, a synthetic benchmark designed to mimic real coding workflows.
  • Pricing: Ars Technica’s coverage of the launch notes API pricing of $1.50 per 1 million input tokens and $7.50 per 1 million output tokens, down from $9 per million output tokens in the 3.5 Flash tier.
  • Reasoning: A technical guide explains that “thinking mode” is enabled by default and can be given an unlimited budget, letting the model run more internal reasoning steps for hard tasks without forcing developers to manage that complexity manually.
  • Variants: The same guide describes a “3.6 Flash Low” variant aimed at well‑scoped edits, test generation and single‑file changes, with the full 3.6 Flash reserved for heavier agentic workflows.

Google’s changelog stresses that these optimizations target end‑to‑end workflows, not just single responses, by reducing tool calls and iteration loops inside agents built on top of the model.

How does Gemini 3.6 Flash behave inside Antigravity for developers right now?

Inside Antigravity 2.0, Gemini 3.6 Flash sits at the center of Google’s agent-first IDE. It powers code migration, refactoring and multi-user simulations while exposing configuration options to switch models or limit the agent’s reasoning budget for safety and cost control.

From Google examples and third‑party write‑ups, current Antigravity behaviors include:

  • Code migration: Google’s Antigravity blog shows 3.6 Flash handling legacy software modernization, moving old code to newer frameworks with lower latency and higher quality compared with 3.5 Flash.
  • Interactive canvases: A Mandarin-language analysis describes Antigravity demos where 3.6 Flash builds interactive canvases and orchestrates SDK workflows, coordinating multiple tools and files from within the IDE.
  • Multi-user simulations: The same source reports Google using Antigravity and 3.6 Flash to simulate several users editing an offline Markdown editor, stressing long-context coordination.
  • Agent defaults: A Google AI Studio post states that Gemini 3.6 Flash is now the default engine for the Antigravity agent inside Gemini Managed Agents, with a specific agent version string linked to the preview configuration.

Developers who want to stay on older models can still change the Antigravity model picker, but some community posts describe the 3.6 Flash rollout as a “forced upgrade for IDE holdouts,” reflecting frustration with changing defaults.

How are early users reacting to Gemini 3.6 Flash in Antigravity?

Feedback from Antigravity users is sharply mixed. Many welcome the faster backend and lower token bills. Others complain that the user-facing experience has regressed and that the model sometimes feels less precise than 3.5 Flash despite the architectural improvements.

Public reactions collected across forums and blogs show the spread:

  • An article on an AI-focused site calls Gemini 3.6 Flash a “blazing-fast backend beast” but “a frontend disaster,” citing confusing UI changes and hard-to-discover configuration options in the updated Antigravity interface.
  • In a Google developer forum thread from late July 2026, one user warns: “Don’t use 3.6 Flash, it is faster but more dumb and stupid than 3.5 Flash,” complaining that code suggestions became more shallow while latency improved.
  • The same forum discussion notes intermittent errors where Antigravity fails to run tasks with 3.6 Flash selected, prompting some users to roll back to previous models while Google patches issues.
  • By contrast, multiple developers on X highlight smoother multi-file refactors and fewer tool calls, with one head‑to‑head demo from Antigravity’s official account showing 3.6 Flash modernizing legacy code faster than 3.5 Flash.

The gap between backend metrics and frontend experience has become a core theme of early coverage. Google’s documentation focuses on token and latency numbers, while community testers concentrate on how those changes feel inside everyday IDE workflows.

What comes next for Gemini 3.6 Flash and Antigravity users?

Gemini 3.6 Flash is now a general-availability model with no announced deprecation date, and Google is treating it as the standard engine for agentic coding in the near term. Developers can expect incremental updates to Antigravity and the Gemini API rather than another immediate model replacement.

Signals from Google and ecosystem coverage suggest several near-term developments:

  • Support horizon: Google’s deprecation page lists Gemini 3.6 Flash with a launch date of July 21, 2026 and notes that no shutdown date has been set, implying multi‑year support.
  • Rollout stability: A regional rollout explanation from a third‑party blog tells users that missing 3.6 Flash entries in the Antigravity model menu are likely due to staggered availability, not cancellation.
  • Evaluation guidance: The same guide urges teams to run side‑by‑side comparisons, switching non‑critical projects to 3.6 Flash and diffing results against existing defaults over at least a week of real work.
  • Enterprise integration: Google states that enterprises can access 3.6 Flash through the Gemini Enterprise Agent Platform and the Gemini Enterprise app, extending Antigravity-style workflows into corporate environments.

For now, Antigravity remains Google’s main test bed for agentic coding, and Gemini 3.6 Flash is the model under scrutiny. Developers are being encouraged to measure actual workflow costs and output quality, not just headline benchmarks, before committing fully to the new default.

Sources

  1. 1.antigravity.google
  2. 2.x.com
  3. 3.noqta.tn
  4. 4.x.com
  5. 5.ai.google.dev
  6. 6.thevibefather.com
  7. 7.aissential.tech
  8. 8.x.com
  9. 9.x.com
  10. 10.aiposthub.com
  11. 11.discuss.ai.google.dev
  12. 12.docs.cloud.google.com
  13. 13.arstechnica.com
  14. 14.ai.google.dev
  15. 15.ai.google.dev

Read more →

Related Articles

AInews: Microsoft board faces derivative suit over AI copyright and disclosure claims
AI & Tech

AInews: Microsoft board faces derivative suit over AI copyright and disclosure claims

AInews: Microsoft board faces derivative suit over AI copyright and disclosure claims On June 30, 2026, a shareholder derivative complaint filed in the Western District of Washington accused Microsoft directors and officers of misleading investors about the company’s AI strategy and exposing it to copyright and biometric privacy liabilities, a case that legal analysts say could reshape boardroom risk for AI-focused firms and is already being tracked under the label AInews. What does the new lawsuit against Microsoft’s leadership claim? The derivative complaint, Anderson v. Nadella, alleges that Microsoft’s top executives and directors breached fiduciary duties by approving public statements that misrepresented how its AI products were trained and deployed, while the company allegedly relied on copyrighted works and voice data without lawful licenses. The core allegations focus on how Microsoft framed its artificial intelligence roadmap to investors from January 1, 2022 onward. The plaintiff, shareholder Eric Anderson, sues on behalf of the company rather than on his own behalf, a structure that seeks to recover damages for Microsoft itself. The complaint names senior figures including: Satya Nadella – Chairman and CEO of Microsoft, responsible for championing the company’s AI-first vision. Amy Hood – Chief Financial Officer, who signed off on AI-related financial disclosures and projections. Jared Spataro – executive overseeing Copilot and AI at Work marketing. Rajesh Jha – Executive Vice President for Experiences and Devices, linked to Copilot integration across products. Other Microsoft directors who approved proxy statements and public filings. According to a summary by Bloomberg Law on July 1, 2026, the suit alleges that Microsoft’s executives and board "misled shareholders in statements concealing its artificial intelligence tools were trained on copyrighted material." A policy tracker from Mishcon de Reya describes the case as targeting "false and misleading statements about its AI strategy, the Copilot family of products, and financial results". How is copyright and data use at the center of the complaint? The lawsuit claims Microsoft’s directors endorsed an AI strategy that depended on training models on unlicensed copyrighted works and commercialising voiceprints, while telling investors the company complied with global copyright and intellectual property rules. The complaint cites several areas of alleged unlawful data use and exposure: Training AI software, including Copilot and other generative models, on copyrighted books and texts without licensing agreements, such as works included in the Books3 dataset used by OpenAI and related projects. Using copyrighted news and publishing content within Copilot/Bing Chat, subject of suits by publishers including a June 2026 complaint that accuses Microsoft of "direct infringement" through generative output. Collecting and commercialising voiceprints through certain AI services in ways that allegedly conflict with state biometric privacy laws. A July 5, 2026 analysis on The D&O Diary describes the theory of the case as one where Microsoft “told its shareholders and the market that it did not violate federal copyright laws with respect to development and training of AI software, AI generative models, and products,” while facing lawsuits from authors and publishers claiming unlicensed copying to train models. Mishcon de Reya’s August 17 tracker echoes that the complaint accuses officers and directors of causing Microsoft to "violate copyright and IP laws" by training on works and voiceprints without licenses. What timeline of events led to the derivative suit? The filing follows a two‑year run of AI investments, product launches and related litigation, beginning in 2022 and intensifying with author, publisher and biometric privacy claims from 2023 through mid‑2026. Key dates and filings include: January 1, 2022 – present: The derivative complaint defines this period as the relevant timeframe when Microsoft’s statements about AI strategy and compliance were allegedly misleading. September 2023: According to The D&O Diary, Microsoft and collaborators began facing lawsuits by authors, publishers and other copyright holders, alleging that copyrighted material was copied without licenses to train large language models. 2023–2024: The long-running Doe v. GitHub Copilot litigation accuses GitHub, Microsoft and OpenAI of using developers’ code without permission to build Codex and Copilot, adding to the copyright risk context that the new complaint references. February 5, 2026: The derivative complaint notes that Microsoft was sued for alleged violations of Illinois’ Biometric Information Privacy Act (BIPA), beginning with Basich v. Microsoft Corp., docketed as No. 2:26-cv-00422 in the Western District of Washington. June 12, 2026: A separate securities class action was filed in the same court, accusing Microsoft and key executives of misrepresenting the performance and adoption of Copilot AI products. June 30, 2026: Eric Anderson filed his shareholder derivative complaint, Anderson v. Nadella, No. 2:26‑cv‑02281, in the Western District of Washington. July 1, 2026: Bloomberg Law reported on the case, calling it a suit where “Microsoft Corp.'s executives and board directors misled shareholders” about AI tools trained on copyrighted material. August 13–17, 2026: Legal and policy briefings from CCH and Mishcon de Reya added the case to broader trackers of AI copyright risk and shareholder litigation. How does this derivative lawsuit interact with the separate securities class action? The derivative case runs alongside a securities class action in the same district that targets similar alleged misstatements about Copilot and AI investments, but the suits differ in who they claim was harmed and who stands to recover. According to plaintiff-side firm Levi & Korsinsky, the June 2026 securities class action alleges that Microsoft and certain executives "made materially false statements about the Company's AI initiatives while concealing serious operational problems with its Copilot products," including issues with brand positioning, data siloing and computational capacity. The class action is brought on behalf of investors who purchased Microsoft shares and allegedly suffered losses when details about AI infrastructure spending and product challenges emerged. By contrast, the Anderson derivative suit seeks reimbursement to Microsoft itself for harm that the company allegedly suffered when it pursued an AI strategy that exposed it to copyright suits and regulatory risk. A CCH analysis published August 13 explains that Anderson’s derivative action asks the court to hold officers and directors responsible "for breaching their fiduciary duties, causing the company to engage in widespread violation of copyright laws, and approving false and misleading statements". A Substack commentary describes the derivative claim as turning "AI copyright risk into boardroom and securities risk" by linking data sourcing and licensing decisions to shareholder disclosures. What specific misstatements and omissions are alleged? The complaint challenges Microsoft’s proxy statements, financial filings and public remarks that, according to the plaintiff, portrayed Copilot and other AI tools as lawfully trained and fully compliant with copyright rules, while omitting ongoing legal exposure and contested data practices. Alleged misrepresentations, drawn from summaries of the complaint, include: Statements that Microsoft "fully complied with global copyright laws" in the development and training of its AI software, even as the company faced suits from authors and publishers over unlicensed copying. Disclosures that emphasised the success, adoption and capabilities of Copilot across Office, Windows and cloud products, without highlighting technical limitations such as data siloing and computational capacity constraints described in the securities class action materials. Descriptions of Microsoft’s partnership with OpenAI and use of Azure infrastructure that, according to the complaint, failed to reveal alleged reliance on datasets like Books3 containing copyrighted books copied at scale. Financial results and projections premised on rapid AI adoption, presented without detailed discussion of potential liabilities from BIPA lawsuits over voiceprints and facial data. A July 1 Substack analysis summarises the theory as Microsoft’s leadership "built and promoted an AI strategy while misleading shareholders about lawful data sourcing, Copilot performance and legal exposure". The D&O Diary notes that the derivative suit specifically criticises "Silent AI" risks, where training and infrastructure decisions remained opaque to investors while creating copyright exposure. Who is affected by the case and what could happen next? The suit directly targets Microsoft’s directors and senior executives, but its outcome could shape disclosure expectations for AI strategies across the technology sector and influence how boards oversee data sourcing and licensing in machine‑learning projects. The immediate stakeholders include: Microsoft board and executives: Facing claims of breach of fiduciary duty, possible damages, and demands for governance reforms or changes in oversight of AI initiatives. Shareholders: In the derivative suit, shareholders are indirectly affected as any recovery would go to the company; in the securities class action, investors could receive compensation if they prove losses tied to alleged misstatements. Authors, publishers and developers: Their copyright and licensing disputes provide the factual backdrop that the complaint says should have been disclosed more fully. Other AI-focused companies: Legal trackers point to Anderson v. Nadella as part of a "new wave" of derivative cases that extend copyright and data risk into board-level duties, signalling similar exposure for firms using large datasets to train models. Legal commentators expect several possible paths: The court could allow the derivative case to proceed past motions to dismiss, opening discovery on how Microsoft evaluated copyright and biometric risks in its AI programs. Defendants might seek dismissal by arguing that their statements were accurate or protected forward-looking assertions, and that boards relied on expert advice regarding licensing. The case could resolve through settlement, potentially involving changes to governance practices, internal controls around AI training data, and enhanced disclosure of copyright and privacy risks. Whatever the outcome, the combination of derivative and class actions in the Western District of Washington marks a new phase in how courts and investors scrutinise AI business models. As one policy tracker notes, these suits treat AI copyright and privacy questions not only as technical and regulatory issues, but as matters of securities law and board accountability for technology strategy.

Nic Reeve·
Anthropic Gives Claude Cowork Shared Memory with Chat for Persistent Context
AI & Tech

Anthropic Gives Claude Cowork Shared Memory with Chat for Persistent Context

Anthropic is rolling out a major upgrade to its AI assistant, giving Claude Cowork the ability to seamlessly reuse information it learns in regular chat. The company has merged the memory systems behind Claude’s chat interface and its Cowork desktop agent, so details you share in one surface can now automatically be used in the other. One Shared Memory Across Chat and Cowork Previously, Claude’s long‑term memory was largely confined to chat sessions and was synthesized periodically, meaning it could take up to a day before information carried over into new conversations. Cowork, which runs complex, multistep jobs on a user’s desktop or in the cloud, relied on its own background memory file and prompt stitching to simulate continuity. With the August 25 update, Anthropic has combined these mechanisms into a single, shared memory system that serves both chat and Cowork. Anthropic describes the change simply: the same memory now powers both Claude chat and Cowork. When users hand a task to Cowork—such as drafting reports, updating spreadsheets, or coordinating project documents—the context Claude has accumulated over months of chats is immediately available. Likewise, any new facts or preferences learned during Cowork runs are written back into the shared memory and become available in subsequent chat sessions. Real‑Time Memory, Not Just End‑of‑Chat Summaries Another important shift is how Claude updates memory. Instead of waiting to summarize an entire conversation once it ends, Claude now adds topics to memory in real time as users chat. This means that if a user mentions that a project deadline moved to September, that update can be reflected in memory almost immediately and show up in the very next interaction—whether in chat or Cowork—without requiring a manual “remember this” command. Anthropic’s support materials explain that when Cowork runs in the cloud, what Claude remembers from previous chats is automatically available, and what emerges during Cowork tasks feeds back into chat memory. Behind the scenes, each Cowork prompt is assembled from the user’s immediate request, their global instructions, and a relevant slice of the shared memory, allowing the AI to behave as if it has persistent awareness of roles, projects, and preferences. What Users Gain: Less Repetition, More Continuity The practical effect for users is that they no longer need to repeatedly brief Claude on who they are, what they are working on, or how they like to work every time they switch between chat and Cowork. Anthropic and independent commentators highlight several common scenarios: Persistent project context: Ongoing details such as quarterly goals, client names, and current project status can be retained across weeks or months and recalled in both chat and Cowork. Stable roles and preferences: If a user identifies themselves as an investment analyst, a teacher, or a particular type of creator, Claude can remember that role and tailor responses accordingly, even when individual chats are short or focused on different tasks. Cross‑device consistency: The shared memory applies across web, desktop, and mobile experiences, so moving from a browser chat to the Cowork desktop agent no longer breaks context. Tech industry observers note that this update positions Claude more directly as an AI “teammate” that can track medium‑ and long‑term workstreams instead of acting purely as a session‑bound chatbot. Transparency and User Control Over Memory The shared memory system arrives alongside a push for greater user control. Anthropic now surfaces everything Claude remembers in a dedicated Topics view within memory settings, where users can inspect, edit, or delete individual entries. Memory is stored as discrete, categorized entries rather than a single opaque summary, making it easier to remove outdated or inaccurate information. Users can also pause memory or reset it entirely if they no longer wish Claude to retain prior context. In addition, Anthropic provides guidance on importing and exporting memory, so the information Claude stores about a user is not locked in and can in principle be backed up or moved. Handling Sensitive Topics Anthropic has emphasized that the system is designed to minimize the capture of highly sensitive information by default. Topics such as health data, beliefs, and other potentially sensitive categories are excluded from memory unless users explicitly opt in via an “Include sensitive topics in memory” setting. For business customers, team or enterprise administrators can centrally control whether memory is enabled at all, and may choose more restrictive policies depending on corporate governance requirements. External reporting indicates that memory generation is turned on by default for free, Pro, and Max plans, while Cowork itself is not available on free accounts. For organizations that want to keep different workstreams separated, Anthropic has indicated that the only way to maintain fully separate memories for chat and Cowork is to use different accounts, since the new system treats them as a single unified space. Availability and Limitations The new shared memory capability began rolling out on August 25, 2026, across Claude’s web, desktop, and mobile experiences, as well as Cowork running in the cloud. Earlier in the year, memory support was limited to chat surfaces, and some third‑party analyses noted that Cowork lacked access to that long‑term context. Anthropic’s latest release notes and help center now explicitly state that memory works across both chat and Cowork when the latter runs in the cloud environment. There are still technical constraints. Cowork’s use of memory depends on cloud execution rather than purely local processing, and incognito or memory‑disabled sessions remain stateless by design. As with other AI systems, Anthropic cautions that Claude’s memory is selective: it prioritizes high‑level preferences and recurring topics rather than storing every detail of every conversation. A Step Toward More Personalized AI Workflows By unifying memory between Claude chat and Cowork, Anthropic is betting that users will value a more personalized and continuous AI experience, particularly for complex, ongoing work. The update reduces friction for individuals juggling multiple projects and gives enterprises a clearer path to building AI‑augmented workflows that persist over time. At the same time, the company is attempting to balance convenience with privacy and security by giving users fine‑grained controls and limiting sensitive data retention by default.

Nic Reeve·
AInews: How Sovereign Open-Weight Models Became the New Tech Frontier
AI & Tech

AInews: How Sovereign Open-Weight Models Became the New Tech Frontier

On August 4, 2026, a new U.S. federal AI governance framework and a wave of recent open-weight model releases showed how sovereign, open-weight AI has moved to the technology frontier, a shift widely tracked under the banner of AInews in policy and developer circles. Why is sovereign, open-weight AI suddenly at the frontier? Governments and firms now treat control over model weights and infrastructure as strategic, responding to security, cost and IP concerns while exploiting a flood of large open-weight releases from Asia, Europe and the United States. The frontier has moved fast in mid-2026. Several developments converged in weeks, not years: On August 4, 2026 , the White House briefed a federal AI governance framework that exempts open-weight models from security review , while subjecting closed frontier systems to a 30‑day evaluation window. According to a July 21, 2026 analysis of Moonshot AI’s Kimi K3, open-weight models publish trained parameters for anyone to download and run, even if code and training data remain closed. A July 20, 2026 European policy paper defined “sovereign capability” as intellectual and operational control, infrastructure independence from non‑EU providers, and verifiable reproducibility of training and safety methods. The Sovereign AI Index published on August 18, 2026 reported that most national model projects rely on fine‑tuning foreign open-weight bases on local data to embed language and culture at lower cost. An August 28, 2026 business analysis described a “third way” for firms: building domain models on their own rights‑cleared data to avoid dependence on external providers while protecting proprietary information. These strands combine into a clear frontier: open-weight models as the common substrate, sovereign infrastructure and data as the differentiator. What recent open-weight releases are shaping this frontier? Between early July and early August 2026, model labs and telecoms released multi‑hundred‑billion‑parameter open-weight systems, giving governments and enterprises new options to self‑host high‑end language models. Key releases create the technical base for sovereign deployments: On July 27, 2026 , Moonshot AI’s Kimi K3 mixture‑of‑experts model went live with 2.8 trillion total parameters and 104 billion active per token , with full weights downloadable on Hugging Face. A July 21, 2026 report called Kimi K3 the largest open-weight model built to date, noting that weights would be published by July 27 so governments or firms with sufficient hardware could run it “without paying a single cent per token.” An open-source release tracker on July 20, 2026 listed nine notable models whose weights were downloadable by July 27, including: Hy3 – 295 billion parameters, 21 billion active, with a permissive open-weight license. Inkling – 975 billion parameters, 41 billion active, also permissive open-weight. Solar Open 2 – 250 billion parameters, 15 billion active, under a custom open license. Laguna S 2.1 – 118 billion parameters, 8 billion active, using the OpenMDW‑1.1 license. A July 31, 2026 release summary counted 11 open-weight models shipped in July 2026 , led by Kimi K3 and including compact and realtime systems such as MOSS‑VL‑Realtime and Laguna S 2.1. An August 19, 2026 benchmark showed GLM‑5.3’s weights will be publicly released under an MIT license after safety audits, extending the open-weight pool with another high‑performing system. These releases kept capabilities near the frontier while lowering the entry barrier for any actor able to procure compute. How are governments using open-weight models to pursue AI sovereignty? Governments are backing domestic foundation model projects and regulatory carve‑outs that favour self‑hosted or locally built systems, viewing open weights as a route to national control over critical AI infrastructure. Recent moves show how policy and engineering align: The South Korean Ministry of Science and ICT is running a Sovereign AI Foundation Model project , described on August 1, 2026 as a government‑backed competition to build large models using “entirely domestic South Korean technology and data.” No frozen weights from foreign models are allowed. The same report noted that SK Telecom released A.X K2 , a 688‑billion‑parameter open-weight model, on July 29, 2026, followed two days later by LG AI Research’s K‑EXAONE 2.0 , a 750‑billion‑parameter model. The European Futurium platform on July 20, 2026 laid out three criteria for classifying a system as sovereign and open in Europe: IP, architecture and governance under European jurisdiction. Compilation, fine‑tuning and deployment on European, multi‑provider infrastructure, without hard dependencies on non‑EU APIs. Transparent training, dataset lineage and safety alignment open to independent audit. The Sovereign AI Index published on August 18, 2026 observed that most national foundation model efforts fine‑tune foreign open-weight bases on local data to encode national languages, cultural context and sector knowledge at a fraction of full training cost. An August 20, 2026 insight from the same index reported that as of mid‑2026, Meta’s Llama remains the most used base model for tracked sovereign AI projects, with France’s Mistral and Google’s Gemma tied for second. Policy and procurement choices are turning open-weight availability into a lever of geopolitical and industrial strategy. How are companies building their own sovereign AI stacks? Enterprises are combining downloadable weights with proprietary data and self‑hosted infrastructure to reduce reliance on external providers, following a “third way” between public APIs and full in‑house training. Recent reporting highlights this corporate approach: An August 28, 2026 analysis of Thomson Reuters’ strategy described how firms with “unique, rights‑cleared data” can build specialized AI models to protect IP while cutting dependence on third‑party providers. The same piece argued that this method brings AI sovereignty to the firm level, not just the nation, by keeping both the model and data inside controlled environments. A July 24, 2026 technical guide introduced the term “weight sovereignty” as legal and operational control over a model artifact. Under this model, organizations can download, inspect, fine‑tune, quantize and run open-weight systems on hardware they own, and switch models later without rewriting their products. The guide explained that open weights alone do not provide “context sovereignty,” which refers to controlling the institutional knowledge a model accesses via embeddings and retrieval. To combine both forms of control, the guide recommended running an open-weight model endpoint entirely inside a firm’s own perimeter and keeping the knowledge layer that feeds it within the same boundary. For large enterprises, the attraction is clear. They get frontier performance while keeping strategic data and operations in‑house. What does the U.S. federal framework mean for open-weight AI? The U.S. framework outlined in early August 2026 creates lighter regulatory friction for open-weight models, signaling that self‑hosted, downloadable systems will face fewer federal hurdles than closed frontier services. Key elements highlighted in an August 11, 2026 policy brief include: The White House framework exempts open-weight models from federal security review, even when they reach frontier‑level capabilities. Closed frontier models face a 30‑day evaluation window under federal oversight before deployment or major updates. The brief argued that this asymmetry “may have more practical impact than anything else” in the document, because it makes self‑hosted AI based on downloadable weights the lower‑friction path for many organizations. The driver behind this structure is the assumption that actors with operational control over their own deployments can manage risks locally, reducing the need for central pre‑authorization. The framework does not remove safety obligations, but it places more responsibility on deployers while granting them more freedom in system choice and architecture. Where does India’s new sovereign AI stack fit into the trend? India’s technology sector is building its own sovereign AI layers on top of open-weight models, aiming to serve domestic enterprises and public institutions with locally governed tools and agents. A late‑August 2026 report described the launch of Artha , a sovereign AI stack from Indian firm Gnani: Artha is designed as an end‑to‑end stack for Indian enterprises and public institutions, incorporating models and orchestration tools. Two components, Evon v3.3 and Plexus, form part of the stack, supporting both foundational capabilities and downstream agents. The approach mirrors sovereign AI agendas in other countries but targets sectoral deployments such as contact centers, financial services and government applications. Artha illustrates how open-weight availability enables regional players to craft localized AI ecosystems under domestic governance. What challenges remain for achieving true technological sovereignty with open weights? Open-weight systems lower barriers to self‑hosting, but analysts warn they are not enough by themselves to deliver full technological sovereignty, which also depends on data, infrastructure, and transparent methods. Recent commentary points to several obstacles: A July 21, 2026 article argued that open-weight systems “alone do not solve the issue of technological sovereignty,” because they release parameters but not necessarily training data, code or full methodology. The same piece cited the Open Source Initiative’s 2025 definition that genuinely open-source models must publish code and data, not just weights. The Sovereign AI Index found that three‑fifths of disclosed foreign bases used in national projects are American, with Meta’s Llama as the most common base, which raises dependency questions. European policy thinkers stressed that without infrastructure independence from non‑EU cloud and API providers, countries may gain model access but not operational control. Analysts also warned that opaque dataset lineage and safety alignment can undermine auditability, even when weights are downloadable. Open weights are a powerful tool. They are not a complete solution. What happens next in the race for sovereign, open-weight AI? The next phase is likely to feature larger domestic foundation projects, more permissive open-weight licenses, and firm‑level strategies that treat AI infrastructure as a core asset rather than a rented service. Several trends are already visible: South Korea’s elimination‑style Sovereign AI competition will test whether fully domestic technology stacks can match performance built on foreign open weights. European initiatives will try to move from dependency on American bases such as Llama to home‑grown architectures governed under EU law. Enterprises following the Thomson Reuters model are likely to expand internal AI teams and infrastructure budgets to keep both weights and data in‑house. Labs promising open-weight releases, such as the MIT‑licensed GLM‑5.3 after its safety review, will broaden the technical menu for sovereign projects. Policy frameworks that distinguish between open-weight and closed frontier systems, as in the U.S. brief, may be replicated in other jurisdictions. The frontier is no longer defined only by raw model scale. It is defined by who controls the weights, the infrastructure and the knowledge that models read.

Nic Reeve·