# July 2026 Release Note These are the Treasure AI features and improvements released in July, 2026. ## AI Studio ### New Feature: Custom Skill Sharing *Posted on: Jul 3, 2026* - AI Studio now lets you share the custom skills you build in a project with everyone in your account, so teammates can install them with a single click — no public GitHub repository required. - Designed for teams that want to reuse in-house expertise, it keeps skills private to your account as an alternative to the public Plugin Marketplace, and makes sharing easy even for people who can't or don't want to publish to GitHub. - Build skills in a project, then share them as a named plugin from the new **Develop** tab; teammates discover and install them from the **Shared** tab and manage their installs under **Installed**. - Sharing publishes a snapshot, so you can keep refining a skill and push updates when you're ready — subscribers pick up your latest version the next time they start a chat. - Learn more by visiting the [Sharing Custom Skills](/products/ai-studio/skills/sharing-custom-skills) page. ### Now Available in the Korea (ap02) Region *Posted on: Jul 3, 2026* - Treasure AI Studio is now available to accounts hosted in the Korea (ap02) region, so Korea-based teams can sign in and run the same chat-based AI workflows offered in the US, Tokyo, and EU01 regions. - Designed for customers with data residency requirements in Korea, it keeps LLM inference within the Korea geographic boundary on Amazon Bedrock (Seoul). - In the Korea region, AI Studio offers a single model tier — **Balanced**, backed by Claude Sonnet 4 — while the **Pro** and **Fast** tiers are not available there. ### Enhancement to Connections: Create a Connection from a Chat *Posted on: Jul 3, 2026* - Treasure AI Studio now lets you create a data-source connection without leaving the conversation: when an agent needs a service you haven't connected yet, it shows an inline **Connection Required** card with a **Connect** button right in the chat. - Designed for anyone working with an agent, it removes the interruption of stopping to visit **Settings → Connections** before the agent can reach your data, so you can authorize on demand and keep going. - Click **Connect** on the card to complete the same secure OAuth authorization used in Settings (or **Decline** to skip); the connection you create this way is a normal connection that appears under **Settings → Connections** and is reused in later chats. This is available for the Databricks and Snowflake connectors. - Learn more by visiting the [Connections](/products/ai-studio/connections) page. A Connection Required card shown in an AI Studio chat, reading 'The agent needs a connection to Databricks. Please connect to continue.' with Decline and Connect buttons ### AI Studio Update: Work Folders and a Refreshed Sidebar *Posted on: Jul 8, 2026* - The AI Studio workspace that pre-loads your instructions, skills, and default data context into every new chat is now called a **Work Folder** (previously "Project") — the same capability, with a name that better reflects how you use it. - **New Chat** now leads the top of the sidebar, a quick **+** action appears on hover to start a chat inside a work folder, and search has moved into a header toggle (🔍) that reveals a box filtering both chats and work folders by name. - Designed for everyday users, these changes put the most frequent action — starting a conversation — front and center and make the sidebar easier to scan. - Only the labels changed: your existing work folders, their instructions, and their pre-selected skills continue to work exactly as before. - Learn more by visiting the [AI Studio Core Concepts](/products/ai-studio/concepts) page. ### New Feature: Custom Instructions *Posted on: Jul 8, 2026* - Treasure AI Studio now lets an account administrator set a **custom instruction** that is added to the system prompt of every agent in the organization, so shared conventions apply automatically in every chat. - Designed for account administrators, it gives an organization a self-service way to steer agent behavior — a preferred database, an output format, or a house style for summaries — without each user restating those conventions in every conversation. - Set it under **Settings → Instructions** (up to 16,384 characters); changes apply to new chats only. - Because the instruction becomes part of the agent's system prompt, do not include secrets, credentials, or personal data. - Learn more by visiting the [Custom Instructions](/products/ai-studio/custom-instructions) page. ### New Feature: Treasure Data CDP Connector for AI Studio *Posted on: Jul 14, 2026* - AI Studio now connects to your Treasure Data CDP through the same Connector/Connection model as Databricks and Snowflake: each user authorizes their own connection over OAuth, and the agent can then run queries, workflows, and audience-segment operations across your CDP directly in a chat. - Learn more by visiting the [Connect Treasure Data CDP](/products/ai-studio/connections/treasure-data) and [Connections](/products/ai-studio/connections) pages. AI Studio Connections page showing Treasure Data available to connect, alongside Databricks and Snowflake ## Engage Studio ### New Feature: HTML Email Hosting (View in Browser) *Posted on: Jul 3, 2026* - HTML Email Hosting serves a static, sanitized copy of a launched email campaign as a web page under your own Email Domain, so recipients who click **View in Browser** in their inbox see the full email rendered in a browser tab instead of relying on email client rendering. - Designed for marketers who want a reliable fallback for recipients whose email clients render HTML poorly, the feature publishes the page automatically at campaign launch and exposes its HTTPS URL through the `{{campaign.view_in_browser_url}}` variable, which can be inserted via the Beefree editor's Special Links panel. - HTML Email Hosting is currently in beta and requires an Email Domain with `DIGITAL_ASSETS` DNS enabled, plus feature enablement by Treasure AI Support; contact your account team to request access. - Learn more by visiting the [View in Browser](/products/marketing-cloud/engage-studio/channels/email/html-email-hosting) page. ## Integration Hub ### Enhancement to Iterable Export Connector: Truncate Mode *Posted on: Jul 1, 2026* - The Iterable Export Connector now supports a **truncate** action that replaces an Iterable list's membership in a single job, treating the query result as the complete desired state of the list. - Designed for enterprise customers managing large, frequently refreshed audience lists, truncate mode removes the need to orchestrate a separate `remove` job followed by an `add` job just to keep list membership in sync. - Truncate subscribes every user in the query result (refreshing their data fields, as **add** does) and unsubscribes any existing list member not present in the result; an empty query result is a valid input and clears the list. Set the **project_type** parameter (`email_based`, `userid_based`, or `hybrid`) to match how the target Iterable project identifies users. - Truncate mode is membership-only: the `campaign_id`, `channel_unsubscribe`, and `update_existing_users_only` parameters are ignored when `action` is `truncate`. - Learn more by visiting the [Iterable Export Integration](/int/iterable-export-integration) page. ### New Connector: Batch Export Connector — Profile Update *Posted on: Jul 9, 2026* - The Batch Export Connector sends customer profile data from Treasure AI directly to Batch's Profile Mass Update API, so segment attributes such as email, phone number, language, and custom fields stay in sync with Batch customer profiles. - Designed for marketers who use Batch as their customer engagement platform, the connector removes the manual exports and custom scripts previously required to keep Batch profiles current, improving data freshness for mobile push, web push, in-app, email, and SMS campaigns. - Configure the export from a query result: map columns to Batch native attributes (`$email_address`, `$language`, and more) or custom attributes using the `identifier__`, `batch__`, and type-prefixed column-naming convention, then run it as a one-time or scheduled export. - Learn more by visiting the [Batch Export Integration](/int/batch-export-integration) page. ### Enhancement to Yelp Conversions API Export: Bulk Upload Mode *Posted on: Jul 14, 2026* - The Yelp Conversions API Export connector now supports a **bulk_event** upload mode that batches up to 1,000 conversion events into a single API call, alongside the existing **single_event** mode that sends one event per request. - Designed for multi-location advertisers with high event volumes, bulk upload mode reduces API call overhead and improves throughput for large-scale segment exports and activation workflows, using the same field mapping, normalization, and SHA-256 hashing rules as single-event uploads. - Set the **Upload Mode** parameter to `bulk_event` when configuring the export (default remains `single_event`); no other configuration changes are required. - Learn more by visiting the [Yelp Conversions API Export Integration](/int/yelp-conversions-api-export-integration) page. ## Data Workbench ### New Feature: CREATE TABLE Support for Hive *Posted on: Jul 10, 2026* - The Hive query engine now supports the `CREATE TABLE` statement, so data engineers can define new tables directly using HiveQL — including table and column comments, data retention, and User-Defined Partitioning (UDP) via table properties — without switching to Trino. - Learn more by visiting the [CREATE TABLE Statement Syntax](/products/customer-data-platform/data-workbench/queries/sql-reference/create_table) page. ## Real-Time ### Enhancement to the Personalization API: td_ip and td_global_id Enrichment *Posted on: Jul 9, 2026* - The Personalization API (`{region}.p13n.in.treasuredata.com`, called via the JavaScript SDK's `fetchPersonalization` or directly over HTTP) now automatically populates `td_ip` from the request's `X-Forwarded-For` header and `td_global_id` from the matching browser cookie, when present, on every incoming event. - Designed for developers integrating real-time personalization into websites and apps, this brings the Personalization API's server-side enrichment in line with the standard Ingest API, removing an inconsistency where `td_ip` and `td_global_id` were populated automatically on one ingestion path but not the other. - No client-side changes are required — existing calls to the Personalization API pick up the enriched `td_ip` and `td_global_id` values automatically. - Learn more by visiting the [Personalization API Quickstart](/apis/p13n-api) page. ## AI Agent Foundry ### New Model: GPT-5.5 Support *Posted on: Jul 14, 2026* - AI Agent Foundry now supports OpenAI's GPT-5.5 as a selectable model for your agents. - Designed for customers who are limited to OpenAI models, it gives them access to GPT-5.5 rather than restricting them to earlier GPT versions such as GPT-5. - GPT-5.5 supports an adjustable **Reasoning effort** setting — including a new highest level, **Extra high** — so you can tune how deeply the model reasons before it responds. - GPT-5.5 is available alongside the existing GPT-5, GPT-5 mini, and GPT-5 nano models, and existing agents are unaffected. - Learn more by visiting the [Creating an Agent](/products/customer-data-platform/ai-agent-foundry/ai-agent/creating-an-agent) page. ## Control Panel ### Upcoming Change: Removal of the "Remember Me" Sign-in Option *Posted on: Jul 7, 2026* - Treasure AI is removing the "Remember Me" option from the Treasure Console sign-in page, so affected users will no longer be able to stay signed in automatically across browser sessions. - This change strengthens account security by ensuring that a configured user session timeout is always honored, closing a gap where an active "Remember Me" session could keep a user signed in well beyond the session timeout setting. - This change only affects users who sign in with email and password; users who sign in via SSO are not affected. The change is planned to take effect between July and August 2026. - Learn more by visiting the [Specifying Maximum Login Attempts and Session Timeout](/products/control-panel/security/sign-in-settings/specifying-maximum-login-attempts-and-session-timeout) page. ## Treasure Code (CLI) ### Enhancement: Move and Find Segments by Name *Posted on: Jul 9, 2026* - Treasure Code now lets you move a segment to a different folder by name — no internal ID lookup required. - A recursive search finds any segment across all folders by typing part of its name; if two segments share the same name, the command lists both and asks which one you meant rather than guessing. ### Fix: Query Output No Longer Truncated When Exported *Posted on: Jul 9, 2026* - Two issues that silently cut off query results during data exports have been fixed: results no longer stop at 40 rows by default, and large result sets are no longer cut off mid-stream with no warning. - Automated workflows and pipelines that export through Treasure Code now receive the full result every time. ### Enhancement: Journey Files Now Use a Distinct File Extension *Posted on: Jul 9, 2026* - Journey configuration files now use the `.journey.yml` extension, making them easy to tell apart from segment files in any folder or file browser. - Existing journey files continue to work without any changes needed.