Snowflake Cortex · First-party API · LLM

cortex_analyst_text_to_sql

Capability changeCapability change announced Apr 13, 2026

Provider-recommended replacement: system_execute_sql

Notice

Capability change

Capability change announced Apr 13, 2026

Snowflake Cortex documents a capability change: “Apr 13, 2026: Improved SQL generation in Cortex Agents Cortex Agents that use Cortex Analyst semantic views as tools now generate SQL directly, rather than…”

Hosting route
First-party API
Affected scope
Not stated in the notice
Replacement
system_execute_sql
Announced
Apr 13, 2026
First seen by ModelClock
Oct 3, 2026

What the provider published

docs.snowflake.com ↗

Apr 13, 2026: Improved SQL generation in Cortex Agents

Cortex Agents that use Cortex Analyst semantic views as tools now generate SQL directly, rather than delegating SQL generation to the Cortex Analyst service as a separate step. This results in improved accuracy and lower latency for analytical queries.

The tool definition in your agent configuration remains the same. No changes to your agent configuration or semantic views are required. Other resources defined in your semantic view, such as Cortex Search services, continue to be used by the agent.

Changes to the response format

  • Tool use and tool result blocks of type cortex_analyst_text_to_sql are replaced by blocks of type system_execute_sql. The system_execute_sql tool use block contains a sql field with the SQL generated by the agent. The tool result block contains the query_id, result_set, and final sql.
  • If your application parses the agent response for cortex_analyst_text_to_sql blocks, update it to look for

Read from the provider's text; the quote is the provider's exact lines.

Revision history

Loading…
Raw history JSON
cortex_analyst_text_to_sql lifecycle · ModelClock