Today, we’re launching self-learning context enrichment (preview) and a reimagined Knowledge Studio experience (preview) in Knowledge Catalog, Google Cloud’s context engine for agents. Building on Knowledge Catalog’s existing Gemini-powered enrichment, self-learning enrichment analyzes agent and user interactions to find gaps and keep your business context accurate and current. Knowledge Studio is the new command center for context engineers and data stewards to explore their data estate conversationally, navigate a visual context graph, and review proposed changes to the context graph before they are published to their users and agents.
An agent is only as good as the organization-wide definitions, rules, and relationships it reasons over — the context, as it were. That’s why curating context has become one of the most important disciplines in enterprise agentic capabilities. Today, most of that work happens by hand. Context engineers write prompts and mappings agent by agent, while data stewards try to manually keep definitions current across thousands of assets. But this breaks down as organizations move from a handful of agents to thousands, and eventually millions.
Knowledge Catalog’s Gemini-powered self-learning enrichment turns that manual upkeep into a continuous feedback loop. By analyzing agent and user interactions, it pinpoints missing or outdated context and pulls verified definitions from playbooks, code repositories, and business documents into governed, reusable context sets. Then, with optimized search, every agent gets precisely the right context it needs instead of reasoning over bloated prompts and raw schemas, and benefits from shared learning across your organization. Knowledge Catalog makes AI agents nearly 4X more accurate, with up to 33% lower latency, and using up to 75% fewer tokens, based on internal benchmarks.
Keep context current with Gemini-powered self-learning enrichment
Consider a simple question to a Gemini agent: “What was the net revenue in EMEA last quarter?” Answering it correctly requires knowing how your company defines net revenue, which tables hold the bookings, and how they join, yet that knowledge is typically scattered across a finance playbook in Google Docs, a data model in GitHub, and a Confluence page. Static catalogs expect subject matter experts to manually capture and update business definitions, metrics, and other context upfront so that an agent can effectively query the right data. However, in reality, experts rarely have the time to document every asset, and the moment the finance team revises how partner credits are treated next quarter, static definitions fall behind and every agent with a hardcoded formula starts giving the wrong answer.
Knowledge Catalog’s enrichment capability acts where you already keep your business knowledge: across your team’s every doc, repo, and table. It connects to your structured data across first-party and third-party sources and unstructured data in Cloud Storage, Google Workspace, GitHub, Confluence, and SharePoint. It finds, extracts, assembles, and maintains that business knowledge for you, linking those unstructured sources like playbooks and wikis and their context to your structured metadata in Knowledge Catalog like tables and schemas to make your structured data far more discoverable and actionable. On demand or on a schedule, it proposes business definitions, table and column descriptions, join relationships, golden queries, and task-specific agent instructions, each with source citations and a confidence score. On every run, it detects what changed at the source, retires obsolete definitions, and flags conflicts for review.
It learns from both your user and agent interactions. You can configure enrichment to analyze interaction traces from Gemini agents, Conversational Analytics in BigQuery, or your custom agents while redacting PII, and it pinpoints where agents struggled, such as ambiguous column lookups, ungrounded metrics, missing definitions, or users rephrasing the same question. It then finds the authoritative answer and stages a fix, so the same mistake doesn’t happen twice. That’s how context engineering keeps pace with millions of agent interactions, freeing experts to review changes instead of writing them from scratch.
