Google Gemini Spark Leak: A 24/7 Gemini Agent May Be Coming

Sun, 17 May 2026 11:58:08 +0800

Google has not officially released Gemini Spark.

Current information about it mainly comes from internal Gemini Web test screens, community screenshots, TestingCatalog reporting, and 36Kr / Xinzhiyuan’s summary of related leaks. The consistent picture is that Gemini Spark BETA may be an always-on AI Agent that Google is preparing. Its positioning is no longer just a chat assistant, but an “everyday AI agent” that can handle email, online tasks, and multi-step workflows in the background.

So the boundary should be clear first: this is a leak analysis, not an official Google announcement. All features, naming, and launch timing still need to be confirmed by Google.

Bottom line

Based on currently exposed information, Gemini Spark has three key points:

It may be a 24-hour online Agent inside the Gemini system, not a normal chat model.
It may use broader personal context, including Google apps, chat history, tasks, logged-in websites, and location.
Its risks are as large as its appeal, because it may involve information sharing, remote browser data, purchases, and third-party service calls.

If Google really launches Spark, Gemini’s role will change from “AI that answers questions” to “AI that continuously handles tasks for you.”

What Gemini Spark is

TestingCatalog reported on May 14, 2026 that Google is testing Gemini Spark BETA inside Gemini Web. The exposed welcome text describes it as an everyday AI agent that can help users 24/7 with inbox, online tasks, and more multi-step work.

The 36Kr / Xinzhiyuan article also says that after Spark was uncovered, the outside world saw a “full-time Agent” direction: it can stay on standby all day, process inboxes, execute online tasks, and may even involve purchases and information sharing.

This means Spark is not simply a new model name. It looks more like a Gemini product-layer upgrade: bringing Gemini out of the conversation window and into users’ email, web, calendar, tasks, and cross-app workflows.

How it may work

According to the hidden onboarding text disclosed by TestingCatalog, Gemini Spark may gather context from multiple sources, including:

Connected Apps.
skills.
chats.
tasks.
Websites the user has logged into.
Personal intelligence.
location.

This information would help Spark understand what the user wants to complete and call the necessary context while executing tasks. The text also says that, to complete some actions, Gemini may share necessary information with third parties, such as names, contact details, files, preferences, and information the user may consider sensitive.

If these descriptions prove accurate, Spark will work more like a context-aware agent system than a one-shot Q&A assistant. It will not only look at the current prompt, but may combine long-term preferences, connected apps, browser state, and task history.

Why it matters

The key to Gemini Spark is not one more chat entry point. It is that Google has a natural ecosystem entry point.

OpenAI and Anthropic can build powerful Agents, but they do not naturally own the full chain of Gmail, Calendar, Drive, Chrome, Android, and Workspace. If Google connects Spark into these products, users will not need to build many extra workflows before letting an Agent enter daily work.

This may bring three changes.

First, Gemini may move from passive Q&A to active execution. Users may no longer only ask “summarize this email”; they may ask it to continuously organize the inbox, track tasks, and take follow-up actions.

Second, Agents will rely more on personal context. The more it understands your email, calendar, files, browser state, and preferences, the more useful the result may be.

Third, permission boundaries will become more sensitive. Doing more also means users need to know more clearly when it can act, how far it can go, and whether confirmation is required.

Where the risks are

Several details in the onboarding text disclosed by TestingCatalog are worth watching.

First, Spark is experimental. Even if it launches, it should not be treated as a fully mature system that needs no supervision.

Second, although the system is designed to ask for permission before sensitive operations, the text also warns that it may share information or complete purchases without asking.

Third, to maintain session continuity, Gemini will save remote browser data, such as login details and remote code execution data. Users can clear these data in Settings and can also disable Connected Apps and Personal intelligence.

Taken together, these points show that Spark’s product direction is aggressive: it wants to be an Agent that can truly execute tasks, not only generate suggestions. But the closer it gets to real execution, the more it needs strict permissioning, auditing, confirmation, and rollback mechanisms.

Relationship with Remy and AI Ultra

TestingCatalog says Spark may be a renamed version of the agentic Gemini upgrade previously codenamed Remy, and may also relate to the Gemini Agent direction for Google AI Ultra subscribers.

If this clue is correct, Spark may not be a brand-new project from nowhere. It may be Google repackaging previously higher-end or more closed Agent capabilities and preparing to bring them to a wider audience.

36Kr / Xinzhiyuan also describes it as an upgrade from “Remy” to “Spark”: Gemini Agent is no longer just a feature, but is moving toward a 24/7 digital life manager.

But this is still a judgment based on leaked information. Whether Google will use Spark as the official name, whether it will be limited to AI Ultra, and whether a lighter subscription tier will appear all need official confirmation.

MCP, skills, and the tool ecosystem

The same batch of community screenshots also showed model selector entries such as MCP Tool Testing. The 36Kr article suggests this may hint that the new Gemini will natively support MCP third-party tool integration, with Thinking mode also being rebuilt.

This clue becomes more interesting when viewed together with Spark.

If Spark were only a chat assistant, skills and MCP would matter less. But if Spark is a long-running Agent, it needs to reliably call tools, access web pages, execute tasks, read and write context, and deliver results to users.

In other words, Spark may not be a single feature. It may be part of Google’s Agent tool ecosystem: the model handles understanding and planning, while skills / MCP / connected apps handle execution and expansion.

What it means for ordinary users

If Gemini Spark really launches, ordinary users may see these direct changes:

Email is not only summarized, but can be categorized, followed up, and turned into tasks.
Web tasks are not only suggested, but may be continuously executed in a remote browser.
Calendar, location, preferences, and previous chats become long-term Agent context.
Purchases, bookings, form filling, and similar actions may enter the AI execution range.

This sounds convenient, but users will need new habits: not only checking what the AI says, but also what it is preparing to do, what it has already done, whether it can be undone, and whether there is a record.

Future AI Agent experience may depend not only on model intelligence, but also on clear permission prompts, inspectable task logs, and recovery from mistakes.

What it means for developers and teams

For developers, Spark matters because Google may be moving Agents from “demo products” toward real workflow platforms.

If Spark can reliably connect Google apps, third-party tools, and browser state, developers will care about:

Whether APIs or extension mechanisms are open.
Whether MCP or skills can be connected by third parties.
Whether enterprise admins can control permissions, data retention, and audits.
Whether Agent execution failures have traceable logs.
Whether sandboxing, approval flows, and sensitive-operation confirmation are supported.

For teams, Spark may first enter high-frequency scenarios such as Gmail, Calendar, Docs, Drive, and Chrome. It may not be suitable for fully automated high-risk work at the beginning, but it is a strong fit for inbox triage, meeting follow-up, document organization, market research, and lightweight operations tasks.

How to read it now

This story is best understood as “high-confidence direction, low-certainty details.”

The high-confidence direction is that Google is pushing Gemini Agents to be more proactive, longer-running, and more deeply integrated with its ecosystem. The Gemini Web test text reported by TestingCatalog, community screenshots, and 36Kr’s summary of multiple leaks all point in the same direction.

The low-certainty details are the official name, launch timing, permission rules, subscription tiers, supported regions, API availability, and whether it will really be called Gemini Spark.

The safest view for now:

Do not treat Spark as an already released official product.
Treat it as a strong signal for Google’s next AI Agent direction.
Wait for official explanations around permissions, privacy, third-party data sharing, and remote browser data storage.

Summary

If Gemini Spark eventually launches, it may be a key step in Gemini’s move from chat assistant to always-on Agent. It is not just a model swap; it places Gemini into Google’s ecosystem of email, web, tasks, location, personal intelligence, and third-party services.

Its potential is large: more proactive, closer to real workflows, and easier to distribute to many users through Google’s ecosystem. Its risks are just as large: once AI can share information, save browser state, make purchases, and call third-party services, permission boundaries must be extremely clear.

So the most important question about Gemini Spark is not “how smart is it”, but how Google plans to make a 24-hour online AI Agent controllable, auditable, and trustworthy.

References:

Gemini Spark on KnightLi Blog