> For the complete documentation index, see [llms.txt](https://docs.helvia.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.helvia.ai/resources/release-notes/helvia.ai-release-2026.11.19.md).

# Helvia.ai Release 2026.11.19

19 November 2026

## 1. Send Your Own Headers to MCP Servers, per Agent and per Node

You can now set custom headers for an MCP server on each agent and on each LLM v2 node, in addition to the integration itself. A header value can be fixed text or a variable, and variables are filled in on every turn.

**Why it matters:** Your MCP servers can act on behalf of the person in the conversation, using details such as their account token. You can also send different headers in different workflow steps without creating extra integrations.

**Example use case:** Your customer portal passes each signed-in user's token to the webchat, and your agent stores it in a variable. A runtime header sends it to your account-services MCP server, so a question like "What is the status of my application?" returns that user's own record.

**How it works:** In Designer, open the agent's **Tools** page, expand an MCP server, and under **Runtime headers** click **Add header**. Enter the header name and its value. To set headers for a single step, use the **Tools** tab of an LLM v2 node. Node headers override agent headers, which override the integration's **Custom headers**.

<div data-with-frame="true"><img src="https://604830754-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBM1xs3i59ajeTgi4uVfN%2Fuploads%2FzSIjVgNkMGbj33QJ1czt%2FPasted%20image%202026-11-17%2014.37.18.png?alt=media&amp;token=b7d6cc48-d3a1-4197-aa6d-ecef5ade5b58" alt="" width="563"></div>

## 2. Self-Service Account Unlock and an Extra Sign-In Check

If your console account is locked after several failed sign-in attempts, you can unlock it yourself from an email link. After a few failed attempts in a row, the sign-in page also shows a quick "I'm not a robot" check.

**Why it matters:** Recovering a locked account is quick and fully in your hands. The sign-in check adds a further layer of protection to every account.

**How it works:** When an account locks, its owner automatically receives an email with an unlock link. The sign-in page also offers **Send unlock link** to request a new one, and completing a password reset unlocks the account too.

<div align="center" data-with-frame="true"><img src="https://604830754-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBM1xs3i59ajeTgi4uVfN%2Fuploads%2FinFzulZ0zPOEPhzdotnb%2FPasted%20image%202026-11-17%2014.37.19.png?alt=media&amp;token=06d78e60-0d0b-419e-a0b0-92307bf98d81" alt="" width="375"></div>

## 3. LLM Integration Endpoints Need a Secure, Full Address

The address of an endpoint on an LLM integration must be an HTTPS address with a full domain name. This applies to any LLM integration that accepts an endpoint URL, such as OpenAI-compatible providers.

**Why it matters:** This check ensures that your agents connect only to your configured model provider, enhancing the security of our services.

**How it works:** Short internal addresses, such as localhost, are not accepted. If an existing integration uses one, update it to the provider's full address in **Workspace > Integrations**. If you need help setting up a self-hosted model, contact Helvia.ai Support at <support@helvia.ai>.

## 4. Platform Emails Come from <no-reply@helvia.ai>

Emails sent by the platform come from <no-reply@helvia.ai>. This covers user invitations, email verification, password reset, locked-account notices, Workspace membership updates, audit log notifications, and more.

**Why it matters:** The sender now makes clear that these are automatic messages from the Helvia.ai platform, not replies from our support team. This helps you recognize them and organize your inbox.

**How it works:** No setup is needed. Do not reply to these emails. If your organization uses mail filters or allowlists, add <no-reply@helvia.ai> to them. Replies to these emails are not monitored, so contact <support@helvia.ai> for help.
