live wire
▸Snowflake’s Cortex Agent quickstart routes metrics and transcripts with prompt rules—but documents no authorization boundarySnowflake▸Oracle Select AI generates SQL/PGQ for property graphs—but errors if one AI profile mixes graphs with tables or viewsOracle▸Domo’s data team standardizes MCP builds with shared scaffolding; beta toolkits inherit user permissionsDomo▸Databricks proposes five outcome signals for agentic BI—and says dashboard counts and license usage miss decision qualityDatabricks▸One vibe-coded database app needed 56+ human test hours and three repair rounds despite AI Studio’s verification claimsMancas & Mancas / arXiv▸BigQuery AI.IF’s default cost mode trains a local model for most rows—and drops row-error thresholdsGoogle Cloud▸AWS’s multi-tenant data-agent pattern gives the broker Lambda no data permissions; Cognito roles carry Lake Formation scopeAWS Big Data Blog▸Amazon OpenSearch’s optimized engine adds nested agent traces, but AWS reserves it for log analytics—not vector searchAWS▸Two interpretation-based provenance semantics cannot express SQL bag difference, new theorem showsKolaitis / arXiv▸Databricks Feature Views reuse one definition for training and live scoring, but online lookup still returns latest available stateDatabricks▸Databricks Genie’s Slack and Teams previews default channel answers to public, even when viewers lack source-data accessDatabricks▸Snowflake’s two-tool GraphRAG agent beat a seven-tool graph setup 70% to 60% on 22 ontology questionsSnowflake Engineering▸Semantix opens an Apache-2.0 semantic-first data-agent stack, but labels the project WIP and has no release or adoption yetGitHub / icosmos-space▸Confluent defines Streamhouse as shared current state for agents and apps, but says broader semantics and governance are still to comeConfluent▸Snowflake’s Cortex Agent quickstart routes metrics and transcripts with prompt rules—but documents no authorization boundarySnowflake▸Oracle Select AI generates SQL/PGQ for property graphs—but errors if one AI profile mixes graphs with tables or viewsOracle▸Domo’s data team standardizes MCP builds with shared scaffolding; beta toolkits inherit user permissionsDomo▸Databricks proposes five outcome signals for agentic BI—and says dashboard counts and license usage miss decision qualityDatabricks▸One vibe-coded database app needed 56+ human test hours and three repair rounds despite AI Studio’s verification claimsMancas & Mancas / arXiv▸BigQuery AI.IF’s default cost mode trains a local model for most rows—and drops row-error thresholdsGoogle Cloud▸AWS’s multi-tenant data-agent pattern gives the broker Lambda no data permissions; Cognito roles carry Lake Formation scopeAWS Big Data Blog▸Amazon OpenSearch’s optimized engine adds nested agent traces, but AWS reserves it for log analytics—not vector searchAWS▸Two interpretation-based provenance semantics cannot express SQL bag difference, new theorem showsKolaitis / arXiv▸Databricks Feature Views reuse one definition for training and live scoring, but online lookup still returns latest available stateDatabricks▸Databricks Genie’s Slack and Teams previews default channel answers to public, even when viewers lack source-data accessDatabricks▸Snowflake’s two-tool GraphRAG agent beat a seven-tool graph setup 70% to 60% on 22 ontology questionsSnowflake Engineering▸Semantix opens an Apache-2.0 semantic-first data-agent stack, but labels the project WIP and has no release or adoption yetGitHub / icosmos-space▸Confluent defines Streamhouse as shared current state for agents and apps, but says broader semantics and governance are still to comeConfluent
nl2sql.ai
releaseRelease

ThoughtSpot puts its SpotterCode agent inside the embed prototyping loop

The new Playground panel turns natural-language requests into runnable Visual Embed SDK code, while leaving execution and conflict resolution with the developer.

AI-assisted embed coding in a developer playground.
Side by side: what changed
By The News Desk· Sep 12, 2026the quick take — two AI hosts go live when you do

ThoughtSpot has added its SpotterCode coding assistant to the Visual Embed Playground, putting prompt-to-code generation beside the editor and live preview developers already use to prototype embedded analytics. The company says the assistant is available now in the Playground for ThoughtSpot instances where the feature is enabled. ThoughtSpot’s announcement positions the addition as a faster route from an intended embed behavior to working SDK code.

What changed

Developers can choose an embed component, describe the desired result in natural language and have SpotterCode update the Playground’s code editor. The generated code targets ThoughtSpot’s Visual Embed SDK and REST APIs; developers then click Run to execute it in the preview pane and can continue with follow-up prompts or edit the code directly. The product documentation lists supported Playground contexts including Search Data, Liveboards, individual visualizations, the full application and the Spotter analytics agent.

Starter prompts illustrate the intended scope: applying runtime filters, keeping a data panel collapsed, adding custom actions, enabling Spotter in a full-app embed and changing interface labels. That makes this less a general-purpose coding agent than a narrowly scoped configuration assistant for ThoughtSpot’s embedding surface.

There is an important guardrail in the workflow. According to ThoughtSpot’s documentation, SpotterCode does not update the editor when it detects a conflict with existing code. The developer must review and clear the conflicting section before trying again. Generated output is also not run automatically; execution remains a separate click in the Playground.

Why it matters

SpotterCode was already designed to connect AI-native development environments such as Cursor and Claude Code to ThoughtSpot’s SDK and API knowledge through an MCP server. The Playground integration moves the same grounded-assistant idea into a disposable prototyping environment, where teams can test an embed configuration before carrying the resulting code into an application. ThoughtSpot distinguishes the IDE use case—working within a project’s structure and design system—from the Playground’s faster explore-and-preview loop.

For analytics teams, the practical significance is not autonomous software delivery. It is a shorter path through a configuration-heavy SDK: prompt for a component or customization, inspect the generated implementation, run it against the instance, and iterate. The feature remains bounded by the APIs and configuration options ThoughtSpot exposes, and its own conflict behavior reinforces that developers still own review and integration.

The release is another sign that analytics vendors are moving natural-language interfaces beyond asking questions of data and into building the surrounding analytics experience. Here, the agent is not writing a SQL query for an analyst; it is helping a developer assemble the product surface in which those queries and answers will appear.

sources

Filed by The News Desk. Corrections: desk@nl2sql.ai · Our standards →

comments · 0

    Comments are moderated before they appear. Your email is used once to confirm it is you — never shown, never sold. Corrections and questions get an answer from the desk when we have one.

    more from the desk