ドキュメント変更履歴 2026-08-28

--- ahttps://docs.snowflake.com/en/user-guide/vscode-ext+++ bhttps://docs.snowflake.com/en/user-guide/vscode-ext@@ -197,4 +197,11 @@    - Select **Cloud** (%vsc-view-download-button%) to save the results as a compressed gzip file.    - Select **Save** (%vsc-view-save-button%) to save the results as a comma-separated (CSV) file.++By default, results render with the Snowsight results viewer, the same component that renders+results in %sf-web-interface%. This supports the display of up to 1 million rows. To switch back+to the legacy results table, set **Query Results: Snowsight Results Viewer** to off.++If a query fails, select **Fix with CoCo** next to the error message to ask CoCo for a fix.+For more information, see [](#label-cortex-code-vscode-shortcuts).  ## Work with Snowpark Python code@@ -435,4 +442,86 @@ 3. Select **Remove** (%vsc-trash-button%). +<a id="label-cortex-code-vscode-extension"></a>++## CoCo in the %sf-vscext%++CoCo in the %sf-vscext% brings the CoCo agent into your editor alongside the extension's+existing SQL and Snowpark Python workflows. You can work locally while you stay connected to your Snowflake account.++You can use these capabilities in **Visual Studio Code** or in **Cursor**. Cursor is based on the same+Visual Studio Code extension model, and you can install and run the Snowflake extension there the same way+you install other Visual Studio Code-compatible extensions.++For platform-wide CoCo behavior, security, and governance concepts, see [CoCo](/user-guide/cortex-code/cortex-code).++<a id="label-cortex-code-vscode-enable"></a>++### Prerequisites++Before you use CoCo in the extension, make sure that:++- You are signed in to a Snowflake account with the extension. See [Sign in to Snowflake with the VS Code extension](#label-vscode-ext-sign-in).+- You have network access to reach Snowflake.++You don't need to install the [CoCo CLI](/user-guide/cortex-code/cortex-code-cli) separately. If you do want the extension to use a specific CoCo executable that's already on your machine, set **CoCo: CLI Path** to its full path.++### Use CoCo++CoCo is enabled by default in the extension. After you sign in, select the CoCo icon in the editor toolbar to open the CoCo side panel and start a chat session.++To turn off the CoCo side panel for all workspaces, set **CoCo: Enabled** to off in the Snowflake extension settings. For other extension settings, see [VS Code extension settings](#label-vscode-ext-settings).++<a id="label-cortex-code-vscode-shortcuts"></a>++### Start CoCo from the editor and query results++You can start a CoCo session from the places where you're already working, without switching to the CoCo side panel first:++- **Ask CoCo** appears above each SQL statement in the editor. Select it to open CoCo with that statement as context, so you can ask CoCo to explain, rewrite, or optimize the statement.++  To hide this action, set **CoCo: Show Ask CoCo Above Statement** to off.++- **Fix with CoCo** appears with the error message in the query results pane when a query fails. Select it to open CoCo with the failed statement and its error, so CoCo can suggest a fix.++<a id="label-cortex-code-vscode-capabilities"></a>++### CoCo capabilities in the extension++CoCo in the %sf-vscext% provides the same agent-based interaction model as the CoCo CLI and CoCo in %sf-web-interface%, adapted to a local editor workflow.++#### Conversation and tools++The extension supports natural-language sessions in which CoCo proposes a plan, requests clarification when inputs are incomplete, and recommends executable steps.+Tooling aligns with the CoCo CLI (including web search, shell commands, file edits, and SQL) so operators can reuse familiar workflows across the CLI and the extension.+The UI surfaces agent reasoning, tool invocation, and multi-step status when expanded, and supports cancellation of a response that is still in progress.++#### Snowflake SQL and results++After explicit approval, CoCo can execute SQL and related operations against the Snowflake account that is active in the extension session.+Query results appear in the chat panel alongside narrative output; result grids support copy and download operations from that panel.++#### Workspace and editor context++You can attach workspace files and directories as context by typing `@` in the chat input to reference them.+CoCo also incorporates the active editor buffer, the current text selection, and SQL result content from the extension query results view when generating a reply.++#### Modes, models, and permissions++**Plan** mode prioritizes structured planning before execution. **Bypass** mode reduces intermediate confirmation for workflows where upfront planning is not required.+The extension exposes model selection for the active chat session. For sensitive operations, permission prompts support **allow once**, **allow for the rest of the session**, **allow always**, and **deny** responses.++#### Chat sessions++Chat history is scoped to the directory that is open in the editor, which isolates conversations by workspace.+Users can resume prior sessions, start new sessions, rename or delete entries, and rely on automatically generated session titles. New sessions display recent history and an introductory prompt.++#### Suggested edits and file changes++File edits proposed by CoCo include a summarized diff. Users can accept or revert all changes, restrict actions to a single file, or review and apply or discard edits at a finer granularity before the workspace is updated.++#### Skills++Skills provide packaged capabilities that CoCo can invoke repeatedly. Enter `/` in chat to list or run a skill, consistent with other CoCo interfaces.+ <a id="label-vscode-ext-settings-preview"></a> @@ -474,6 +563,16 @@     </tr>     <tr>+      <td>CoCo: CLI Path</td>+      <td>Overrides the CoCo executable that the extension uses (`snowflake.coco.cliPath`). Leave this unset unless you want to point the extension at a specific CoCo installation.</td>+      <td>Unset</td>+    </tr>+    <tr>       <td>CoCo: Enabled</td>-      <td>Enable or disable CoCo chat in the extension</td>+      <td>Enable or disable the CoCo side panel for all workspaces (`snowflake.coco.enabled`)</td>+      <td>Enabled</td>+    </tr>+    <tr>+      <td>CoCo: Show Ask CoCo Above Statement</td>+      <td>Show the <strong>Ask CoCo</strong> action above each SQL statement in the editor (`snowflake.coco.showAskCocoAboveStatement`)</td>       <td>Enabled</td>     </tr>@@ -532,4 +631,9 @@       <td>Specifies the maximum number of queries shown in history. Showing more queries might affect performance.</td>       <td>1000</td>+    </tr>+    <tr>+      <td>Query Results: Snowsight Results Viewer</td>+      <td>Render query results with the Snowsight results viewer, the same component that renders results in %sf-web-interface%. Disable it to switch back to the legacy results table.</td>+      <td>Enabled</td>     </tr>     <tr>@@ -590,76 +694,4 @@    ``` -<a id="label-cortex-code-vscode-extension"></a>--## CoCo in the %sf-vscext%--Available to all accounts.--CoCo in the %sf-vscext% brings the CoCo agent into your editor alongside the extension's-existing SQL and Snowpark Python workflows. You can work locally while you stay connected to your Snowflake account.--You can use these capabilities in **Visual Studio Code** or in **Cursor**. Cursor is based on the same-Visual Studio Code extension model, and you can install and run the Snowflake extension there the same way-you install other Visual Studio Code-compatible extensions.--For platform-wide CoCo behavior, security, and governance concepts, see [CoCo](/user-guide/cortex-code/cortex-code).--<a id="label-cortex-code-vscode-enable"></a>--### Prerequisites--Before you use CoCo in the extension, make sure that:--- You are signed in to a Snowflak... (truncated) 

差分が長いため、途中まで表示しています。

--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/snowflake-cowork/build-agents+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/snowflake-cowork/build-agents@@ -260,57 +260,58 @@ ## Create an agent -- Combine all of the tools and components to create an agent using SQL:-  ```sql-  CREATE OR REPLACE AGENT <agent_name>-   COMMENT = 'agent level comment'-   PROFILE = '{"display_name": "My Business Assistant", "avatar":  "business-icon.png", "color": "blue"}'-   FROM SPECIFICATION-   $$-   models:-   orchestration: claude-4-sonnet--   orchestration:-   budget:-       seconds: 30-       tokens: 16000--   instructions:-   response: "You will respond in a friendly but concise manner"-   orchestration: "For any revenue question, use Analyst; for policy questions, use Search"-   sample_questions:-       - question: "What was our revenue last quarter?"--   tools:-   - tool_spec:-       type: "cortex_analyst_text_to_sql"-       name: "<your cortex analyst tool name>"-       description: "<clear and specific tool description>"-   - tool_spec:-       type: "cortex_search"-       name: "<your cortex search tool name>"-       description: "<clear and specific tool description>"-   - tool_spec:-       type: "data_to_chart"-       name: "data_to_chart"-       description: "Generates visualizations from data"--   tool_resources:-   <your cortex analyst tool name>:-       semantic_view: "<db>.<schema>.<semantic_view>"-   <your cortex search tool name>:-       search_service: "<db>.<schema>.<search_service_name>"-       max_results: "5"-       filter:-       "@eq":-           region: "North America"-       title_column: "<title_name>"-       id_column: "<column_name>"-   $$;-  ```+To create an agent using SQL:++```sql+CREATE OR REPLACE AGENT <agent_name>+ COMMENT = 'agent level comment'+ PROFILE = '{"display_name": "My Business Assistant", "avatar": "business-icon.png", "color": "blue"}'+ FROM SPECIFICATION+ $$+ models:+ orchestration: claude-4-sonnet++ orchestration:+ budget:+     seconds: 30+     tokens: 16000++ instructions:+ response: "You will respond in a friendly but concise manner"+ orchestration: "For any revenue question, use Analyst; for policy questions, use Search"+ sample_questions:+     - question: "What was our revenue last quarter?"++ tools:+ - tool_spec:+     type: "cortex_analyst_text_to_sql"+     name: "<your cortex analyst tool name>"+     description: "<clear and specific tool description>"+ - tool_spec:+     type: "cortex_search"+     name: "<your cortex search tool name>"+     description: "<clear and specific tool description>"+ - tool_spec:+     type: "data_to_chart"+     name: "data_to_chart"+     description: "Generates visualizations from data"++ tool_resources:+ <your cortex analyst tool name>:+     semantic_view: "<db>.<schema>.<semantic_view>"+ <your cortex search tool name>:+     search_service: "<db>.<schema>.<search_service_name>"+     max_results: "5"+     filter:+     "@eq":+         region: "North America"+     title_column: "<title_name>"+     id_column: "<column_name>"+ $$;+```  <a id="label-snowflake-intelligence-modify-agents"></a> <a id="label-snowflake-cowork-modify-agents"></a> -## Modifying an existing agent+## Modify an existing agent  For instructions on modifying the configuration for an existing agent, including adding tools and updating other details, see [](#label-snowflake-agents-modify-agents). 

--- ahttps://docs.snowflake.com/en/user-guide/cortex-code/extensibility+++ bhttps://docs.snowflake.com/en/user-guide/cortex-code/extensibility@@ -165,8 +165,15 @@ description: Database administration tasks tools:-- snowflake_sql_execute+- sql_execute - snowflake_object_search --- ```++The SQL execution tool has a different name on each surface. CoCo CLI names it `sql_execute` (renamed+from `snowflake_sql_execute` in CLI 1.1.8), while CoCo Desktop still names it+`snowflake_sql_execute`. If a skill has to work on both surfaces, list both names.++Tool names in a skill's `tools:` list are runtime tool IDs and are+case-sensitive. Built-in tools such as `bash`, `read`, and `write` are lowercase.  #### Skill best practices@@ -473,7 +480,7 @@ tools: -- Bash-- Read-- Write+- bash+- read+- write  model: claude-sonnet-4-5@@ -508,7 +515,7 @@ description: Runs tests and reports results tools:-- Bash-- Read-- Grep+- bash+- read+- grep --- @@ -554,8 +561,14 @@ tools: - "*"           # All tools-- Bash          # Specific tools-- Read-- Write-```+- bash          # Specific tools+- read+- write+```++Tool names in a `tools:` list are the runtime tool IDs, which are lowercase, such as `bash`, `read`,+`write`, `grep`, and `glob`. Capitalized names such as `Bash` don't resolve. An unrecognized entry is+skipped silently, so an agent whose whole list is capitalized starts with no tools at all and reports+no error. If your agent behaves as though it can't read files or run commands, check the casing in its+`tools:` list first.  </dd>@@ -704,5 +717,5 @@     "PreToolUse": [       {-        "matcher": "Bash",+        "matcher": "bash",         "hooks": [           {@@ -740,13 +753,16 @@  To execute your hook only on specific tools, place tool names or patterns in the `matcher` field. For example, to-match all SQL tools, use `"matcher": "SQL*"`. You can use regular expressions to match multiple tools.--| Pattern       | Matches                       |-| ------------- | ----------------------------- |-| `*`           | All tools                     |-| `Bash`        | Only Bash                     |-| `Edit\|Write` | Edit or Write                 |-| `mcp__.*`     | All MCP tools                 |-| `Notebook.*`  | NotebookEdit, NotebookExecute |+match all SQL tools, use `"matcher": ".*sql.*"`. You can use regular expressions to match multiple tools.++The pattern is matched against the runtime tool name, which is case-sensitive. Built-in tool names are+lowercase, so `bash` matches and `Bash` doesn't.++| Pattern       | Matches                                   |+| ------------- | ----------------------------------------- |+| `*`           | All tools                                 |+| `bash`        | Only `bash`                               |+| `edit\|write` | `edit` or `write`                         |+| `mcp__.*`     | All MCP tools                             |+| `notebook.*`  | `notebook_edit_cell`, `notebook_run_cell` |  ### Writing hook scripts@@ -765,5 +781,5 @@   "permission_mode": "default",   "hook_event_name": "PreToolUse",-  "tool_name": "Bash",+  "tool_name": "bash",   "tool_input": {     "command": "ls -la" 

--- ahttps://docs.snowflake.com/en/sql-reference/sql/create-security-integration-oauth-snowflake+++ bhttps://docs.snowflake.com/en/sql-reference/sql/create-security-integration-oauth-snowflake@@ -28,4 +28,5 @@   [ ENABLED = { TRUE | FALSE } ]   [ OAUTH_ISSUE_REFRESH_TOKENS = { TRUE | FALSE } ]+  [ OAUTH_ACCESS_TOKEN_VALIDITY = <integer> ]   [ OAUTH_REFRESH_TOKEN_VALIDITY = <integer> ]   [ OAUTH_SINGLE_USE_REFRESH_TOKENS_REQUIRED = { TRUE | FALSE } ]@@ -59,4 +60,5 @@   [ OAUTH_ANY_ROLE_MODE = { DISABLE | ENABLE | ENABLE_FOR_PRIVILEGE } ]   [ OAUTH_ISSUE_REFRESH_TOKENS = { TRUE | FALSE } ]+  [ OAUTH_ACCESS_TOKEN_VALIDITY = <integer> ]   [ OAUTH_REFRESH_TOKEN_VALIDITY = <integer> ]   [ NETWORK_POLICY = '<network_policy>' ]@@ -203,8 +205,20 @@  If this parameter is set to `FALSE` and the security integration also has `ENABLED = TRUE`, the Snowflake OAuth flow-repeats, a non-configurable access token is issued, and the access token is valid for 600 seconds (10 minutes). After this access token-expires, the user must authenticate again.+repeats and an access token is issued. The access token is valid for the duration specified by `OAUTH_ACCESS_TOKEN_VALIDITY`+(600 seconds by default). After this access token expires, the user must authenticate again.  Setting this parameter to `FALSE` and `ENABLED = FALSE` results in no tokens being issued and the integration is disabled.++</dd>+<dt><code className="samp">OAUTH_ACCESS_TOKEN_VALIDITY = <em>integer</em></code></dt>+<dd>++Integer that specifies how long access tokens should be valid (in seconds).++The supported minimum, maximum, and default values are as follows:++- Minimum: `60` (1 minute)+- Maximum: `3600` (1 hour)+- Default: `600` (10 minutes)  </dd>@@ -433,4 +447,16 @@  Default: `TRUE`++</dd>+<dt><code className="samp">OAUTH_ACCESS_TOKEN_VALIDITY = <em>integer</em></code></dt>+<dd>++Integer that specifies how long access tokens should be valid (in seconds).++The supported minimum, maximum, and default values are as follows:++- Minimum: `60` (1 minute)+- Maximum: `3600` (1 hour)+- Default: `600` (10 minutes)  </dd> 

--- ahttps://docs.snowflake.com/en/user-guide/cleanrooms/ml-jobs+++ bhttps://docs.snowflake.com/en/user-guide/cleanrooms/ml-jobs@@ -75,5 +75,5 @@ An ML Jobs code spec defines one or more containerized ML workloads that run on a compute pool. For the full field reference, including `stage_code_dir` requirements and `image_tag` options,-see [Code specification — ML Jobs](/user-guide/cleanrooms/spec-code-spec#label-dcr-collab-code-spec-ml-jobs).+see [ML Jobs code specification](/user-guide/cleanrooms/spec-code-spec#label-dcr-collab-code-spec-ml-jobs).  ## User flow: template provider@@ -121,5 +121,5 @@     entrypoint: train.py     stage_code_dir: '@my_db.public.ml_stage/ml_project'-    image_tag: "2.8.1"+    image_tag: "2.9.0"     pip_requirements:       - pandas@@ -129,12 +129,15 @@ ``` -The `image_tag` field is optional. If you omit it, the collaboration uses the current default-runtime image. The default may change across Snowflake Data Clean Rooms API releases. To ensure your code spec always runs-against the same set of pre-installed libraries and runtime behavior, pin `image_tag` to a-specific version. See [Code specification — ML Jobs](/user-guide/cleanrooms/spec-code-spec#label-dcr-collab-code-spec-ml-jobs)+The `image_tag` field is optional. If you omit it, the collaboration uses the latest available+runtime image. The image is re-evaluated when the code spec is added to a collaboration and on+each subsequent patch. To ensure your code spec runs against a stable, known+set of libraries, pin `image_tag` to a specific version. See+[Container Runtime releases](/developer-guide/snowflake-ml/container-runtime/releases) for the+list of available versions, and+[ML Jobs code specification](/user-guide/cleanrooms/spec-code-spec#label-dcr-collab-code-spec-ml-jobs) for the full field reference.  For the full field reference, see-[Code specification — ML Jobs](/user-guide/cleanrooms/spec-code-spec#label-dcr-collab-code-spec-ml-jobs).+[ML Jobs code specification](/user-guide/cleanrooms/spec-code-spec#label-dcr-collab-code-spec-ml-jobs).  ### 3. Register templates@@ -360,11 +363,14 @@ All pinned `image_tag` values are preserved unchanged. -- **Unspecified `image_tag`:** Uses the current default, which updates when Snowflake Data Clean Rooms ships a new-  default image. To trigger a patch, add a template with the code spec to the collaboration.+- **Unspecified `image_tag`:** Uses the latest available runtime image, resolved when the code+  spec is added to a collaboration. To pick up a new default image on an existing code spec,+  re-add the code spec to the collaboration. - **Pinned `image_tag`:** Your pin is always preserved unchanged across patches. Pin `image_tag`   to run against a stable, known set of libraries. -See [Code specification — ML Jobs](/user-guide/cleanrooms/spec-code-spec#label-dcr-collab-code-spec-ml-jobs)-for the `image_tag` field reference.+See [ML Jobs code specification](/user-guide/cleanrooms/spec-code-spec#label-dcr-collab-code-spec-ml-jobs)+for the `image_tag` field reference and+[Container Runtime releases](/developer-guide/snowflake-ml/container-runtime/releases) for the+list of available versions.  ### Development workflow@@ -378,5 +384,5 @@ a pinned `image_tag`. Pinning the image version locks down the exact set of dependencies you developed and tested with, so the workload runs identically inside the collaboration. See-[Code specification — ML Jobs](/user-guide/cleanrooms/spec-code-spec#label-dcr-collab-code-spec-ml-jobs)+[ML Jobs code specification](/user-guide/cleanrooms/spec-code-spec#label-dcr-collab-code-spec-ml-jobs) for the `image_tag` field reference.  

--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/setup-openflow-spcs-create-rr+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/setup-openflow-spcs-create-rr@@ -1,3 +1,3 @@-# Set up %ofsfspcs%: Create Snowflake role+# Set up %ofsfspcs%: Create execute-as role  This feature is not available in the People's Republic of China.@@ -13,11 +13,11 @@ but to a specific runtime. Typically such resources include: -- Creation of Runtime specific Snowflake role+- Creation of a runtime-specific execute-as role - Creation of Runtime specific network rules and External Access Integrations (EAI)  This topic describes the creation of these resources. -1. Create a Snowflake Role and associated privileges to write data to Snowflake Role for Runtimes on Snowflake Deployment Section-2. Associate Snowflake Role. See Snowflake Role for Runtimes in the Snowflake Deployment Section.+1. Create an execute-as role and associated privileges for runtimes in Snowflake deployments+2. Associate the execute-as role with the runtime. 3. Create External Access Integrations and associate them to Runtimes.    See [Creating External Access Integrations](#label-create-network-rules-and-external-access-integrations)@@ -26,11 +26,11 @@ <a id="label-create-runtime-role"></a> -## Create a Snowflake role+## Create an execute-as role  When creating and editing Openflow Runtimes, Runtime Owners will have the ability to associate a role with the Runtime. This role will be used for flows that execute within the Runtime.-For more information about Snowflake Roles, see [](#label-openflow-spcs-what-is-runtime-role).+For more information about execute-as roles, see [](#label-openflow-spcs-what-is-runtime-role). -Creating a Snowflake role is a prerequisite for creating a Runtime and involves the following steps:+Creating an execute-as role is a prerequisite for creating a runtime and involves the following steps:  1. Create the role itself@@ -39,7 +39,7 @@ 4. Grant the role access to the External Access Integrations used by the Runtime. -To create a Snowflake role:+To create an execute-as role: -1. Create the required Snowflake role.+1. Create the required execute-as role.  @@ -55,11 +55,11 @@    ``` -2. Allow the Snowflake role to use an existing warehouse that you are planning to use for data ingestion.-   Use this warehouse later when configuring your connectors for runtimes where you will be using this Snowflake role.+2. Allow the execute-as role to use an existing warehouse that you are planning to use for data ingestion.+   Use this warehouse later when configuring your connectors for runtimes where you will be using this execute-as role.    ```sql    GRANT USAGE, OPERATE ON WAREHOUSE <OPENFLOW_INGEST_WAREHOUSE> TO ROLE OPENFLOW_RUNTIME_ROLE_;    ``` -3. Allow the Snowflake role to use, create or otherwise access Snowflake objects.+3. Allow the execute-as role to use, create or otherwise access Snowflake objects.  @@ -87,5 +87,5 @@  1. Create the network rule, grouping the network identifiers into logical areas.-2. Create the external access integration (EAI), specifying the list of network rules and assuring the Snowflake Role has USAGE on the EAI.+2. Create the external access integration (EAI), specifying the list of network rules and assuring the execute-as role has USAGE on the EAI. 3. Associate the EAI with the Runtime in the Openflow UI when creating Runtimes. @@ -145,5 +145,5 @@    ``` -3. Grant access to the EAI to the previously created Snowflake role.+3. Grant access to the EAI to the previously created execute-as role.    ```sql    GRANT USAGE ON INTEGRATION OPENFLOW_<RUNTIME_NAME>_EAI TO ROLE OPENFLOW_RUNTIME_ROLE_<RUNTIME_NAME>; 

--- ahttps://docs.snowflake.com/en/sql-reference/sql/alter-security-integration-oauth-snowflake+++ bhttps://docs.snowflake.com/en/sql-reference/sql/alter-security-integration-oauth-snowflake@@ -30,4 +30,5 @@   [ OAUTH_ISSUE_REFRESH_TOKENS = { TRUE | FALSE } ]   [ OAUTH_REDIRECT_URI = '<uri>' ]+  [ OAUTH_ACCESS_TOKEN_VALIDITY = <integer> ]   [ OAUTH_REFRESH_TOKEN_VALIDITY = <integer> ]   [ OAUTH_SINGLE_USE_REFRESH_TOKENS_REQUIRED = { TRUE | FALSE } ]@@ -68,4 +69,5 @@   [ OAUTH_ANY_ROLE_MODE = { DISABLE | ENABLE | ENABLE_FOR_PRIVILEGE } ]   [ OAUTH_ISSUE_REFRESH_TOKENS = { TRUE | FALSE } ]+  [ OAUTH_ACCESS_TOKEN_VALIDITY = <integer> ]   [ OAUTH_REFRESH_TOKEN_VALIDITY = <integer> ]   [ OAUTH_SINGLE_USE_REFRESH_TOKENS_REQUIRED = { TRUE | FALSE } ]@@ -143,4 +145,16 @@  </dd>+<dt><code className="samp">OAUTH_ACCESS_TOKEN_VALIDITY = <em>integer</em></code></dt>+<dd>++Integer that specifies how long access tokens should be valid (in seconds).++The supported minimum, maximum, and default values are as follows:++- Minimum: `60` (1 minute)+- Maximum: `3600` (1 hour)+- Default: `600` (10 minutes)++</dd> <dt><code className="samp">OAUTH_REFRESH_TOKEN_VALIDITY = <em>integer</em></code></dt> <dd>@@ -435,4 +449,16 @@  Default: `TRUE`++</dd>+<dt><code className="samp">OAUTH_ACCESS_TOKEN_VALIDITY = <em>integer</em></code></dt>+<dd>++Integer that specifies how long access tokens should be valid (in seconds).++The supported minimum, maximum, and default values are as follows:++- Minimum: `60` (1 minute)+- Maximum: `3600` (1 hour)+- Default: `600` (10 minutes)  </dd> 

--- ahttps://docs.snowflake.com/en/sql-reference/data-sharing-usage/listing-consumption-daily+++ bhttps://docs.snowflake.com/en/sql-reference/data-sharing-usage/listing-consumption-daily@@ -165,11 +165,19 @@     </tr>     <tr>-      <td>CONSUMER_MCD_OPT_IN_DATE</td>-      <td>TIMESTAMP_LTZ</td>-      <td>-        The date and time when the consumer account enrolled into the MCD-        program. If the consumer account isn't enrolled in the MCD program, the-        value is NULL.-      </td>+      <td>CONSUMER_MCD_OPT_IN_RANGE</td>+      <td>VARCHAR</td>+      <td>++The number of days since the consumer account enrolled in the Marketplace Capacity Drawdown (MCD) program, expressed as a range. One of:++- `< 30 days`+- `30-60 days`+- `60-90 days`+- `90-120 days`+- `> 120 days`++The upper bound of each range is exclusive. If the consumer account isn't enrolled in the MCD program, the value is NULL.++</td>     </tr>   </tbody> 

--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/setup-openflow-byoc+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/setup-openflow-byoc@@ -88,18 +88,18 @@ <a id="label-deployment-byoc-setup-runtime-role"></a> -#### Snowflake role--A Snowflake role is a Snowflake role that is associated with a specific Openflow runtime and used for the following tasks:+#### Execute-as role++An execute-as role is a Snowflake role associated with a specific Openflow runtime and used for the following tasks:  - Grant access to Snowflake resources. - Grant access to connector-specific resources. -Snowflake roles are linked to Openflow Snowflake Managed Token, avoiding the need for customers to create separate service users and key pairs for authentication to Snowflake.+Execute-as roles are linked to Openflow Snowflake Managed Token, avoiding the need for customers to create separate service users and key pairs for authentication to Snowflake.  &lt;RUNTIMENAME&gt; denotes the name of the associated runtime. -To create a Snowflake role:--1. Create the required Snowflake role.+To create an execute-as role:++1. Create the required execute-as role.    ```sql    USE ROLE ACCOUNTADMIN;@@ -107,12 +107,12 @@    ``` -2. Grant the Snowflake role access to a warehouse.+2. Grant the execute-as role access to a warehouse.    Snowflake recommends using a dedicated warehouse for data ingestion.-   This warehouse should be used when configuring your connectors for runtimes where you will be using this Snowflake role.+   This warehouse should be used when configuring your connectors for runtimes where you will be using this execute-as role.    ```sql    GRANT USAGE, OPERATE ON WAREHOUSE <OPENFLOW_INGEST_WAREHOUSE> TO ROLE OPENFLOW_RUNTIME_ROLE_;    ``` -3. Allow the Snowflake role to use, create or otherwise access Snowflake objects.+3. Allow the execute-as role to use, create or otherwise access Snowflake objects.     <blockquote>@@ -130,5 +130,5 @@    ``` -4. Allow the user to use the Snowflake role+4. Allow the user to use the execute-as role    ```sql    GRANT ROLE OPENFLOW_RUNTIME_ROLE_ TO USER <username>; 

--- ahttps://docs.snowflake.com/en/user-guide/cortex-code/cortex-code-desktop/onboarding-and-authentication+++ bhttps://docs.snowflake.com/en/user-guide/cortex-code/cortex-code-desktop/onboarding-and-authentication@@ -211,14 +211,15 @@ ### Common fields -| Field                               | Description                                                                               |-| ----------------------------------- | ----------------------------------------------------------------------------------------- |-| `account`                           | Account identifier (`orgname-accountname`). Required.                                     |-| `user`                              | Your Snowflake username. Required.                                                        |-| `authenticator`                     | Sign-in method (for example, `oauth_authorization_code`, `externalbrowser`, `snowflake`). |-| `warehouse`                         | Default warehouse for queries.                                                            |-| `role`                              | Default role.                                                                             |-| `database`                          | Default database.                                                                         |-| `schema`                            | Default schema.                                                                           |-| `client_store_temporary_credential` | Cache OAuth/SSO tokens so you don't have to sign in again on each launch.                 |+| Field                               | Description                                                                                                                                                                                                                |+| ----------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |+| `account`                           | Account identifier (`orgname-accountname`). Required.                                                                                                                                                                      |+| `host`                              | Snowflake host URL override. Use this for PrivateLink connections or government regions where the account identifier alone can't resolve the endpoint (for example, `myorg-myaccount.privatelink.snowflakecomputing.com`). |+| `user`                              | Your Snowflake username. Required.                                                                                                                                                                                         |+| `authenticator`                     | Sign-in method (for example, `oauth_authorization_code`, `externalbrowser`, `snowflake`).                                                                                                                                  |+| `warehouse`                         | Default warehouse for queries.                                                                                                                                                                                             |+| `role`                              | Default role.                                                                                                                                                                                                              |+| `database`                          | Default database.                                                                                                                                                                                                          |+| `schema`                            | Default schema.                                                                                                                                                                                                            |+| `client_store_temporary_credential` | Cache OAuth/SSO tokens so you don't re-sign-in each launch.                                                                                                                                                                |  ## Credential security 

--- ahttps://docs.snowflake.com/en/collaboration/provider-becoming+++ bhttps://docs.snowflake.com/en/collaboration/provider-becoming@@ -210,16 +210,12 @@ ### Set up Stripe to get paid for listings -Stripe is used to send payments to providers for Snowflake Marketplace purchases.-As defined in the [Provider and Consumer Terms](https://www.snowflake.com/legal/snowflake-provider-and-consumer-terms/),-providers appoint Snowflake as their agent for receiving consumer payments.--To receive payments for your listings, you must set up a Stripe Express account associated with Snowflake.--[Stripe](https://stripe.com/) is the online payment processing system used by Snowflake to process payments from consumers who purchase-your paid listings. Payments collected from consumers are disbursed to your Stripe account for %sf-marketplace% following Stripe-receiving payment from the consumer.--When you set up a Stripe Express account, you need to provide information about your business so that Stripe can verify your business details.-The person that sets up the Stripe account must also set up multi-factor authentication to set up and manage the Stripe account.+%sf-marketplace% uses Stripe to process Provider payouts. To receive payouts, Providers must create a Stripe Express+connected account as their payout method through %sf-marketplace%. If eligible, Providers can reuse verified business information+from an existing Stripe account instead of completing verification again. To do so, the email address associated with your+Snowflake user must match your Stripe sign-in email, and you must be an Administrator or Super Administrator of the existing Stripe account.++There is no additional cost to Providers for using the Stripe connected account. As part of the setup process,+Providers must accept the [Stripe Connected Account Agreement](https://stripe.com/legal/connect-account).+This agreement is between the Provider and Stripe; Snowflake is not a party to it.  1. Sign in to %sf-web-interface-link%. 

--- ahttps://docs.snowflake.com/en/sql-reference/data-sharing-usage/listing-events-daily+++ bhttps://docs.snowflake.com/en/sql-reference/data-sharing-usage/listing-events-daily@@ -160,7 +160,19 @@     </tr>     <tr>-      <td>CONSUMER_MCD_OPT_IN_DATE</td>-      <td>TIMESTAMP_LTZ</td>-      <td>The date and time when the consumer account enrolled into the MCD program. If the consumer account isn't enrolled in the MCD program, the value is NULL.</td>+      <td>CONSUMER_MCD_OPT_IN_RANGE</td>+      <td>VARCHAR</td>+      <td>++The number of days since the consumer account enrolled in the Marketplace Capacity Drawdown (MCD) program, expressed as a range. One of:++- `< 30 days`+- `30-60 days`+- `60-90 days`+- `90-120 days`+- `> 120 days`++The upper bound of each range is exclusive. If the consumer account isn't enrolled in the MCD program, the value is NULL.++</td>     </tr>   </tbody> 

--- ahttps://docs.snowflake.com/en/developer-guide/streamlit/limitations+++ bhttps://docs.snowflake.com/en/developer-guide/streamlit/limitations@@ -57,5 +57,5 @@     </tr>     <tr>-      <td>[Package-based v2 components](#label-streamlit-custom-components)</td>+      <td>[Custom Components v2](#label-streamlit-custom-components)</td>       <td>Not supported</td>       <td>Supported</td>@@ -142,12 +142,11 @@  As a consequence of the CSP, custom components can't load scripts from external domains-in warehouse and container runtimes. Because package-based components use an asset directory-to serve their static content, the following differences apply:--- In warehouse runtimes, package-based v2 components that utilize an asset directory aren't supported.-- In container runtimes, package-based v2 components are fully supported.--To use a v2 custom component in a warehouse runtime, it must be defined with inline HTML, CSS,-and JavaScript.+in warehouse and container runtimes.++- In warehouse runtimes, Components v2 (`st.components.v2.component`) isn't supported.+- In container runtimes, Components v2 is fully supported, including package-based components that+  use an asset directory.++Components v1 (`st.components.v1.html`, `st.components.v1.iframe`) is supported in both runtimes.  Components imported from a third-party source are subject to the license attached to that component. You are responsible 

--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/about-spcs+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/about-spcs@@ -26,16 +26,16 @@ - Employing reverse ETL: Closing the loop on insight generation by sharing with external operational systems via APIs, messaging infrastructure, and more. -## Understanding Snowflake roles and External Access Integrations+## Understanding execute-as roles and External Access Integrations  %ofsfspcs-plural% must be able to interact with data sources and destinations that are typically outside Snowflake. In addition these deployments must also be able to communicate with and access Snowflake itself.-Snowflake roles and external access integrations provide this support.+Execute-as roles and external access integrations provide this support.  <a id="label-openflow-spcs-what-is-runtime-role"></a> -### What is a Snowflake role?+### What is an execute-as role? -A Snowflake role is a traditional Snowflake role, associated with a specific Openflow Runtime, and used for the following tasks:+An execute-as role is a Snowflake role associated with a specific Openflow runtime, used for the following tasks:  - Grant access to external access integrations (EAIs).@@ -45,5 +45,5 @@ - Grant access to resources that are connector-specific -Snowflake roles are linked to Openflow session tokens, avoiding the need for customers+Execute-as roles are linked to Openflow session tokens, avoiding the need for customers to create separate service users and key pairs for authentication to Snowflake. @@ -56,5 +56,5 @@ endpoints an Openflow connector can read from or write to. -Data engineers define and configure EAIs and Snowflake roles specific to a given connector and its underlying runtime.+Data engineers define and configure EAIs and execute-as roles specific to a given connector and its underlying runtime.  ## Typical %ofsfspcs% workflow@@ -98,5 +98,5 @@ - Works with a Snowflake administrator to configure required allow listed domains such   that %ofsfspcs% can access the external data sources.-- Creates Snowflake roles, external integrations, and other objects that can later be used by runtimes.+- Creates execute-as roles, external integrations, and other objects that can later be used by runtimes. - Uses the runtime canvas to build completely new flows or to configure deployed connectors.   Creates a completely new flow or uses an existing connector as-is or as a starting point to customize.@@ -133,5 +133,5 @@ - The **control plane** is the layer you use to create, upgrade, and observe deployments and runtimes through the Openflow UI or APIs. On %ofsfspcs-plural%, Snowflake operates the control plane. - A **deployment** is the data plane container for your runtimes. Each deployment is backed by a [compute pool](/developer-guide/snowpark-container-services/working-with-compute-pool). An account can have multiple %ofsfspcs-plural% to separate workloads by project, team, or environment. See [Create deployment](/user-guide/data-integration/openflow/setup-openflow-spcs-deployment).-- A **runtime** hosts your data flows within a deployment. Each deployment can host multiple runtimes, and each runtime has its own Snowflake role and network access configuration. See [Create runtime](/user-guide/data-integration/openflow/setup-openflow-spcs-create-runtime).+- A **runtime** hosts your data flows within a deployment. Each deployment can host multiple runtimes, and each runtime has its own execute-as role and network access configuration. See [Create runtime](/user-guide/data-integration/openflow/setup-openflow-spcs-create-runtime).  For definitions of all Openflow components, see [Openflow components](/user-guide/data-integration/openflow/about#label-openflow-components). 

--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/mysql/iceberg+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/mysql/iceberg@@ -225,12 +225,12 @@       <td>TINYINT / SMALLINT / MEDIUMINT (signed or unsigned)</td>       <td>INT</td>-      <td>`int`</td>-      <td>`int`</td>+      <td>`long`</td>+      <td>`long`</td>     </tr>     <tr>       <td>INT (signed)</td>       <td>INT</td>-      <td>`int`</td>-      <td>`int`</td>+      <td>`long`</td>+      <td>`long`</td>     </tr>     <tr>@@ -255,6 +255,6 @@       <td>YEAR</td>       <td>INT</td>-      <td>`int`</td>-      <td>`int`</td>+      <td>`long`</td>+      <td>`long`</td>     </tr>     <tr>@@ -285,6 +285,6 @@       <td>BOOLEAN / BOOL</td>       <td>INT</td>-      <td>`int`</td>-      <td>`int`</td>+      <td>`long`</td>+      <td>`long`</td>     </tr>     <tr> 

--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-cli/sql/execute-sql+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-cli/sql/execute-sql@@ -16,8 +16,8 @@   ``` -The `snow sql` command also can execute multiple statements; in that case, multiple result sets are returned. For example, running:--```snowcli-snow sql  -q "select 'a', 'b'; select 'c', 'd';"+The `snow sql` command can also execute multiple statements; in that case, multiple result sets are returned. For example, running:++```snowcli+snow sql -q "select 'a', 'b'; select 'c', 'd';" ``` @@ -429,10 +429,10 @@       <td>start_date (string)</td>       <td>None</td>-      <td>Return only queries executed after the specified date. Date is expected to be provided in ISO format (for example `2025-01-01T09:00:00`)</td>+      <td>Return only queries executed after the specified date. Date is expected to be provided in ISO format (for example `2025-01-01T09:00:00`).</td>     </tr>     <tr>       <td>end_date (string)</td>       <td>None</td>-      <td>Return only queries executed before the specified date. Date is expected to be provided in ISO format (for example `2025-01-01T09:00:00`)</td>+      <td>Return only queries executed before the specified date. Date is expected to be provided in ISO format (for example `2025-01-01T09:00:00`).</td>     </tr>     <tr>@@ -592,5 +592,5 @@    ``` -6. To execute the commands, select `ENTER`.+6. To execute the commands, press `ENTER`.     The command output is displayed, as shown: 

--- ahttps://docs.snowflake.com/en/release-notes/2026/10_30+++ bhttps://docs.snowflake.com/en/release-notes/2026/10_30@@ -11,13 +11,8 @@ <a id="about-listing-consumers"></a> -# 10.30 Release Notes (no announcements) (Preview)+# 10.30 Release Notes (no announcements): Aug 22, 2026 - Aug 25, 2026 -Content on this page is available in advance of the completion of the 10.30 release, which is currently-either *pending* or *in progress* and is scheduled for completion on Aug 25, 2026 (subject to change).--Features, updates, or behavior changes described on this page might not be available in your accounts-until the release is complete.--For updates to these release notes, see [](#label-rel-notes-change-log-10-30).+This release has completed. For differences between the in-advance and final versions of these release+notes, see [](#label-rel-notes-change-log-10-30).  This release contains no significant features, updates, or enhancements to announce.@@ -33,4 +28,5 @@ | Release notes    | Initial publication (preview)                                | Aug 20, 2026 | | PERIOD data type | **Removed** — feature not enabled in 10.30; will be in 10.31 | Aug 24, 2026 |+| Release notes    | Final publication                                            | Aug 26, 2026 |  </div> 

--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/aisql-regional-availability+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/aisql-regional-availability@@ -1181,7 +1181,7 @@       <td>`llama3.3-70b`</td>       <td>%cm%</td>-      <td>%cm%</td>-      <td></td>-      <td>%cm%</td>+      <td></td>+      <td></td>+      <td></td>       <td></td>       <td></td>@@ -1577,5 +1577,5 @@ | \| `llama3.1-8b`                      | %cm%                             | %cm%                        | %cm%                            | | \| `llama3.1-70b`                     | %cm%                             | %cm%                        | %cm%                            |-| \| `llama3.3-70b`                     | %cm%                             | %cm%                        | %cm%                            |+| \| `llama3.3-70b`                     |                                  |                             |                                 | | \| `openai-gpt-4.1`                   |                                  |                             |                                 | | \| `mistral-large2`                   | %cm%                             | %cm%                        | %cm%                            |@@ -1656,6 +1656,6 @@     <tr>       <td>`llama3.3-70b`</td>-      <td>%cm%</td>-      <td>%cm%</td>+      <td></td>+      <td></td>     </tr>     <tr> 

--- ahttps://docs.snowflake.com/en/user-guide/security-access-control-privileges+++ bhttps://docs.snowflake.com/en/user-guide/security-access-control-privileges@@ -714,5 +714,15 @@     <tr>       <td>CREATE INTEGRATION</td>-      <td>Enables creating a new catalog, notification, security, or storage integration.</td>+      <td>Enables creating an integration of any type. To let a role create only one type of integration, grant the corresponding granular privilege instead, such as CREATE NOTIFICATION INTEGRATION or CREATE STORAGE INTEGRATION.</td>+      <td>Must be granted by the ACCOUNTADMIN role.</td>+    </tr>+    <tr>+      <td>CREATE NOTIFICATION INTEGRATION</td>+      <td>Enables creating a new notification integration. This privilege does not grant the ability to create other types of integrations.</td>+      <td>Must be granted by the ACCOUNTADMIN role.</td>+    </tr>+    <tr>+      <td>CREATE STORAGE INTEGRATION</td>+      <td>Enables creating a new storage integration. This privilege does not grant the ability to create other types of integrations.</td>       <td>Must be granted by the ACCOUNTADMIN role.</td>     </tr> 

--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/sql-server-cdc/about+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/sql-server-cdc/about@@ -98,6 +98,5 @@       capture instance for each table to be replicated using `sys.sp_cdc_enable_table`.    2. Creates credentials for the connector.-   3. Deploys the Openflow CDC wrapper procedures so the connector can manage capture-      instances and apply source schema changes autonomously.+   3. Deploys the Openflow CDC wrapper procedures so the connector can rotate capture instances during supported schema changes. If permissions or internal policy blocks deployment, see [When the wrapper procedures aren't deployed](#label-sql-server-cdc-wrapper-procedures-missing).    4. (Optional) Provides the SSL certificate to connect to the SQL Server instance over SSL. @@ -275,4 +274,12 @@ - **Incompatible type change.** When the new source type maps to a different Snowflake data type (for example, `INT` to `VARCHAR`, mapped to `NUMBER` and `TEXT` respectively). - **Rename column.** SQL Server doesn't allow renaming a column that belongs to an active CDC capture instance. This is a source-side restriction that SQL Server enforces itself, not a limitation of the connector: the rename statement fails on the source database before any change reaches the connector.++<a id="label-sql-server-cdc-wrapper-procedures-missing"></a>++#### When the wrapper procedures aren't deployed++The connector expects `dbo.sf_openflow_cdc_enable_table` and `dbo.sf_openflow_cdc_disable_table` from [Deploy the Openflow CDC wrapper procedures](/user-guide/data-integration/openflow/connectors/sql-server-cdc/setup#label-sql-server-cdc-wrapper-procedures). Only use replication without them when permissions or internal policy blocks deployment. Treat that as a last resort, not the normal path. Replication still works until a supported schema change occurs; then a DBA must run manual capture-instance SQL for that change.++Look for a WARN bulletin on the **MultiDatabaseCaptureChangeCdcSqlServer** processor whose message starts with `Schema-change replication` (Openflow bulletins or runtime logs). The bulletin includes the SQL to run. Use that script to unblock the table, or deploy the procedures and grants from [Deploy the Openflow CDC wrapper procedures](/user-guide/data-integration/openflow/connectors/sql-server-cdc/setup#label-sql-server-cdc-wrapper-procedures) so later schema changes don't need manual steps. After the fix, the connector continues on the next run without restarting the flow or re-adding the table.  #### How the schema transition works 

--- ahttps://docs.snowflake.com/en/collaboration/provider-transactions-invoicing-collections+++ bhttps://docs.snowflake.com/en/collaboration/provider-transactions-invoicing-collections@@ -75,10 +75,11 @@ ## Payouts, Net Terms and fees -**Stripe** is the payment processor for %sf-marketplace% payouts. To receive payouts, Providers must set up their-payout method through %sf-marketplace%. During setup, Providers may either create a new-Stripe Connect account or connect an existing Stripe account. There are no-additional costs to Providers for using the Snowflake Stripe Connect account. As part of the setup process,+**%sf-marketplace% uses Stripe to process Provider payouts.** To receive payouts, Providers must create a Stripe Express+connected account as their payout method through %sf-marketplace%. If eligible, Providers can reuse verified information+from an existing Stripe account instead of completing verification again.++There is no additional cost to Providers for using the Stripe connected account. As part of the setup process, Providers must accept the [Stripe Connected Account Agreement](https://stripe.com/legal/connect-account).-Those terms are between the Provider and Stripe, and Snowflake is not a party to that agreement.+This agreement is between the Provider and Stripe; Snowflake is not a party to it.  **Net terms,** the amount of time a customer has to pay an invoice, are determined by the Provider and should be 

--- ahttps://docs.snowflake.com/en/user-guide/cleanrooms/spec-code-spec+++ bhttps://docs.snowflake.com/en/user-guide/cleanrooms/spec-code-spec@@ -333,8 +333,9 @@  The ML runtime image version to use. Maximum 64 characters. If omitted, the collaboration uses the-current default image version (currently `2.8.1`). The default may change across Snowflake Data Clean Rooms API releases.+latest available runtime image, resolved when the code spec is added to a collaboration.+The default image is updated when new+runtime versions are released. Pinning `image_tag` to a specific version is recommended so that your code spec runs against a-known set of pre-installed libraries and runtime behavior, and isn't affected when the default-image is updated.+known set of pre-installed libraries and runtime behavior.  All pinned versions are preserved unchanged across patches.@@ -356,5 +357,5 @@     entrypoint: train.py     stage_code_dir: '@MY_DB.PUBLIC.MY_STAGE/ml_project'-    image_tag: "2.8.1"+    image_tag: "2.9.0"     pip_requirements:       - pandas@@ -364,5 +365,5 @@     entrypoint: score.py     stage_code_dir: '@MY_DB.PUBLIC.MY_STAGE/ml_project'-    image_tag: "2.8.1"+    image_tag: "2.9.0"     pip_requirements:       - pandas 

--- ahttps://docs.snowflake.com/en/user-guide/cortex-code/cortex-code-snowsight/skills-and-plugins+++ bhttps://docs.snowflake.com/en/user-guide/cortex-code/cortex-code-snowsight/skills-and-plugins@@ -2,4 +2,14 @@  Skills extend CoCo with specialized capabilities that can be invoked by typing `/` in the message box.++## Requirements++To use skills and plugins in CoCo on Snowsight, you need:++- An active warehouse in your session. Skills execute queries and AI functions on your behalf,+  so your current warehouse handles the compute. Any warehouse size works for most skills.++- To manage skills in the Horizon Catalog (share, change access, delete), you need the+  ACCOUNTADMIN role or a role with equivalent privileges on the Catalog.  ## Built-in skills 

--- ahttps://docs.snowflake.com/en/user-guide/oauth-partner+++ bhttps://docs.snowflake.com/en/user-guide/oauth-partner@@ -76,4 +76,5 @@ oauthClientParams ::=   [ OAUTH_ISSUE_REFRESH_TOKENS = TRUE | FALSE ]+  [ OAUTH_ACCESS_TOKEN_VALIDITY = <integer> ]   [ OAUTH_REFRESH_TOKEN_VALIDITY = <integer> ]   [ BLOCKED_ROLES_LIST = ('<role_name>', '<role_name>') ]@@ -139,4 +140,13 @@ your account. +### Controlling access token validity++The optional `OAUTH_ACCESS_TOKEN_VALIDITY` parameter specifies how long an access token is valid (in seconds). Access tokens are+short-lived. The default is 600 seconds (10 minutes). You can set the value anywhere between 60 seconds (1 minute) and 3600 seconds+(1 hour).++When an access token expires, the partner application can use a refresh token to request a new access token without prompting the user to+log in again, as long as the refresh token is still valid.+ ### Using Client Redirect with Snowflake OAuth for partner applications  

--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-cli/connecting/configure-cli+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-cli/connecting/configure-cli@@ -47,7 +47,7 @@  By default %sf-cli% looks for the `config.toml` file in the `~/.snowflake` directory or, in case this directory does not exist, in a system-specific location, as listed below.-You can also specify which configuration file should be used using `--config-file` flag or `SNOWFLAKE_HOME` environment variable.--- If you specify the `--config-file` option (such as, `snow --config-file ./my-config-file-path`), %sf-cli% uses the specified configuration file.+You can also specify which configuration file should be used with the `--config-file` flag or `SNOWFLAKE_HOME` environment variable.++- If you specify the `--config-file` option (such as `snow --config-file ./my-config-file-path`), %sf-cli% uses the specified configuration file. - If the `SNOWFLAKE_HOME` environment variable is set, %sf-cli% uses the location specified by this variable. - If a `~/.snowflake` directory exists on your machine, %sf-cli% uses the `~/.snowflake/config.toml` file.@@ -332,5 +332,5 @@ Windows PowerShell has encoding settings of its own that %sf-cli% configuration doesn't reach. `[Console]::OutputEncoding` controls what the console passes to and from native executables, `$OutputEncoding` controls what PowerShell sends through-the pipeline, and `$PSDefaultParameterValues['Out-File:Encoding']` controls which text encoding `Out-File` and the `>` operator use to write its output to disk.+the pipeline, and `$PSDefaultParameterValues['Out-File:Encoding']` controls which text encoding `Out-File` and the `>` operator use to write their output to disk. If any of these is left on a legacy code page, non-ASCII characters are silently corrupted even when %sf-cli% emits UTF-8. This issue can occur in the following scenarios:@@ -340,5 +340,5 @@ - Passing the output of a %sf-cli% command to another native command using the `|` operator. -To prevent these issues, apart from applying one of the three options described earlier you need to force PowerShell to use UTF-8+To prevent these issues, apart from applying one of the three options described earlier, you need to force PowerShell to use UTF-8 by adding the following to your PowerShell session or profile (`$PROFILE`):  

--- ahttps://docs.snowflake.com/en/developer-guide/native-apps/ui-consumer-enable-logging+++ bhttps://docs.snowflake.com/en/developer-guide/native-apps/ui-consumer-enable-logging@@ -58,5 +58,5 @@   event definitions emitted by an app, a consumer should create an event table and set it as   the active event table for their account.-- Optional event definitions can be enabled or disable by the consumer as necessary. Optional event+- Optional event definitions can be enabled or disabled by the consumer as necessary. Optional event   definitions require an active event table, but they are not required to install or use the app. @@ -131,8 +131,8 @@   your account. - After you [enable event sharing](#label-nativeapps-consumer-logging-enabling), a masked and redacted-  copy of the trace events and logs messages is automatically inserted in the event table of the designated+  copy of the trace events and log messages is automatically inserted in the event table of the designated   provider account. - Snowflake does not charge you to enable event sharing. However, you are responsible for the-  cost of ingesting trace events and log message in the event table as well as storage+  cost of ingesting trace events and log messages in the event table as well as storage   costs for the event table. - After enabling event sharing with a provider, you cannot revoke access to shared@@ -371,5 +371,5 @@ ## View the log and trace levels for an app -The log and trace level of an app are defined by the provider before publishing an app.+The log and trace levels of an app are defined by the provider before publishing an app. Consumers cannot change the log and trace levels for an app. @@ -399,5 +399,5 @@ definition, the app dynamically changes log level to WARN so that ERROR_AND_WARNING events can be collected. The app emits events that are less or equally as verbose as WARN and shares those error and warning events with the provider.-The values of `log_level` would be OFF and the value of `effective_log_level` would be WARN.+The value of `log_level` would be OFF and the value of `effective_log_level` would be WARN.  In contrast, if the provider defines the log level as TRACE, but the consumer enables the ERROR_AND_WARNING 

--- ahttps://docs.snowflake.com/en/user-guide/oauth-custom+++ bhttps://docs.snowflake.com/en/user-guide/oauth-custom@@ -156,4 +156,14 @@  Snowflake supports network policies for OAuth. For more information, see [](#label-snow-oauth-network-policies).++### Controlling access token validity++The optional `OAUTH_ACCESS_TOKEN_VALIDITY` parameter specifies how long an access token is valid (in seconds). Access tokens are+short-lived. The default is 600 seconds (10 minutes). You can set the value anywhere between 60 seconds (1 minute) and 3600 seconds+(1 hour).++When an access token expires, the client can use a refresh token to request a new access token without prompting the user to log in+again, as long as the refresh token is still valid. For the full parameter description, see+[CREATE SECURITY INTEGRATION (Snowflake OAuth)](/sql-reference/sql/create-security-integration-oauth-snowflake).  ### Integration example 

--- ahttps://docs.snowflake.com/en/sql-reference/sql/create-storage-integration-postgres-internal+++ bhttps://docs.snowflake.com/en/sql-reference/sql/create-storage-integration-postgres-internal@@ -110,8 +110,9 @@ <div className="colwidths-auto"> -| Privilege          | Object            | Notes                                                               |-| ------------------ | ----------------- | ------------------------------------------------------------------- |-| CREATE INTEGRATION | Account           | %ac-accountadmin%                                                   |-| OWNERSHIP          | Postgres instance | Required on the Postgres instance specified by `POSTGRES_INSTANCE`. |+| Privilege                  | Object            | Notes                                                                                                                               |+| -------------------------- | ----------------- | ----------------------------------------------------------------------------------------------------------------------------------- |+| CREATE INTEGRATION         | Account           | %ac-accountadmin%                                                                                                                   |+| OWNERSHIP                  | Postgres instance | Required on the Postgres instance specified by `POSTGRES_INSTANCE`.                                                                 |+| CREATE STORAGE INTEGRATION | Account           | Grants the ability to create storage integrations. This privilege does not grant the ability to create other types of integrations. |  </div> 

--- ahttps://docs.snowflake.com/en/sql-reference/sql/create-notification-integration-webhooks+++ bhttps://docs.snowflake.com/en/sql-reference/sql/create-notification-integration-webhooks@@ -230,8 +230,9 @@ <div className="colwidths-auto"> -| Privilege          | Object  | Notes                                                                                                                                                              |-| ------------------ | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |-| CREATE INTEGRATION | Account | %ac-accountadmin%                                                                                                                                                  |-| USAGE              | Secret  | If you set the WEBHOOK_SECRET property to a secret object, you must have the USAGE privilege on that secret and on the database and schema containing that secret. |+| Privilege                       | Object  | Notes                                                                                                                                                              |+| ------------------------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |+| CREATE INTEGRATION              | Account | %ac-accountadmin%                                                                                                                                                  |+| USAGE                           | Secret  | If you set the WEBHOOK_SECRET property to a secret object, you must have the USAGE privilege on that secret and on the database and schema containing that secret. |+| CREATE NOTIFICATION INTEGRATION | Account | Grants the ability to create notification integrations. This privilege does not grant the ability to create other types of integrations.                           |  </div> 

--- ahttps://docs.snowflake.com/en/developer-guide/restricted-callers-rights+++ bhttps://docs.snowflake.com/en/developer-guide/restricted-callers-rights@@ -1,4 +1,5 @@ # Restricted caller's rights +- [](/developer-guide/restricted-callers-rights/high-level-caller-privileges) - [](/developer-guide/stored-procedure/stored-procedures-rights) - [](/developer-guide/streamlit/features/restricted-callers-rights)@@ -28,4 +29,8 @@ such as tables and warehouses that the executable accesses. When the executable attempts to access the objects, the caller grants associated with the owner of the executable are used to determine which of the caller's privileges can be used for the operation.++Some operations require a [high-level caller privilege](/developer-guide/restricted-callers-rights/high-level-caller-privileges)+in addition to the corresponding fine-grained caller grants. For details, see+[Operations and the required high-level caller privilege](/developer-guide/restricted-callers-rights/high-level-caller-privileges#operations-and-the-required-high-level-caller-privilege).  ## Executables that run with restricted caller's rights@@ -53,8 +58,4 @@ For more information, see [](/developer-guide/streamlit/features/restricted-callers-rights). -Some operations require a [high-level caller privilege](/developer-guide/restricted-callers-rights/high-level-caller-privileges)-in addition to the corresponding fine-grained caller grants. For details, see-[Operations and the required high-level caller privilege](/developer-guide/restricted-callers-rights/high-level-caller-privileges#operations-and-the-required-high-level-caller-privilege).- ## Grant caller grants  

--- ahttps://docs.snowflake.com/en/user-guide/cortex-code/cli-reference+++ bhttps://docs.snowflake.com/en/user-guide/cortex-code/cli-reference@@ -37,9 +37,15 @@ | `--mode <standard\|code>`                        | Agent tool mode; `code` uses a lean coding tool set (see [Code mode](/user-guide/cortex-code/code-mode)) | | `--plan`                                         | Plan mode: require approval before all actions                                                           |+| `--auto-accept-plans`                            | Auto-accept plan mode requests and confirmations without prompting                                       | | `--bypass`, `--dangerously-allow-all-tool-calls` | Enable bypass mode, automatically approving all tool calls                                               |+| `--allowed-tools <tools>`                        | Tools that execute without prompting for permission (for example, `"Bash(git *)"`)                       |+| `--disallowed-tools <tools>`                     | Tools that are removed from the model's context and can't be used                                        | | `--continue`                                     | Resume most recent conversation                                                                          | | `-r, --resume [<session_id>]`                    | Resume specific session by ID, or `last` for the most recent session                                     | | `-p, --print "<prompt>"`                         | Pass specified prompt, print response, and exit                                                          | | `--output-format stream-json`                    | JSON output (for scripting)                                                                              |+| `--effort <level>`                               | Thinking effort level: `minimal`, `low`, `medium`, `high`, or `max`                                      |+| `--max-turns <n>`                                | Maximum number of agentic turns per conversation round                                                   |+| `--private`                                      | Don't save this session to history (disables conversation persistence and server-side logging)           | | `--cloud [<workspace>]`                          | Run tools in a Snowflake-managed container                                                               | | `--no-workspace`                                 | With `--cloud`, use an ephemeral workspace                                                               |@@ -51,5 +57,6 @@  `--bypass` and `--dangerously-allow-all-tool-calls` are aliases of the same option. Omit the value of `-r, --resume` to open the-resume picker instead of naming a session.+resume picker instead of naming a session. Use `--allowed-tools` to pre-approve specific tools (for example, `"Bash(git *)"` to+approve all git commands); use `--disallowed-tools` to prevent specific tools from being offered to the model at all.  Bypass mode approves every tool call without prompting you first. Use it only when you trust every action the agent might take. 

--- ahttps://docs.snowflake.com/en/user-guide/snowflake-postgres/postgres-create-instance+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-postgres/postgres-create-instance@@ -66,5 +66,5 @@   COMPUTE_FAMILY = '<compute_family>'   STORAGE_SIZE_GB = <storage_gb>-  AUTHENTICATION_AUTHORITY = POSTGRES+  AUTHENTICATION_AUTHORITY = { POSTGRES | POSTGRES_OR_SNOWFLAKE }   [ POSTGRES_VERSION = { 16 | 17 | 18 } ]   [ NETWORK_POLICY = '<network_policy>' ]@@ -91,9 +91,10 @@  </dd>-<dt>`AUTHENTICATION_AUTHORITY = POSTGRES`</dt>+<dt>`AUTHENTICATION_AUTHORITY = { POSTGRES | POSTGRES_OR_SNOWFLAKE }`</dt> <dd> -Determines how you authenticate to your instance. Currently, the only available option is `POSTGRES`, but other-authentication methods, including `SNOWFLAKE`, might be supported in the future.+Specifies the authentication method for the instance. POSTGRES indicates that only Postgres user passwords can be used.+POSTGRES_OR_SNOWFLAKE also allows the use of short-lived access token passwords. See+[](/user-guide/snowflake-postgres/postgres-token-auth) for more details.  </dd> 

--- ahttps://docs.snowflake.com/en/user-guide/cortex-code/credit-usage-limit+++ bhttps://docs.snowflake.com/en/user-guide/cortex-code/credit-usage-limit@@ -257,5 +257,5 @@ EXECUTE IMMEDIATE $$ DECLARE-  current_user STRING;+  target_user STRING;   rs_users RESULTSET;   res      RESULTSET;@@ -267,11 +267,11 @@    FOR record IN rs_users DO-    current_user := record."name";+    target_user := record."name";      EXECUTE IMMEDIATE-      'SHOW PARAMETERS LIKE ''CORTEX_CODE_CLI_DAILY_EST_CREDIT_LIMIT_PER_USER'' IN USER "' || :current_user || '"';+      'SHOW PARAMETERS LIKE ''CORTEX_CODE_CLI_DAILY_EST_CREDIT_LIMIT_PER_USER'' IN USER "' || :target_user || '"';      INSERT INTO _param_overrides (user_name, param_value)-      SELECT :current_user, "value"+      SELECT :target_user, "value"       FROM TABLE(RESULT_SCAN(LAST_QUERY_ID()))       WHERE "level" = 'USER'; 

--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-cli/connecting/configure-connections+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-cli/connecting/configure-connections@@ -15,5 +15,5 @@ You can also use the `--temporary-connection` option, which does not require defining it in `config.toml`. -For improved security, Snowflake strongly recommends using either `SNOWFLAKE_CONNECTIONS__PASSWORD` or `SNOWFLAKE_PASSWORD` environment variable.+For improved security, Snowflake strongly recommends using either `SNOWFLAKE_CONNECTIONS__PASSWORD` or `SNOWFLAKE_PASSWORD` environment variables.  <a id="label-snowcli-define-connections"></a>@@ -175,5 +175,5 @@ - `--diag-allowlist-path` to specify the absolute path to a JSON file containing the output of the SYSTEM$ALLOWLIST() or SYSTEM$ALLOWLIST_PRIVATELINK() SQL commands. This option is required only if the user defined in the connection does not have permission to run the system allowlist functions or if connecting to the account URL fails. -The following example generates a diagnostic report for the `myconnection2` connection and stores in the `~/report/SnowflakeConnectionTestReport.txt` file:+The following example generates a diagnostic report for the `myconnection2` connection and stores it in the `~/report/SnowflakeConnectionTestReport.txt` file:  ```snowcli@@ -307,5 +307,5 @@ ``` -For improved security, Snowflake strongly recommends using either `SNOWFLAKE_CONNECTIONS__PASSWORD` or `SNOWFLAKE_PASSWORD` environment variable.+For improved security, Snowflake strongly recommends using either `SNOWFLAKE_CONNECTIONS__PASSWORD` or `SNOWFLAKE_PASSWORD` environment variables.  <a id="label-snowcli-import-connections-snowsql"></a>@@ -385,5 +385,5 @@ ``` -For improved security, Snowflake strongly recommends using either `SNOWFLAKE_CONNECTIONS__PASSWORD` or `SNOWFLAKE_PASSWORD` environment variable.+For improved security, Snowflake strongly recommends using either `SNOWFLAKE_CONNECTIONS__PASSWORD` or `SNOWFLAKE_PASSWORD` environment variables.  For additional security, you can use a [private key file](#label-snowcli-private-key) and store the path to your private key file in the `SNOWFLAKE_PRIVATE_KEY_FILE` environment variable, as shown: 

--- ahttps://docs.snowflake.com/en/developer-guide/native-apps/creating-setup-script+++ bhttps://docs.snowflake.com/en/developer-guide/native-apps/creating-setup-script@@ -49,5 +49,5 @@ - Creating Snowpark user-defined functions (UDFs) or procedures that use IMPORT to include files   on a named stage.-- Calling procedures, functions or anonymous code blocks that refer to code not included in the+- Calling procedures, functions, or anonymous code blocks that refer to code not included in the   application package. - Importing code files from a named stage when using the [](/sql-reference/sql/create-function)@@ -288,5 +288,5 @@ ## About application roles -By default the consumer has no privileges on objects created within the app. Even the ACCOUNTADMIN role+By default, the consumer has no privileges on objects created within the app. Even the ACCOUNTADMIN role cannot view the objects **within** an app. Objects that the app creates outside itself, such as a database, are visible only to the ACCOUNTADMIN role of the consumer account.@@ -296,5 +296,5 @@  Application roles should be created by the setup script when the app is installed and are automatically granted-to the app owner's role, who then can grant appropriate application roles to other roles in the consumer account.+to the app owner's role, which then can grant appropriate application roles to other roles in the consumer account.  Application roles are the only type of role that can be created within an app. Database@@ -345,5 +345,5 @@ GRANT USAGE ON SCHEMA app_code TO APPLICATION ROLE user; CREATE OR REPLACE PROCEDURE app_code.config_app(...)-GRANT USAGE ON PROCEDURE app_code.config_app(..)+GRANT USAGE ON PROCEDURE app_code.config_app(...)   TO APPLICATION ROLE admin;  

--- ahttps://docs.snowflake.com/en/user-guide/cortex-code/cortex-code-desktop/index+++ bhttps://docs.snowflake.com/en/user-guide/cortex-code/cortex-code-desktop/index@@ -10,5 +10,5 @@ - [Plugins in CoCo Desktop](/user-guide/cortex-code/cortex-code-desktop/plugins) -CoCo Desktop is a native Mac/Windows desktop application that brings CoCo's full+CoCo Desktop is a native macOS/Windows desktop application that brings CoCo's full agentic capabilities into an IDE-like surface: file editor, integrated terminal, agentic AI loop, agentic browser, agentic notebook, and deep Snowflake awareness.@@ -125,7 +125,7 @@ ## Monitoring and history -| Topic                                                                                                    | Description                         |-| -------------------------------------------------------------------------------------------------------- | ----------------------------------- |-| [Usage history view](/user-guide/cortex-code/cortex-code-desktop/cortex-code-desktop-usage-history-view) | Monitor usage and token consumption |+| Topic                                                                                | Description                         |+| ------------------------------------------------------------------------------------ | ----------------------------------- |+| [Usage history view](/sql-reference/account-usage/cortex_code_desktop_usage_history) | Monitor usage and token consumption |  ## Security 

--- ahttps://docs.snowflake.com/en/sql-reference/sql/create-storage-integration+++ bhttps://docs.snowflake.com/en/sql-reference/sql/create-storage-integration@@ -522,7 +522,8 @@ <div className="colwidths-auto"> -| Privilege          | Object  | Notes             |-| ------------------ | ------- | ----------------- |-| CREATE INTEGRATION | Account | %ac-accountadmin% |+| Privilege                  | Object  | Notes                                                                                                                               |+| -------------------------- | ------- | ----------------------------------------------------------------------------------------------------------------------------------- |+| CREATE INTEGRATION         | Account | %ac-accountadmin%                                                                                                                   |+| CREATE STORAGE INTEGRATION | Account | Grants the ability to create storage integrations. This privilege does not grant the ability to create other types of integrations. |  </div> 

--- ahttps://docs.snowflake.com/en/user-guide/cortex-code/cortex-code-desktop/dbt-integration+++ bhttps://docs.snowflake.com/en/user-guide/cortex-code/cortex-code-desktop/dbt-integration@@ -159,7 +159,8 @@ ### Project size limit -A dbt project synced to a Snowflake workspace can contain at most 20,000 files across all-folders, including generated `target/` and `dbt_packages/` artifacts. See-[Limitations, requirements, and considerations](/user-guide/data-engineering/dbt-projects-on-snowflake-using-workspaces#label-dbt-requirements-workspaces).+When you deploy a specific dbt project folder as a dbt+project object, that folder can contain at most 100,000 files across all folders, including+generated `target/` and `dbt_packages/` artifacts. See+[](/user-guide/data-engineering/dbt-projects-on-snowflake-limitations).  ### Inspecting your workspaces 

--- ahttps://docs.snowflake.com/en/sql-reference/sql/create-notification-integration-queue-outbound-azure+++ bhttps://docs.snowflake.com/en/sql-reference/sql/create-notification-integration-queue-outbound-azure@@ -128,7 +128,8 @@ <div className="colwidths-auto"> -| Privilege          | Object  | Notes             |-| ------------------ | ------- | ----------------- |-| CREATE INTEGRATION | Account | %ac-accountadmin% |+| Privilege                       | Object  | Notes                                                                                                                                    |+| ------------------------------- | ------- | ---------------------------------------------------------------------------------------------------------------------------------------- |+| CREATE INTEGRATION              | Account | %ac-accountadmin%                                                                                                                        |+| CREATE NOTIFICATION INTEGRATION | Account | Grants the ability to create notification integrations. This privilege does not grant the ability to create other types of integrations. |  </div> 

--- ahttps://docs.snowflake.com/en/sql-reference/sql/create-notification-integration-queue-outbound-aws+++ bhttps://docs.snowflake.com/en/sql-reference/sql/create-notification-integration-queue-outbound-aws@@ -129,7 +129,8 @@ <div className="colwidths-auto"> -| Privilege          | Object  | Notes             |-| ------------------ | ------- | ----------------- |-| CREATE INTEGRATION | Account | %ac-accountadmin% |+| Privilege                       | Object  | Notes                                                                                                                                    |+| ------------------------------- | ------- | ---------------------------------------------------------------------------------------------------------------------------------------- |+| CREATE INTEGRATION              | Account | %ac-accountadmin%                                                                                                                        |+| CREATE NOTIFICATION INTEGRATION | Account | Grants the ability to create notification integrations. This privilege does not grant the ability to create other types of integrations. |  </div> 

--- ahttps://docs.snowflake.com/en/sql-reference/sql/create-notification-integration-queue-outbound-gcp+++ bhttps://docs.snowflake.com/en/sql-reference/sql/create-notification-integration-queue-outbound-gcp@@ -120,7 +120,8 @@ <div className="colwidths-auto"> -| Privilege          | Object  | Notes             |-| ------------------ | ------- | ----------------- |-| CREATE INTEGRATION | Account | %ac-accountadmin% |+| Privilege                       | Object  | Notes                                                                                                                                    |+| ------------------------------- | ------- | ---------------------------------------------------------------------------------------------------------------------------------------- |+| CREATE INTEGRATION              | Account | %ac-accountadmin%                                                                                                                        |+| CREATE NOTIFICATION INTEGRATION | Account | Grants the ability to create notification integrations. This privilege does not grant the ability to create other types of integrations. |  </div> 

--- ahttps://docs.snowflake.com/en/sql-reference/sql/create-notification-integration-queue-inbound-azure+++ bhttps://docs.snowflake.com/en/sql-reference/sql/create-notification-integration-queue-inbound-azure@@ -133,7 +133,8 @@ <div className="colwidths-auto"> -| Privilege          | Object  | Notes             |-| ------------------ | ------- | ----------------- |-| CREATE INTEGRATION | Account | %ac-accountadmin% |+| Privilege                       | Object  | Notes                                                                                                                                    |+| ------------------------------- | ------- | ---------------------------------------------------------------------------------------------------------------------------------------- |+| CREATE INTEGRATION              | Account | %ac-accountadmin%                                                                                                                        |+| CREATE NOTIFICATION INTEGRATION | Account | Grants the ability to create notification integrations. This privilege does not grant the ability to create other types of integrations. |  </div> 

--- ahttps://docs.snowflake.com/en/sql-reference/sql/create-notification-integration-queue-inbound-gcp+++ bhttps://docs.snowflake.com/en/sql-reference/sql/create-notification-integration-queue-inbound-gcp@@ -107,7 +107,8 @@ <div className="colwidths-auto"> -| Privilege          | Object  | Notes             |-| ------------------ | ------- | ----------------- |-| CREATE INTEGRATION | Account | %ac-accountadmin% |+| Privilege                       | Object  | Notes                                                                                                                                    |+| ------------------------------- | ------- | ---------------------------------------------------------------------------------------------------------------------------------------- |+| CREATE INTEGRATION              | Account | %ac-accountadmin%                                                                                                                        |+| CREATE NOTIFICATION INTEGRATION | Account | Grants the ability to create notification integrations. This privilege does not grant the ability to create other types of integrations. |  </div> 

--- ahttps://docs.snowflake.com/en/sql-reference/sql/create-notification-integration-email+++ bhttps://docs.snowflake.com/en/sql-reference/sql/create-notification-integration-email@@ -139,7 +139,8 @@ <div className="colwidths-auto"> -| Privilege          | Object  | Notes             |-| ------------------ | ------- | ----------------- |-| CREATE INTEGRATION | Account | %ac-accountadmin% |+| Privilege                       | Object  | Notes                                                                                                                                    |+| ------------------------------- | ------- | ---------------------------------------------------------------------------------------------------------------------------------------- |+| CREATE INTEGRATION              | Account | %ac-accountadmin%                                                                                                                        |+| CREATE NOTIFICATION INTEGRATION | Account | Grants the ability to create notification integrations. This privilege does not grant the ability to create other types of integrations. |  </div> 

--- ahttps://docs.snowflake.com/en/developer-guide/odbc/odbc-universal-core+++ bhttps://docs.snowflake.com/en/developer-guide/odbc/odbc-universal-core@@ -254,5 +254,5 @@ - **Fixed scale handling during the conversion from `SQL_C_NUMERIC` to `VARCHAR`.** ODBC 4.x applies the scale from `SQL_NUMERIC_STRUCT`, for example magnitude `12345` with scale `2` becomes `"123.45"`; ODBC 3.x ignored scale. New driver now honors the explicitly set scale by the user. *(BD#33)* - **Fixed binding of subnormal doubles near `DBL_MIN`.** ODBC 4.x preserves the value; ODBC 3.x could store `0.0`. Prevents data loss for very small floating-point values. *(BD#36)*-- **Improved conversion from TIME `SQL_C_CHAR` / `SQL_C_WCHAR`.** ODBC 4.x returns `SQL_ERROR` with SQLSTATE `22003` (numeric value out of range) when the buffer is too small for the base time (HH:MM:ss), and `SQL_SUCCESS_WITH_INFO` with SQLSTATE `01004` (string data, right truncated) when only fractional seconds are truncated; ODBC 3.x returned error when buffer was undersized to hold the full time. *(BD#38)*+- **Improved conversion from TIME `SQL_C_CHAR` / `SQL_C_WCHAR`.** ODBC 4.x returns `SQL_ERROR` with SQLSTATE `22003` (numeric value out of range) when the buffer is too small for the base time (HH:MM:SS), and `SQL_SUCCESS_WITH_INFO` with SQLSTATE `01004` (string data, right truncated) when only fractional seconds are truncated; ODBC 3.x returned error when buffer was undersized to hold the full time. *(BD#38)* - **Fixed conversion from DATE to `SQL_C_BINARY` with an undersized buffer.** ODBC 4.x returns `SQL_ERROR` with SQLSTATE `22003` (numeric value out of range); ODBC 3.x could return `SQL_SUCCESS` with truncated data. Prevents data inconsistency. *(BD#44)* - **Fixed the export of `SQLGetFunctions` for `SQL_API_SQLCANCELHANDLE`.** ODBC 4.x reports the function as supported; ODBC 3.x reported `SQL_FALSE` even though the export worked at runtime. *(BD#45, to be verified)*@@ -273,5 +273,5 @@ ### PUT/GET behavior -- **Fixed stage array binding thresholds and user-defined array bind support.** ODBC 4.x honors `arrayBindSupported`. `CLIENT_STAGE_ARRAY_BINDING_THRESHOLD` is aligned across the drivers suite; ODBC 3.x ignored server-provided value of `arrayBindSupported`. *(BD#78)*+- **Fixed stage array binding thresholds and user-defined array bind support.** ODBC 4.x honors `arrayBindSupported`. `CLIENT_STAGE_ARRAY_BINDING_THRESHOLD` is aligned across the driver suite; ODBC 3.x ignored server-provided value of `arrayBindSupported`. *(BD#78)*  ### Authentication and security@@ -286,5 +286,5 @@ ### Snowflake extensions and diagnostics -- **Extended Snowflake statement attributes: `SQL_SF_STMT_ATTR_LAST_QUERY_ID`, `SQL_SF_STMT_ATTR_MULTI_STATEMENT_COUNT`.** ODBC 4.x: `SQL_SF_STMT_ATTR_LAST_QUERY_ID` is read-only and properly populated in all cases; `SQL_SF_STMT_ATTR_MULTI_STATEMENT_COUNT` defaults to `-1` (auto-detect) and supports get/set. ODBC 3.x: `SQL_SF_STMT_ATTR_LAST_QUERY_ID` is not populated in all use cases. Set on `SQL_SF_STMT_ATTR_LAST_QUERY_ID` succeeds with no-op.; `SQL_SF_STMT_ATTR_MULTI_STATEMENT_COUNT` is not implemented. Extends multi-statement control and tightens query-ID behavior. *(BD#56)*+- **Extended Snowflake statement attributes: `SQL_SF_STMT_ATTR_LAST_QUERY_ID`, `SQL_SF_STMT_ATTR_MULTI_STATEMENT_COUNT`.** ODBC 4.x: `SQL_SF_STMT_ATTR_LAST_QUERY_ID` is read-only and properly populated in all cases; `SQL_SF_STMT_ATTR_MULTI_STATEMENT_COUNT` defaults to `-1` (auto-detect) and supports get/set. ODBC 3.x: `SQL_SF_STMT_ATTR_LAST_QUERY_ID` is not populated in all use cases. Set on `SQL_SF_STMT_ATTR_LAST_QUERY_ID` succeeds with a no-op. `SQL_SF_STMT_ATTR_MULTI_STATEMENT_COUNT` is not implemented. Extends multi-statement control and tightens query-ID behavior. *(BD#56)* - **Changed diagnostic message text.** ODBC 4.x appends an internal error trace by default (`ErrorTraceEnabled` in `sf.odbc.ini`, default `true`); ODBC 3.x returned message text only. Improves error visibility; can be disabled. *(BD#77)*  

--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/setup-openflow-spcs+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/setup-openflow-spcs@@ -60,6 +60,6 @@     <tr>       <td>4</td>-      <td>[Create Snowflake role](/user-guide/data-integration/openflow/setup-openflow-spcs-create-rr)</td>-      <td>After creating an %ofsfspcs%, you must create a Snowflake role and associated external access integrations.</td>+      <td>[Create execute-as role](/user-guide/data-integration/openflow/setup-openflow-spcs-create-rr)</td>+      <td>After creating an %ofsfspcs%, you must create an execute-as role and associated external access integrations.</td>       <td>Data engineer</td>     </tr>@@ -67,5 +67,5 @@       <td>5</td>       <td>[Create runtime](/user-guide/data-integration/openflow/setup-openflow-spcs-create-runtime)</td>-      <td>Create a runtime associated with the previously created Snowflake role.</td>+      <td>Create a runtime associated with the previously created execute-as role.</td>       <td>Data engineer</td>     </tr> 

--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/sql-server-cdc/setup+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/sql-server-cdc/setup@@ -210,7 +210,5 @@  -5. Deploy the Openflow CDC wrapper procedures so the connector can manage capture instances and-   apply source schema changes autonomously. For more information, see-   [Deploy the Openflow CDC wrapper procedures](#label-sql-server-cdc-wrapper-procedures).+5. Deploy the Openflow CDC wrapper procedures so the connector can rotate capture instances when supported schema changes occur. For deployment instructions, see [Deploy the Openflow CDC wrapper procedures](#label-sql-server-cdc-wrapper-procedures). If permissions or internal policy blocks deployment, see [When the wrapper procedures aren't deployed](/user-guide/data-integration/openflow/connectors/sql-server-cdc/about#label-sql-server-cdc-wrapper-procedures-missing).  6. (Optional) Grant the VIEW DEFINITION privilege on the User Defined Data Types (UDDT).@@ -234,4 +232,6 @@  ## Deploy the Openflow CDC wrapper procedures++Deploy these procedures during connector setup (step 5). Without them, replication runs normally until a supported schema change occurs; at that point a DBA must run the SQL from the WARN bulletin on the **MultiDatabaseCaptureChangeCdcSqlServer** processor for each change. Only take that path when permissions or internal policy blocks deployment. For what to look for, see [When the wrapper procedures aren't deployed](/user-guide/data-integration/openflow/connectors/sql-server-cdc/about#label-sql-server-cdc-wrapper-procedures-missing).  The connector applies supported source table schema changes (DDL) without stopping replication or 

--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/ai-observability+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/ai-observability@@ -53,7 +53,7 @@ Credits, tokens, models, and request IDs for every surface are recorded in [SNOWFLAKE_COCO_USAGE_HISTORY](/sql-reference/account-usage/snowflake_coco_usage_history), whose `INTERFACE` column identifies the originating surface. Per-surface views are also available: -- **Snowsight**: [CORTEX_CODE_SNOWSIGHT_USAGE_HISTORY](/sql-reference/account-usage/cortex_code_snowsight_usage_history)-- **Desktop**: [CORTEX_CODE_DESKTOP_USAGE_HISTORY](/user-guide/cortex-code/cortex-code-desktop/cortex-code-desktop-usage-history-view) (see also [Audit logging and observability](/user-guide/cortex-code/cortex-code-desktop/security#audit-logging-and-observability))-- **CLI**: [CORTEX_CODE_CLI_USAGE_HISTORY](/sql-reference/account-usage/cortex_code_cli_usage_history)+- **Snowsight**: [Observability](/user-guide/cortex-code/cortex-code-snowsight/observability) and [CORTEX_CODE_SNOWSIGHT_USAGE_HISTORY](/sql-reference/account-usage/cortex_code_snowsight_usage_history)+- **Desktop**: [Audit logging and observability](/user-guide/cortex-code/cortex-code-desktop/security#audit-logging-and-observability) and [CORTEX_CODE_DESKTOP_USAGE_HISTORY](/sql-reference/account-usage/cortex_code_desktop_usage_history)+- **CLI**: [CoCo CLI](/user-guide/cortex-code/cortex-code-cli) and [CORTEX_CODE_CLI_USAGE_HISTORY](/sql-reference/account-usage/cortex_code_cli_usage_history)  See also [Cost controls for CoCo](/user-guide/cortex-code/cost-controls) and [daily credit usage limits](/user-guide/cortex-code/credit-usage-limit). 

--- ahttps://docs.snowflake.com/en/user-guide/data-engineering/dbt-projects-on-snowflake-limitations+++ bhttps://docs.snowflake.com/en/user-guide/data-engineering/dbt-projects-on-snowflake-limitations@@ -29,7 +29,6 @@   requires an `account` and `user`, but these can be left with an empty or arbitrary string because the dbt project runs in   Snowflake under the current account and user context.-- A dbt project in a workspace can't have more than 20,000 files in its folder structure. This limit includes all files in the dbt project-  directory and subdirectories, including the `target/dbt_packages/logs` directories, which is where log files are saved when a dbt-  project runs from within the workspace.+- When you deploy a specific dbt project folder as a dbt project object, that folder can contain at most 100,000 files. This limit includes all files in the dbt project+  directory and subdirectories, including generated `target`, `dbt_packages`, and `logs` directories. - Serverless tasks can't be used to execute dbt project objects. When you create a task that executes the EXECUTE DBT PROJECT command, you must   specify a user-managed warehouse. 

--- ahttps://docs.snowflake.com/en/user-guide/cortex-code/cortex-code-snowsight+++ bhttps://docs.snowflake.com/en/user-guide/cortex-code/cortex-code-snowsight@@ -5,4 +5,5 @@ - [CoCo](/user-guide/cortex-code/cortex-code) - [CoCo Desktop](/user-guide/cortex-code/cortex-code-desktop)+- [Cost controls for CoCo](/user-guide/cortex-code/credit-usage-limit) - [Snowsight](/user-guide/ui-snowsight) - [Workspaces](/user-guide/ui-snowsight/workspaces)@@ -140,5 +141,5 @@  - **Governance and security:** Retrieve information about user and role access, data ownership, and tables containing personally identifiable information (PII).-- **Cost management:** Query account usage and credit consumption, and identify high-cost warehouses or queries.+- **Cost management:** Query account usage and credit consumption, and identify high-cost warehouses or queries. For information about managing CoCo usage and setting credit limits, see [Cost controls for CoCo](/user-guide/cortex-code/credit-usage-limit).  ## Supported models and regions@@ -297,5 +298,5 @@  CoCo always starts a session using your default role, regardless of the role you've selected-in %sf-web-interface% worksheets, workspaces, or the role selector in the lower-left corner of the UI. If you need to perform actions+in %sf-web-interface% worksheets, Workspaces, or the role selector in the lower-left corner of the UI. If you need to perform actions that require a different role, you can ask CoCo to change roles during the session (for example, "switch to the SYSADMIN role").  

--- ahttps://docs.snowflake.com/en/user-guide/cortex-code/tools+++ bhttps://docs.snowflake.com/en/user-guide/cortex-code/tools@@ -18,4 +18,9 @@  When creating custom skills, you must specify the tools the skill can use. See [](#label-extensibility-skills).++The section headings on this page are display names. Wherever you name a tool in configuration, such as+a skill or subagent `tools:` list, a hook `matcher` field, or a permission rule, use the lowercase+runtime tool ID instead: `read`, `write`, `edit`, `glob`, `grep`, `bash`, and so on. These names are+case-sensitive, and a name that matches no tool is ignored without an error.  ## File tools 

--- ahttps://docs.snowflake.com/en/user-guide/organization-hub-insights+++ bhttps://docs.snowflake.com/en/user-guide/organization-hub-insights@@ -27,6 +27,6 @@ The top of Insights contains highlights from each section. Select a tile to switch to the corresponding tile further down the page. -A tile labeled **Coming soon** is in private preview. To request access, use the feedback button in-%sf-web-interface% or contact your Snowflake account team.+A tile labeled **Coming soon** is in private preview. In private preview, that tile includes organization budgets.+To request access, use the feedback button in %sf-web-interface% or contact your Snowflake account team.  ## Billing and Cost 

--- ahttps://docs.snowflake.com/en/user-guide/organization-hub-command-center+++ bhttps://docs.snowflake.com/en/user-guide/organization-hub-command-center@@ -13,5 +13,5 @@  Command Center requires an [organization account](/user-guide/organization-accounts). Access is limited to the-GLOBALORGADMIN role. More granular application roles aren't available yet.+GLOBALORGADMIN role.  ## Get started@@ -38,3 +38,3 @@ Command Center, including Organization Features and 3rd party access configuration, requires the GLOBALORGADMIN role. ORGANIZATION_USAGE application roles can open [Insights](/user-guide/organization-hub-insights), but they can't open-Command Center yet.+Command Center. 

--- ahttps://docs.snowflake.com/en/user-guide/snowpipe-streaming/snowpipe-streaming-high-performance-best-practices+++ bhttps://docs.snowflake.com/en/user-guide/snowpipe-streaming/snowpipe-streaming-high-performance-best-practices@@ -179,5 +179,7 @@ ### Wrap ingestion in try-catch blocks -Don't assume that `insertRows` always succeeds. Ensure that your ingestion loop can catch `SFException` and interpret the HTTP status codes, specifically 409 for invalidations and 429 for throttling.+Don't assume that an append call always succeeds. Every call to `appendRow`/`appendRows` (Java) or `append_row`/`append_rows` (Python) can return an error, so wrap it, catch the error the SDK returns (for example, `StreamingIngestError` in Python), and then retry or otherwise handle it. Never ignore or drop the returned error. Interpret the HTTP status codes, specifically 409 for invalidations and 429 for throttling.++Some errors surface asynchronously, after rows are buffered rather than at the append call, so in addition to catching errors at the call site, monitor channel status (for example, `getChannelStatus` or `row_error_count`) to detect failures that appear later.  ### Implement exponential back-off 

--- ahttps://docs.snowflake.com/en/user-guide/cortex-code/changelog+++ bhttps://docs.snowflake.com/en/user-guide/cortex-code/changelog@@ -6,5 +6,5 @@ - [Cortex Code CLI](/user-guide/cortex-code/cortex-code-cli) -This page documents notable changes to CoCo CLI.+This page documents notable changes to Cortex Code.  ## 1.1.65 (2026-08-11)@@ -13,5 +13,5 @@  - Data exploration subagent: CoCo CLI now includes a `data-discovery` subagent that can explore your Snowflake databases, schemas, and tables to answer questions about your data. It's enabled by default for all accounts. To turn it off, set `CORTEX_CODE_EXPERIMENTAL_FEATURES={"dataDiscovery":false}`.-- Managed settings enforcement: Administrators can enforce organization policies through a managed settings file. You can limit the Snowflake accounts and authentication methods that CoCo CLI is allowed to use and require a minimum CLI version. Use `cortex managed-settings` to inspect the active policy.+- Managed settings enforcement: Administrators can enforce organization policies through a managed settings file. You can limit the Snowflake accounts and authentication methods that CoCo CLI is allowed to use, and require a minimum CLI version. Use `cortex managed-settings` to inspect the active policy. - Snowflake authentication for MCP servers: HTTP and SSE MCP servers can now authenticate with a named Snowflake connection. Add a `snowflake_connection` field to the server's entry in `mcp.json`, or use `cortex mcp add`, and CoCo CLI injects a fresh session token on every request. This gives you zero-configuration access to MCP servers hosted on Snowpark Container Services without a static token. - Ignore ambient MCP servers: Added the `--only-explicit-mcp-servers` flag so a session loads only the MCP servers you pass in, for example with `--mcp-config`, and skips the servers configured in `mcp.json` and `~/.claude.json`. 

--- ahttps://docs.snowflake.com/en/user-guide/cortex-code/cortex-code-acp+++ bhttps://docs.snowflake.com/en/user-guide/cortex-code/cortex-code-acp@@ -92,5 +92,5 @@ ### Configure Zed -To use Cortex Code in Zed, add it as a custom external agent. Before you start, complete the [Prerequisites](#prerequisites) and confirm that `cortex acp serve -c <connection_name>` runs successfully in a terminal.+To use CoCo in Zed, add it as a custom external agent. Before you start, complete the [Prerequisites](#prerequisites) and confirm that `cortex acp serve -c <connection_name>` runs successfully in a terminal.  The configuration below uses the same `agent_servers` structure described in the [Zed external agents documentation](https://zed.dev/docs/ai/external-agents). The only difference is the `command` and `args` values, which launch Cortex Code's ACP subprocess (`cortex acp serve`) instead of a generic agent executable.@@ -138,5 +138,5 @@ ### Configure JetBrains IDEs -To use Cortex Code in a JetBrains IDE that supports ACP, add it as a custom agent in `~/.jetbrains/acp.json`. Before you start, complete the [Prerequisites](#prerequisites) and confirm that `cortex acp serve -c <connection_name>` runs successfully in a terminal.+To use CoCo in a JetBrains IDE that supports ACP, add it as a custom agent in `~/.jetbrains/acp.json`. Before you start, complete the [Prerequisites](#prerequisites) and confirm that `cortex acp serve -c <connection_name>` runs successfully in a terminal.  1. Open the **AI Chat** tool window. 

--- ahttps://docs.snowflake.com/en/sql-reference/account-usage/snowflake_coco_usage_history+++ bhttps://docs.snowflake.com/en/sql-reference/account-usage/snowflake_coco_usage_history@@ -12,5 +12,5 @@ - [](/user-guide/cortex-code/cortex-code) - [](/sql-reference/account-usage/cortex_code_cli_usage_history)-- [](/user-guide/cortex-code/cortex-code-desktop/cortex-code-desktop-usage-history-view)+- [](/sql-reference/account-usage/cortex_code_desktop_usage_history) - [](/sql-reference/account-usage/cortex_code_snowsight_usage_history) @@ -25,5 +25,5 @@  - [CORTEX_CODE_CLI_USAGE_HISTORY](/sql-reference/account-usage/cortex_code_cli_usage_history) for CoCo CLI-- [CORTEX_CODE_DESKTOP_USAGE_HISTORY](/user-guide/cortex-code/cortex-code-desktop/cortex-code-desktop-usage-history-view) for CoCo Desktop+- [CORTEX_CODE_DESKTOP_USAGE_HISTORY](/sql-reference/account-usage/cortex_code_desktop_usage_history) for CoCo Desktop - [CORTEX_CODE_SNOWSIGHT_USAGE_HISTORY](/sql-reference/account-usage/cortex_code_snowsight_usage_history) for CoCo in Snowsight  

--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-search/tutorials/cortex-search-tutorial-2-chat+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-search/tutorials/cortex-search-tutorial-2-chat@@ -27,5 +27,5 @@  You will use a sample dataset hosted on Kaggle for this tutorial.-The Books dataset is a collection of book names, titles, and descriptions. The complete dataset can be found on+The Books dataset is a collection of titles and descriptions. The complete dataset can be found on [Kaggle](https://www.kaggle.com/datasets/elvinrustam/books-dataset/data). @@ -63,5 +63,5 @@ ``` -Now upload the dataset. You can upload the dataset in %sf-web-interface% or using SQL. To upload in %sf-web-interface%:+Now upload the dataset to %sf-web-interface%:  1. Sign in to %sf-web-interface-link%. 

--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-search/cortex-search-monitor+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-search/cortex-search-monitor@@ -216,5 +216,5 @@ The following is an example of data found in the VALUE column: -```javascript+```json {   "snow.ai.observability.operation_type": "QUERY",@@ -247,5 +247,5 @@   record_attributes['snow.ai.observability.user.name']::STRING AS user_name,   record_attributes['snow.ai.observability.role.name']::STRING AS role_name,-  record_attributes['snow.ai.observability.session.id']::STRING AS session_id,+  record_attributes['snow.ai.observability.session.id']::STRING AS session_id FROM TABLE(snowflake.local.get_ai_observability_events(   '<database_name>', 

--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/security/workload-identity-federation+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/security/workload-identity-federation@@ -82,5 +82,5 @@ unique to each secret. -Grant `USAGE` on the database, schema, and secret to the Snowflake role assigned to the Openflow runtime:+Grant `USAGE` on the database, schema, and secret to the execute-as role assigned to the Openflow runtime:  ```sql@@ -145,5 +145,5 @@ You can create a one-to-many mapping between a single secret and multiple IAM roles. For example, to give read-only access to one Snowflake role and read-write access to another, edit the role's trust policy to add a condition on the-`sf_rnm` claim, which equals the name of the Snowflake role assigned to the Openflow runtime:+`sf_rnm` claim, which equals the name of the execute-as role assigned to the Openflow runtime:  ```json 

--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/setup-openflow-spcs-create-runtime+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/setup-openflow-spcs-create-runtime@@ -51,6 +51,6 @@     </tr>     <tr>-      <td>**Snowflake Role**</td>-      <td>Choose the Snowflake role previously created in [](/user-guide/data-integration/openflow/setup-openflow-spcs-create-rr).</td>+      <td>**Execute-as Role**</td>+      <td>Choose the execute-as role previously created in [](/user-guide/data-integration/openflow/setup-openflow-spcs-create-rr).</td>     </tr>     <tr> 

--- ahttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-skills+++ bhttps://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-skills@@ -120,7 +120,5 @@ ### Cortex Extensions -Support for this feature is currently not in production and is available only to selected accounts.--You can reference a [Cortex Extension](/LIMITEDACCESS/cortex-code-skill-plugin-sharing) by fully qualified name+You can reference a [Cortex Extension](/user-guide/cortex-code/cortex-code-skill-plugin-sharing) by fully qualified name (FQN) instead of listing each of its skills individually. At request time, Snowflake expands the reference into the extension's individual skills, so the agent orchestrator sees each member skill directly. Updates to the 

--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/postgres/iceberg+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/postgres/iceberg@@ -222,6 +222,6 @@       <td>SMALLINT / INTEGER</td>       <td>INT</td>-      <td>`int`</td>-      <td>`int`</td>+      <td>`long`</td>+      <td>`long`</td>     </tr>     <tr> 

--- ahttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/sql-server/iceberg+++ bhttps://docs.snowflake.com/en/user-guide/data-integration/openflow/connectors/sql-server/iceberg@@ -231,6 +231,6 @@       <td>TINYINT / SMALLINT / INT</td>       <td>INT</td>-      <td>`int`</td>-      <td>`int`</td>+      <td>`long`</td>+      <td>`long`</td>     </tr>     <tr> 

--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-cli/command-reference/dcm-commands/list-deployments+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-cli/command-reference/dcm-commands/list-deployments@@ -203,5 +203,5 @@ <dd> -Value of client id provided by the Identity Provider for Snowflake integration.+Value of the client ID provided by the Identity Provider for Snowflake integration.  </dd>@@ -245,5 +245,5 @@ <dd> -Enables a silent re-authentication when the actual access token becomes outdated. Default: *False*.+Enables a silent re-authentication when the current access token becomes outdated. Default: *False*.  </dd> 

--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-cli/native-apps/project-definitions+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-cli/native-apps/project-definitions@@ -308,5 +308,5 @@ If `src` refers to just one file (not a glob), `dest` can refer to a target `<path>` or a `<path/name>`. -You can also pass in a string for each item instead of a `dict`, which case, the value is treated as both `src` and `dest`.+You can also pass in a string for each item instead of a `dict`, in which case, the value is treated as both `src` and `dest`.  Example without a processor:@@ -510,5 +510,5 @@ Whether to enable debug mode when using a named stage to create an application. -Default: `True`+Default: `true`  </td> 

--- ahttps://docs.snowflake.com/en/developer-guide/snowflake-cli/native-apps/bundle-app+++ bhttps://docs.snowflake.com/en/developer-guide/snowflake-cli/native-apps/bundle-app@@ -52,5 +52,5 @@ ## Generate SQL code using Snowpark annotation processing -As a %native-app% developer with a limited SQL background, you might find it cumbersome to write and maintain [setup scripts](/developer-guide/native-apps/creating-setup-script), which can get quite large and complicated over time. Setup scripts contain all the application logic that a customer can use with their data, and hence are a required part of developing a Snowflake Native App. One of the core components of setup scripts is your ability to use Snowpark Python extension functions for functions and stored procedures. In addition to writing Snowpark code in Python, Java, or other Snowpark supported languages, you need to write the corresponding portions of those functions and procedures using SQL in the setup script.+As a %native-app% developer with a limited SQL background, you might find it cumbersome to write and maintain [setup scripts](/developer-guide/native-apps/creating-setup-script), which can get quite large and complicated over time. Setup scripts contain all the application logic that a customer can use with their data, and hence are a required part of developing a Snowflake Native App. One of the core components of setup scripts is your ability to use Snowpark Python extension functions for functions and stored procedures. In addition to writing Snowpark code in Python, Java, or other Snowpark-supported languages, you need to write the corresponding portions of those functions and procedures using SQL in the setup script.  For example, you could create a basic function and stored procedure using Snowpark Python, as shown:@@ -149,5 +149,5 @@ The Snowpark processor executes Python files from your project directory, including subdirectories. Only use `snow app bundle`, `snow app deploy`, and `snow app diff` with projects and Python files you trust. -- You can't use any `Session` objects in these files, as %sf-cli% executes these Python files in a sandbox environment with no connection to Snowflake. As a result, any reference of a Snowpark `Session` results in an error.+- You can't use any `Session` objects in these files, as %sf-cli% executes these Python files in a sandbox environment with no connection to Snowflake. As a result, any reference to a Snowpark `Session` results in an error. - You can use only the `@udf`, `@sproc`, `@udaf`, and `@udtf` Snowpark Python decorators. - You can't use these decorators as regular functions to register your code as a Snowflake object. Only code explicitly annotated with the supported decorators is recognized. Therefore, the Python function must be a named function. Lambda functions are not supported.