Releasesby GlyphNew compute plans, and new IDs for existing plans
We're introducing new compute plans for Render services, including memory-optimized plans with higher ratios of RAM to CPU and a new 12-CPU tier for web services, private services, and background workers. To support the expanded catalog, we're also changing compute plan IDs to a spec-based format that includes the relevant specs.
Also shipped Aug 26, 2026Render in August 2026 →
You can now view real-time logs for your Python UDFs in Cloud Logging
You can now view real-time logs for your Python UDFs in Cloud Logging. This feature is generally available .
Cortex Extension references in agent skills (General availability)
Referencing a Cortex Extension from an agent skill is now generally available. Set the skill source type to CORTEX_EXTENSION and path to the extension's fully qualified name, and Snowflake expands the reference into the extension's member skills at request time, so you don't list each skill individually.
Cortex Agents Coding Agent (General availability)
The Cortex Agents Coding Agent is now generally available. Add the code_toolset_all tool type to a Cortex Agent, and Snowflake provisions and manages a sandbox backed by the same runtime that powers Snowflake CoCo: bash, file read/write/edit, grep, glob, web search, SQL execution, and skills.
Organization user types (General availability)
With this release, you can specify whether an organization user represents a person or a service. Set the TYPE property to SERVICE for a service or application that interacts with Snowflake without human interaction. If you don't specify a type, the organization user is a PERSON user, which matches the previous behavior.
Semantic Studio (Preview)
Semantic Studio is now available in public preview for all accounts. Semantic Studio is the authoring environment for semantic views in Workspaces, combining conversational authoring with CoCo, direct YAML editing, and deployment to the live Snowflake object in a single surface.
Zerobus Ingest into streaming tables is now generally available
Ingesting into streaming tables with Zerobus Ingest in Lakeflow Connect is now generally available. Writing to a streaming table works the same way as writing to a managed Delta table, with the same limits and quotas. See Create or identify the target table .
More from RenderEvery Render release →
Introduced the Flex compute plan for Render Workflows
Render Workflows uses a new default compute plan for task runs: flex . The flex compute plan provides up to 1 CPU and 4 GB of RAM. Task runs on flex are billed only for the CPU and RAM they actually use, resulting in significantly lower costs for computationally inexpensive runs.
Added usage telemetry to the Render CLI
The Render CLI now automatically collects usage telemetry to help us understand common use cases and improve user experience. Telemetry is enabled by default in version 2.26.0 or later.
See your service's deploys on a new page
Services now have a new Deploys page in the Render Dashboard. The Deploys page features: Your service's deploy history, without a date cutoff. A Live badge indicating the current deploy. Status of in-progress deploys. A banner flagging when auto-deploys are disabled.
Reduced median service build time by 40% (all runtimes)
Render service builds now run on nodes with faster CPU and disk. These improvements have reduced the median build time for a Render service by 40%, with this reduction reflected across all runtimes: Before this rollout (week of July 13), median build time was 38 seconds, consistent with prior weeks.
Added Blueprint support for Render Workflows
You can now manage your workflow services using Blueprints , Render's infrastructure-as-code model. Define workflows alongside other service types in your Blueprint YAML.
Managed OIDC now supports Anthropic and OpenAI
Render’s managed OpenID Connect (OIDC) authentication now supports Anthropic and OpenAI in addition to AWS. Render services can authenticate to both providers without storing long-lived API keys. Render instead issues short-lived identity tokens for each service and automatically rotates them as needed.
Render MCP now supports OAuth for Claude Code, Codex, and Cursor
The Render MCP server now supports OAuth-based authentication for Claude Code, Codex, and Cursor: The MCP server continues to support API key authentication for other applications and non-interactive environments, such as CI/CD. See setup instructions for each supported tool in the documentation .
Added two Key Value plans and lowered prices for larger existing plans
Render now supports two additional compute plans for Key Value instances: 3 GB RAM with up to 3,000 simultaneous connections 50 GB RAM with up to 50,000 simultaneous connections We've also reduced pricing for existing Key Value compute plans that provide at least 1 GB RAM.