Futureweb

Distributed Cloud

Google Cloud says Data Agent Kit became generally available on September 30. InfoQ and LavX wrote it up on October 24, and LavX dates the GA later than Google does.

Google's Data Agent Kit post is dated September 30, 2026. InfoQ and LavX wrote on October 24. LavX dates the GA later than the post does. September wins.

The short version

The Google Cloud blog post by Arun Nair and Jeff Nelson is dated September 30, 2026, and it says the kit is generally available. InfoQ and LavX published accounts on October 24. LavX dates the GA to October 24. The September 30 post is the record. GA adds BigQuery Graph, Bigtable, and Managed Service for Apache Spark. This page does not print an IAM recipe.

September 30 is the product date

Arun Nair and Jeff Nelson posted on the Google Cloud blog on September 30, 2026 that Data Agent Kit is generally available. The post calls it a free set of Model Context Protocol tools and skills that let a coding agent the reader already uses talk to Google Cloud data products. With GA, the post says, the kit adds BigQuery Graph, Bigtable, and Managed Service for Apache Spark, plus what it calls dozens of quality-of-life improvements. More than 15 Google Data Cloud services is the post's scope for the connections. InfoQ's October 24 story, and LavX's story the same morning, are accounts of that kit. They are not a second launch.Origin Range Requests are a Cloudflare cache change.

LavX moves the date

LavX's October 24 piece says Google released the kit to general availability on October 24 and that a summer preview had just ended. The blog post is dated September 30 and says the kit is generally available that day. ComputeLabs published a research note on October 9 that already describes GA as a fact. This page does not split the difference. A later article can be the first time a reader heard about a September post. It cannot move the post. Where LavX and the blog disagree on the day, the blog wins.Cloudflare's October 9 profiling post is a different product.

What the tools are, in the post's words

The post separates two pieces. MCP tools connect the agent to the data services so it can inspect schemas, run queries, read job logs, and manage resources. Skills are instructions Google says its engineers wrote, for practices such as SQL shape, row keys, and pipelines. The product page says there is no charge for the kit for Google Cloud users. Neither page says a query against those services is free. A free plugin in front of a metered warehouse is still a metered warehouse.K-ISMS is a certificate, not a data plugin.

Who the post says can use it

The September 30 post names Antigravity, Claude Code, Codex, and other tools, plus an IDE extension for VS Code, Antigravity, Cursor, and other VS Code-compatible editors, and a plugin path for Antigravity, Claude Code, and Codex. It says Cloud Shell and Cloud Workstations have it preinstalled. That is a list of clients, not a claim that every agent on the internet gained Google data access on September 30. A project that never installs the kit is outside it. A project that does still needs the cloud project's own permissions. This page does not print those permissions.a TLS certificate binds a name, not a warehouse.

Skills are not the same control as IAM

InfoQ's headline splits guardrails between skills and IAM. LavX describes one skill that stops and asks before irreversible actions. That is a prompt the agent is supposed to follow. IAM is the project's actual permission. A skill that asks nicely is not a boundary the platform enforces. This page will not paste the skill text or the list of statements it worries about. The distinction is the news: one control lives in the instruction, and the other lives in the cloud project.

What GA does not mean

Generally available, on this post, means the named additions are no longer preview features of the kit. It does not mean every Google data product is in the kit, and it does not mean an agent is allowed to change production because the tool can see it. The post's examples, a graph built from tables, a Bigtable row key, a Spark job, are illustrations. They are not case studies with a customer's name.

Why it is on an October 24 wire

The wire carried InfoQ's October 24 headline. A desk that files the headline as the launch will file the wrong day. The honest brief is the gap: a September 30 post, an October 9 note that already says GA, and two October 24 articles, one of which redates the announcement. Readers who pin a release from a news date will pin the wrong week. Asked directly, What did general availability add, on Google's post? BigQuery Graph, Bigtable, and Managed Service for Apache Spark, on top of a kit the post says already reaches more than 15 Google Data Cloud services.the Node October release is a version, not a kit.

ComputeLabs is a fourth, and it is earlier

ComputeLabs is not one of the three sources at the bottom, because Google, InfoQ, and LavX already fill the record. It matters only as a date check. An October 9 page that treats GA as past is incompatible with an October 24 launch. It is compatible with a September 30 post that took a few days to be summarized. Asked directly, Did Data Agent Kit launch on October 24, 2026? The accounts did. The product post is September 30. ComputeLabs has a note dated October 9 that already treats GA as done. October 24 is when InfoQ and LavX wrote.

The limit

No IAM steps. No skill script. No claim that October 24 is the GA. The record is the September 30 post, and the October 24 pieces are accounts, one of them wrong about the day. The short answer this page will stand on is this: The Google Cloud blog post by Arun Nair and Jeff Nelson is dated September 30, 2026, and it says the kit is generally available. InfoQ and LavX published accounts on October 24. LavX dates the GA to October 24. The September 30 post is the record. GA adds BigQuery Graph, Bigtable, and Managed Service for Apache Spark. This page does not print an IAM recipe.

Sources

The reports this brief is filing. Futureweb did not republish them.

  1. Google Cloud blog
  2. InfoQ
  3. LavX News

Questions

Did Data Agent Kit launch on October 24, 2026?

The accounts did. The product post is September 30. ComputeLabs has a note dated October 9 that already treats GA as done. October 24 is when InfoQ and LavX wrote.

What did general availability add, on Google's post?

BigQuery Graph, Bigtable, and Managed Service for Apache Spark, on top of a kit the post says already reaches more than 15 Google Data Cloud services.

Is the kit a charge, on Google's account?

The post says the MCP tools and skills are free. It does not say the underlying queries and storage are free. ComputeLabs makes that distinction. This page keeps it.

Where does Google say the kit runs?

Antigravity, Claude Code, Codex, VS Code-compatible editors, and preinstalled in Cloud Shell and Cloud Workstations. That list is the post's, not a test this page ran.

Does this page repeat a skill's command list?

No. LavX describes a skill that asks for confirmation before destructive steps. The steps stay in the skill. The news is that the guardrail is a prompt, and that IAM is a different control.