# 2026 02 18 release notes (core) ## Release summary This page summarises items scheduled for the following release to the Patchworks Core Production environment.

Release version	Release date	Release status
v2026-02-18	Wednesday 18th February 2026 (a.m)	completed

New features, updates, and enhancements of note are summarised by product area, below: * [Hosted Patchworks MCP server](#process-flows) * [Process flows](#process-flows-1) * [Virtual environments](#virtual-environments) * [Company management](#company-management) ## Hosted Patchworks MCP server

Type	Summary	Ref #
New	Hosted Patchworks MCP server This release introduces our hosted MCP solution. In just a few minutes, you can deploy an MCP server with a set of default tools, and then connect to your preferred AI assistant (Claude, ChatGPT, Gemini CLI). With our hosted (rather than local) implementation, setup requirements are minimal - no technical knowledge is required. The default toolset covers key Patchworks functionality (flow creation, flow management, data pools, marketplace, troubleshooting, and utilities). With some Python knowledge, you can extend your server capabilities by adding your own tools. Patchworks MCP server (hosted)	CPT-4737 CPT-5376

## Process flows

Type	Summary	Ref #
Bug	Try/catch receives an empty payload from a given data path Fixed an issue where the given data path for a connector returned an empty dataset (e.g. `[]` or `{}`), which was (incorrectly) treated as a failed request. This stopped any further pagination and routed the flow down the `catch` branch. Now, empty results are handled correctly, allowing pagination to continue and the flow to proceed as expected. Try/Catch shape	CPT-5403

## Virtual environments

Type	Summary	Ref #
Bug	Using environment variables in custom scripts Fixed an issue where using environment variable values to populate flow variables was not working correctly in custom scripts - instead, placeholder text was passed through as a literal string. Additionally, environment variables were exposed in the script's output payload as a numerically indexed array, so users had to reference them by position rather than by a readable key name. Now, you can access environment variables by key (though backwards compatibility for numeric indexes is retained). Environment variables	CPT-4606 CPT-5422

Type

Summary

Ref #

Bug

Using environment variables in custom scripts
Fixed an issue where using environment variable values to populate flow variables was not working correctly in custom scripts - instead, placeholder text was passed through as a literal string.

Additionally, environment variables were exposed in the script's output payload as a numerically indexed array, so users had to reference them by position rather than by a readable key name.

Now, you can access environment variables by key (though backwards compatibility for numeric indexes is retained).

Environment variables

CPT-4606
CPT-5422

## Company management

Type Summary Ref #

Type	Summary	Ref #
Enhancement	Improved company insights for multi-company profiles If you manage multiple company profiles in Patchworks, you now have greater visibility on insights for those companies - specifically: You can now choose to view aggregated data and operations usage for your managed companies OR your parent company and managed companies When viewing aggregated usage, a list of 'child' (i.e. managed) companies is displayed so you can see usage for each one. For organisations with an annual billing agreement, a new `annual usage` section is displayed at the top of the insights page, showing cumulative data and operations usage. For organisations with an annual billing agreement, the navigation sidebar displays annual (rather than monthly) usage values. For organisations with an annual billing agreement, allowance values (available from a dropdown at the top of the insights page) are multiplied by 12. For organisations with a 'powered by' agreement, data and operations allowance bars (at the top of the insights page) will always show values associated with the parent company only, irrespective of whether the view is set for parent company, managed companies, or parent & managed companies. Company insights	CPT-4059 CPT-4704

Enhancement

Improved company insights for multi-company profiles
If you manage multiple company profiles in Patchworks, you now have greater visibility on insights for those companies - specifically:

You can now choose to view aggregated data and operations usage for your managed companies OR your parent company and managed companies
When viewing aggregated usage, a list of 'child' (i.e. managed) companies is displayed so you can see usage for each one.
For organisations with an annual billing agreement, a new annual usage section is displayed at the top of the insights page, showing cumulative data and operations usage.
For organisations with an annual billing agreement, the navigation sidebar displays annual (rather than monthly) usage values.
For organisations with an annual billing agreement, allowance values (available from a dropdown at the top of the insights page) are multiplied by 12.
For organisations with a 'powered by' agreement, data and operations allowance bars (at the top of the insights page) will always show values associated with the parent company only, irrespective of whether the view is set for parent company, managed companies, or parent & managed companies.

Company insights

CPT-4059
CPT-4704

--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://doc.wearepatchworks.com/product-documentation/release-information/core-release-notes/2026-02-18-release-notes-core.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.