> ## Documentation Index
> Fetch the complete documentation index at: https://docs.condense.io/llms.txt
> Use this file to discover all available pages before exploring further.

# What's New in v2.6.0

> Condense v2.6.0 adds runtime alerts with SMTP email, pre-configured member access, Coding Agent token tracking and a QA Agent, and more reliable operations.

Condense v2.6.0 makes it easier to watch your pipelines, onboard your team and build with AI. This release adds runtime alerts that can email you through your own mail server, lets admins prepare a new member's access before they sign up, and brings usage tracking and automatic testing to the Coding Agent. It also makes application management and event delivery more reliable.

The following sections summarize what changed in this release.

## Runtime Alerts for Connectors and Transforms

You can now set alerts on how your connectors, transforms and custom connectors are running. Pick from predefined alerts such as CPU Utilization, Memory Utilization, Consumer Lag, Consumer Group Health, Response Latency, Active Connections and CrashLoopBackOff, and Condense notifies you when one crosses its limit.

Set alerts while you deploy a component, or later from the Pipeline page. Where an alert has a threshold and duration, you choose them. Condense manages the queries behind each alert and sends one notification per incident instead of repeating it while the problem continues.

See [Runtime alerts for connectors and transforms](https://docs.condense.io/condense/v2.6.0/alerts/observability-and-alerts.md).

## SMTP Configuration for Alert Emails

Environment Admins can connect an environment to their own mail server, so alerts reach people by email. Go to Settings, then Integrations, then SMTP, enter the server details and send a test email before you rely on it.

Every alert still creates an in-app notification, so nothing is lost if email is unavailable. Temporary delivery failures are retried automatically, and permanent failures show as Delivery Failed in the alert history. Staging and Production keep separate settings.

See [Configure SMTP for alert emails](https://docs.condense.io/condense/v2.6.0/alerts/smtp-configuration.md).

## Invite Members with Pre-Configured Access

Admins can now choose a new member's roles and environments when they send the invitation, instead of waiting for the person to sign up first. The invitation shows as Pending, and you can still change, resend or cancel it. When the person signs in for the first time, their access is already in place, so they land on a working environment instead of an empty dashboard.

See [Invite Members](https://docs.condense.io/condense/v2.6.0/condense-guide/condense-console/invite-members.md).

## Coding Agent Improvements

The Coding Agent now comes ready to use inside the web VS Code IDE that opens when you create an application. There is nothing to install and no separate sign-in.

Two additions make it easier to monitor and trust. Token usage is tracked, so you can see how much AI model capacity your coding work uses. A new QA Agent writes test cases for the code the Coding Agent generates and validates them.

See [Coding Agent](https://docs.condense.io/condense/v2.6.0/ai-agents/coding-agent.md).

## More Reliable Application Management

Creating, deploying and updating applications now runs through a redesigned workflow that coordinates each step in one place. This makes application creation and deployment more reliable, handles slow container startups better, avoids repeated repository work, and gives clearer tracking of an application's lifecycle.

## More Reliable Event Delivery

Console and Core now track each event until it has been processed, instead of sending it and assuming it arrived. Failed events can be retried, failures are easier to see, and the platform no longer depends on one long-lived connection between Console and Core.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.