allnewscastallnewscast
Breaking News
AI & Tech

Google adds xAI’s Grok 4.6 to its enterprise agent marketplace

Nic Reeve3 min read
Google adds xAI’s Grok 4.6 to its enterprise agent marketplace

Google’s enterprise AI platform has added support for xAI’s Grok 4.6, expanding the model choices available to business users building agents and automations. The new listing appears in Google’s Gemini Enterprise Agent Platform documentation and places Grok 4.6 in the platform’s Model Garden, where developers can access third-party models alongside Google’s own offerings.

According to xAI and Google documentation published this week, Grok 4.6 is positioned as xAI’s most capable model for coding, agentic tasks and knowledge work. The model is described as being built for long-running agents and more ambitious interactive and visual work, with a 500,000-token context window and configurable reasoning levels labeled low, medium, high and xhigh.

The addition matters because enterprise teams increasingly want a single environment where they can compare and deploy multiple frontier models without rewriting their entire workflow. By making Grok 4.6 available inside Google’s enterprise agent stack, Google is giving customers another option for tasks that may benefit from longer context handling, multi-step reasoning and tool use. The model is also surfaced with a dedicated publisher-style entry, indicating that it can be selected and managed through the platform’s standard model browsing interface.

xAI’s own release materials say Grok 4.6 is available through the xAI API and partner services, with pricing set at $2 per million input tokens, $0.50 per million cached input tokens and $6 per million output tokens for prompts under 200,000 tokens. For larger prompts of 200,000 tokens or more, xAI says pricing rises to $4 per million input tokens, $1 per million cached input tokens and $12 per million output tokens. Google’s documentation mirrors the availability, listing Grok 4.6 in preview inside Model Garden.

The model’s arrival on Google’s platform follows a broader rollout that xAI announced earlier in August. In its release notes, xAI said Grok 4.6 is intended for coding, agentic tasks and knowledge work, and that it supports text and image input with text-only output. The company also says the model has no stated text output limit and includes tools such as function calling, web search, X search and code execution.

For enterprise customers, the practical appeal is straightforward: Grok 4.6 is being offered as a high-capacity model for jobs that stretch over long sessions, such as software development, research synthesis and multi-step workflow automation. The 500,000-token window gives the model room to hold far more context than many standard systems, while the reasoning controls allow users to adjust how aggressively the model thinks before responding.

Google has not said Grok 4.6 will replace any existing models on the platform, and the documentation frames the addition as another selectable option rather than a default. That means enterprise teams can test it against other models already in the platform for quality, latency and cost before deciding where it fits best.

The move also underscores how cloud AI marketplaces are evolving into neutral distribution channels for rival model makers. Instead of forcing customers into a single vendor’s ecosystem, platforms like Google’s are increasingly acting as aggregators, giving users access to models from multiple providers under one set of enterprise controls.

For now, Grok 4.6’s presence on Google’s enterprise platform is likely to be watched closely by developers who need large context windows and by organizations already experimenting with agentic workflows. The combination of broad availability, configurable reasoning and enterprise distribution could make it a notable option in a crowded market for advanced AI models.

Read more →

Related Articles

AI News: Tech Giants Face New York City Council Over Safety Rules
AI & Tech

AI News: Tech Giants Face New York City Council Over Safety Rules

Google, Meta, OpenAI and Anthropic representatives are appearing before New York City lawmakers on October 5, 2026, for a rare hearing focused on artificial-intelligence safety, accountability and possible local regulations. The proceeding is the latest development in the city’s push to question major technology companies directly, making it a major moment in AI news . Why is the New York City Council holding the hearing? The Council is examining whether fast-moving AI products create risks that existing safeguards do not adequately address. The October 5 hearing brings all 51 Council members together and is being conducted by the Committee of the Whole, allowing lawmakers to question companies in a single public session. Event date: October 5, 2026. Venue: New York City Council hearing in New York City. Participants: Representatives of Anthropic, OpenAI, Google and Meta. Format: Public testimony under oath. Scope: AI safety risks, consumer protection and possible legislative safeguards. According to the New York City Council, the hearing is intended to examine “the potential dangers of AI technology” and gather company input on legislative responses. Council Speaker Julie Menin announced the session on September 28, after earlier letters sought testimony from leading AI companies. Which technology companies agreed to testify? Anthropic, OpenAI, Google and Meta agreed to send representatives. Meta committed a senior executive before the other three companies confirmed participation after the Council warned that subpoenas could be used to compel testimony. Anthropic: The company behind the Claude family of AI models. OpenAI: The creator of ChatGPT and other generative-AI systems. Google: The Alphabet company developing Gemini and related AI services. Meta: The owner of Facebook, Instagram and WhatsApp, which is developing its own AI products. According to Council announcements reported on September 28, OpenAI and Google agreed to appear on the Sunday before the hearing. Reporting published by CBS News on October 4 identified executives from the four companies as scheduled witnesses. Why did subpoenas become part of the dispute? The companies did not all accept the invitations at the same time. Speaker Menin initially requested participation from senior leaders, then warned that the Council could use its subpoena authority. OpenAI, Google and Anthropic later agreed to send representatives, while Meta had already committed to attend. September 16: The Council announced plans for an October 5 hearing and requested participation from major AI leaders. September 25: The Council unveiled proposed legislative measures and reiterated that attendance was expected. September 28: The Council said OpenAI, Google, Anthropic and Meta would testify under oath. October 5: The public hearing is scheduled to take place. According to PoliticsNY, OpenAI, Google and Anthropic agreed to appear after lawmakers threatened subpoenas. The New York City Council separately announced that Elon Musk’s AI company, SpaceXAI, faced a subpoena after it did not confirm participation. What will lawmakers ask the companies? The Council has not published a complete question list, but its announcements identify several areas of concern. Lawmakers are expected to focus on how companies test models, respond to harmful outputs and protect New Yorkers from misuse. How companies identify and reduce safety failures before releasing AI systems. What protections exist for children and other vulnerable users. How platforms respond to self-harm content, fraud, impersonation and manipulated media. Whether companies provide enough transparency about model limits and incidents. What city governments can regulate without conflicting with state or federal law. The hearing follows reports of tens of thousands of AI-related safety incidents cited in recent coverage, although the public material gathered for the hearing does not establish a single official incident count. The Council’s stated purpose is broader: to assess risks and consider safeguards for residents. What legislation is New York City considering? The Council has linked the hearing to a package of proposals aimed at reducing potential harm from AI systems. The measures remain proposals, not enacted city law, and the public hearing is intended to inform debate over their contents and enforceability. Rules addressing the safety and accountability of AI developers. Possible requirements for companies to disclose risks or testing practices. Consumer protections for people affected by automated decisions or generated content. Local responses to harmful or deceptive uses of generative AI. According to the Council’s September 25 announcement, the proposed bills were scheduled for discussion at the October 5 Committee of the Whole hearing. The Council has also questioned whether protections at the state and federal levels are sufficient for New Yorkers. What makes the hearing unusual? The proceeding combines an unusually large group of lawmakers with testimony under oath from several leading AI companies. According to the Council, it is the first time major AI firms have been set to provide public testimony under oath before the body following recent incident reports. 51 Council members: The full City Council is expected to participate. Four companies: Anthropic, OpenAI, Google and Meta have confirmed attendance. Under oath: The format gives testimony a more formal legal setting than a private briefing. Local focus: Questions will center on risks experienced by people in New York City. Fortune reported on September 25 that the hearing would be a Committee of the Whole, a format the Council had not used since 2022. The same report said several requested chief executives were unlikely to appear personally, meaning company representatives may answer questions instead. What happens after the testimony? The Council can use the testimony to revise proposed bills, request further records or pursue additional hearings. The hearing itself does not automatically create new rules. Any measure would still need to move through the Council’s legislative process and comply with higher-level law. Lawmakers may compare company safety policies and public commitments. The Council may seek documents or additional testimony. Proposed legislation could be amended after the hearing. Companies may face continuing scrutiny over AI-related incidents in New York. The subpoena dispute could shape future dealings between City Hall and technology firms. The hearing also places pressure on companies to explain their safeguards in a public forum. Their answers may influence how New York City approaches AI oversight while broader debates continue in Albany and Washington.

Nic Reeve·
Avos Bets on AI Agents to Turn News Into Personalized Daily Briefings
AI & Tech

Avos Bets on AI Agents to Turn News Into Personalized Daily Briefings

Avos pushes personalized AI briefings into the news mainstream as the Cyprus-based startup unveils a product built to turn sprawling online coverage into concise, recurring editions tailored to each reader’s interests. The company’s pitch is simple: instead of forcing users to scroll through endless feeds, Avos uses AI agents to do the reading, filtering, deduplication, and synthesis before delivering a finished briefing. In recent coverage, founder and CEO Stef Roussos described the product as an “agentic news and research platform” designed around personalized recurring briefings, with editions shaped by topics, sources, markets, tone, and schedule. That positioning places Avos in a fast-growing corner of the artificial intelligence market, where companies are moving beyond chatbots and toward systems that can independently complete multi-step knowledge tasks. In Avos’s case, the task is not generating one-off summaries, but producing a recurring news product that aims to resemble a private front page for every reader. A briefing product, not another feed According to recent reporting, Avos is organized around a simple workflow: a user describes what they want to follow in plain language, and the platform does the research in the background. It then gathers articles from its source catalog, removes duplicates, and assembles a single briefing delivered before the user starts the day. That approach reflects a broader industry shift. Many AI news tools focus on summarization, but Avos is built around recurring publication. Instead of asking people to return to a feed repeatedly, the company is trying to give them a finite edition that reduces information overload. That distinction is central to the startup’s identity and to the language Roussos has used in public comments. Recent coverage also says Avos can deliver briefings in six languages and include live financial data blocks for stocks, crypto, forex, and commodities. The service has been described as offering a free ad-supported plan as well as paid tiers that remove ads and expand capacity and features. Stef Roussos frames AI as an economics shift Roussos has argued that advances in agentic AI have changed the economics of personalized news. In the company’s launch coverage, he said the platform can do much of the research on a personalized basis and synthesize it into a front page meaningful to the individual reader at a measured generation cost of roughly three cents per briefing. That cost framing matters because it highlights the company’s thesis: if agents can reliably handle research, filtering, and cross-referencing at scale, then highly personalized editorial products may become economically viable for consumers rather than only for institutions. Avos is essentially betting that automation can make premium information curation affordable enough to reach a broad audience. The company has also emphasized that it is not trying to replace journalism. Instead, its product is presented as a layer that helps readers process the volume of available reporting. In that model, human publishers still produce the underlying coverage, while Avos attempts to organize it into a reader-specific package. Atlas, anchors, and the infrastructure behind the product In the interview coverage, Roussos said the company built a backend system called Atlas to handle the difficult work of searching for, ingesting, processing, and deduplicating content from thousands of sources. That kind of infrastructure is essential to any agentic briefing product, because the quality of the output depends heavily on source coverage, ranking, and cleanup before generation begins. The company has also introduced “Anchor Mode,” described as an interactive audio experience that functions like a news podcast but allows listeners to ask questions for deeper exploration. That feature suggests Avos is experimenting with more than text delivery, aiming to turn briefings into a multi-format information product that can be consumed in different ways throughout the day. Private beta began in March 2026, according to launch reporting, before the platform moved to a public release in August 2026. That timeline suggests Avos has spent several months refining its briefing workflow before opening it more widely to users. Why the launch matters now Avos arrives at a moment when AI companies are racing to prove that agents can do something more practical than answer simple prompts. News and research briefings are a natural test case because they require repeated browsing, source comparison, filtering, and concise synthesis — all tasks that are difficult for humans to perform efficiently at scale every day. The startup’s model also reflects growing demand for personalization in professional information products. Traders, founders, analysts, and operators often want a tighter signal-to-noise ratio than a general-purpose feed provides. By combining source preferences, market context, tone, and timing, Avos is targeting users who value specificity over volume. At the same time, the product raises familiar questions about reliability, editorial transparency, and dependence on automated synthesis. Those questions are not unique to Avos, but they are especially relevant when a platform positions itself as a recurring source of news and research rather than a simple search or summarization tool. What comes next For now, Avos is presenting itself as a practical application of agentic AI rather than a speculative one. Its launch messaging focuses on a clear promise: users define the agenda, and the software does the reading. If the company can consistently deliver accurate, timely, and truly useful briefings, it may help define a category that sits between news aggregation, editorial curation, and automated research. The bigger test will be whether personalized briefings can become a daily habit for users outside a narrow early-adopter group. If they can, Avos may become one of the more visible examples of how agentic AI is beginning to reshape information consumption.

Nic Reeve·
AInews: Gemini 3.6 Flash quietly becomes Antigravity’s new default engine
AI & Tech

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.

Nic Reeve·