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

# Changelog

Recent updates to Cleric

Every month, we update this changelog with the major features and bug fixes that were shipped to our customer environments.

## August 2026

In August, Cleric made it easier to focus on the issues that need action, address feedback and CI failures on the pull requests it creates, and manage the connections and usage that support your workspace.

**New Features**

* **Duplicate Issue Merging**: Keep recurring alerts with the investigation that already explains them. When a new alert has the same underlying cause as an earlier issue, Cleric adds its evidence to that issue and takes you there.
* **Alert Noise Reduction Stats**: See how much alert noise Cleric kept from becoming work for your team. The Performance page now shows the share of alerts that did not require action and how that changed from the previous period, including alerts that were grouped before investigation, merged afterward, or verified as resolved or false positives.
* **Pull Request Follow-through**: When a Cleric-created pull request receives reviewer comments or a CI failure, Cleric addresses the feedback or failure and posts updates in the linked thread.
* **Rebuilt Integrations Page**: Find, set up, and maintain integrations from one clearer place. **Installed** shows your connected integrations, surfaces connections that need attention, and displays a connection count; **Catalog** makes every available integration searchable by category. Each integration now has its own page for connections and setup.
* **Usage**: Track credit consumption against your billing-period allowance in the new Settings > Usage tab. It also flags overages and lets you review earlier periods.
* **Recommendations on System Health**: Prioritize the setup work that will make Cleric more effective in your environment. Choose which Slack channel receives recommendations, then review and dismiss them from the System Health page.
* **Improved Issue Search and Filtering**: Find past issues using details from anywhere in a conversation, then filter the list by participant.
* **New integrations**:
  * **Honeycomb**: Let Cleric use your Honeycomb trigger definitions to understand the condition an alert watches, how it is evaluated, and who it pages.
  * **Bitbucket Cloud**: Bring Bitbucket Cloud code, commits, pull requests, and Pipelines into investigations, and let Cleric open a pull request for review.
  * **Slite**: Make runbooks, incident procedures, and other documentation in Slite available to investigations with read-only access.
  * **Grafana SQL datasources**: Query MySQL, PostgreSQL, and other SQL datasources through Grafana alongside the metric datasources Cleric already supports.

**Bug Fixes**

* **Resolution and Check Updates**: Fixed Cleric posting resolution and scheduled-check updates when there was nothing new to report.
* **Sign-out**: Fixed sign-out leaving a session valid when the browser did not follow the logout redirect. Sessions are now revoked server-side.
* **Integration Credentials**: Fixed follow-ups using stale credentials. Cleric reloads an integration connection after its credentials are updated.
* **Change Verification Attribution**: Fixed verification updates crediting a bot for a change or omitting people responsible for it.
* **Slack Mentions**: Fixed mentions on Markdown header lines rendering as literal text and failing to notify the intended person.
* **Scheduled Checks**: Fixed checks reporting their initial state regardless of what happened, which delayed a verdict until expiration. Failed probes, unreadable output, and empty results now report as inconclusive.
* **MongoDB Atlas**: Fixed invalid metric queries and added access to disk and database endpoints.

## July 2026

July added Change Verification, scheduled checks for every agent, and narrow-screen layouts in the web app.

**New Features**

* **Change Verification**: Added a built-in `verify` agent that checks a released change against production evidence. It determines whether the intended outcome occurred, whether anything regressed, and which checks need a longer observation window. Run it on demand with `!verify` followed by a pull request link or change description, or set up a trigger to run it automatically for every deployment notification in a release channel. See [Change Verification](/usage/change-verification.md) for more.
* **Scheduled checks for any Agent**: The `investigation` agent and custom agents can now use scheduled checks. All agents have the capability to rerun a command on a cadence until the reported state changes or a time limit expires.
* **Updated Slack channel context**: Added tools that let Cleric read messages around an alert and list accessible channels, to improve context gathering in the initial investigation.

**Bug Fixes**

* **Service Map**: Fixed service-list links opening the full map when the selected service had no dependencies. Reset also clears the focused service and its URL parameter.
* **Issue Filters**: Fixed the agent filter listing agents that do not apply to the selected view.
* **Slack Commands**: Fixed a single `!agent` command producing an error when the message also contained a link with display text.
* **Slack Mentions**: Fixed mention tokens appearing inside code formatting, which prevented Slack from notifying the referenced person.
* **GitHub Credentials**: Fixed expired GitHub credentials interrupting long-running agent sessions. Cleric refreshes tokens before the expiration time reported by the GitHub API.
* **Metric Aggregation**: Fixed per-entity metrics, such as per-pod gauges, being summed and reported as a single fleet-wide value. Cleric now selects aggregation based on what the metric measures and treats partially ingested trailing data points as incomplete.
* **Improved Integration Reliability**: Fixed common tool error patterns in the Linear, Sentry, Grafana, Loki, and Prometheus integrations.

## June 2026

**New Features**

* **Live Hypotheses**: While an investigation runs, Cleric now shows the hypotheses it is actively testing, in both Slack and the web app, so you can see where it is headed before it reaches a conclusion. In Slack the hypotheses update in place and link back to the full view in the web app.
* **Proactive Resolution Updates**: When Cleric verifies that an issue has resolved, it posts an update to the Slack thread and adds a ✅ reaction to the root message. If the issue reopens, Cleric removes the reaction.
* **Service Dependency Map**: The Services page has a new Map tab that shows how your services depend on one another, built from Cleric's service catalog. Search for a service to focus the map on it and its request flow.
* **Investigations View**: The Issues page now opens on a new Investigations tab, which lists Cleric's deep investigations grouped by status: Investigating, Inconclusive, Fix suggested, Monitoring, and Resolved. Switch to the All issues tab for every issue, including those handled by custom agents.
* **Search Knowledge from your IDE**: The Cleric MCP server adds a `search_knowledge` tool. Your coding agent can now query Cleric's knowledge base: saved memories and extracted facts. See [MCP Server](/integrations/mcp.md).
* **New integrations**:
  * **Amplitude**: Give Cleric read-only access to event volumes, active and new user counts, segmentation, saved charts, and annotations. Cleric can compare these against an investigation's time window.
  * **Unleash**: Give Cleric read-only access to feature flags, their per-environment state, activation strategies, and change history, so it can check whether a flag changed around the time an alert fired. Self-hosted instances are supported.

**Bug Fixes**

* **Activity Log Timing**: Fixed per-tool durations in the activity log so each tool call reflects the time it actually took.
* **Datadog Connection Test**: Fixed the Datadog connection test to validate the application key in addition to the API key. Misconfigured keys now fail at setup.
* **Atlassian Connection Test**: Fixed the Atlassian connection test to validate the API token before saving the integration.

## May 2026

**New Features**

* **Define your own Cleric workflows with Automations**: Until now Cleric ran one built-in investigation on every alert. You can now define multiple named agents, each with its own instructions, and control when each one runs with triggers. Route matching alerts to an agent with channel-scoped keyword triggers, run agents on a recurring schedule, or run any agent on demand with `!agent-name`.
* **See and manage what Cleric knows with Knowledge**: Everything Cleric has learned or been taught about your environment now lives in one place in the web app. This brings together memories, facts Cleric picks up about your environment as it works, and the procedures (formerly "Skills") you have taught it.
  * **Topics**: A new background agent indexes your connected data sources and saves durable, human-authored facts (service ownership, runbook pointers, recurring failure patterns) into a queryable knowledge base, reducing the effort you have to spend teaching Cleric directly.
  * **Memories**: A new Knowledge > Memories page lets you search, add, and delete memories. Memories now carry an author, a created date, and a relevance score, so you can see what context has the highest impact on Cleric's responses.
* **Monitor Cleric's calibration status via System Health**: A new System Health page shows the status of Cleric's onboarding and discovery tasks, so you can see how it is learning your environment.
* **New Slack tools**:
  * **Slack Mentions**: Cleric can now @-mention Slack users in its replies. You can instruct Cleric to identify a service owner, the on-call engineer, or the committer of a change, and Cleric will map that person to the right Slack user and notify them.
  * **Post to Slack from web**: While continuing an investigation in the web UI, you can ask Cleric to post its reply in the connected Slack thread.
* **New integrations**:
  * **Cloudflare**: Allow Cleric read-only access to DNS, WAF events, Workers, traffic analytics, load balancers, SSL/TLS, and audit logs.
  * **Linear**: Cleric can now create and reference Linear issues during investigations.
  * **Notion**: Connect Notion and Cleric can search Notion pages and databases during investigations.
  * **Buildkite**: Cleric can now query Buildkite pipelines, builds, jobs, and annotations.

**Bug Fixes**

* **Slack URL Formatting**: Fixed bold emphasis being applied around bare URLs in Slack replies.
* **Budget Messaging**: Fixed the over-budget message to show a friendly reset duration instead of raw values.
* **Cloudflare Token Validation**: Fixed Cloudflare connection tests to use account-scoped endpoints so tokens with account-level permissions validate correctly.

## April 2026

This month focused on getting Cleric's findings into the tools you already use, and on cutting alert noise as coverage grows.

**New Features**

* **Alert Grouping**: Repeat alerts no longer fan out into separate issues. When a new alert in a Slack channel matches a recent issue there, Cleric attaches it to that issue instead of opening a new one. The number of grouped alerts appears in the issues list, along with the affected services.
* **Background Discovery**: Between investigations, Cleric studies your logs and metrics query conventions and applies them during investigations, so it reaches results faster and makes fewer query syntax errors.
* **MCP Server**: Access your Cleric investigation data from your IDE. Connect Claude Code, Cursor, or any MCP client with a personal API key, then search, list, and create issues and pull root cause and evidence into your coding agent. Generate a key under Settings, on the Personal tab. See [MCP Server](/integrations/mcp.md).
* **Citations in Slack**: When the cited sources are available, Cleric now links to them in its Slack responses, the same as in the web app.
* **Issue Slugs**: Every issue now carries a short, human-readable ID like `ISS-3912`, so you can reference a specific investigation in chat or a ticket.
* **New Relic Integration**: Cleric can now query New Relic logs, metrics, traces, alerts, and entities during investigations, through NerdGraph and NRQL.
* **Sentry Integration**: With Sentry connected, Cleric can inspect issues, events, stack traces, releases, and project-level error patterns during investigations.

**Bug Fixes**

* **Memory Proposals**: Fixed memory proposals being truncated in the UI, so you can read the full proposal before accepting it.
* **Web Follow-ups**: Fixed web follow-up messages timing out. Cleric processes them in the background now instead of returning a 504.
* **Login Errors**: When sign-in fails, the page now displays the reason instead of a raw error response.

## March 2026

**New Features**

* **Contextual Responses**: Cleric now responds to thread replies without an explicit `@Cleric` mention when it's part of the conversation. Disable per thread with `@Cleric mute`.
* **Scheduled Follow-ups**: Schedule the agent to check back on an issue at a specific time. Results post to your Slack thread automatically. See [Common Use Cases](https://github.com/ClericHQ/cleric-core/tree/main/docs/public/investigation/common-use-cases/README.md#monitoring-production) for examples.
* **Stop Slack Command**: You can now type `@Cleric stop` to interrupt a running investigation from Slack.
* **MongoDB Atlas Integration**: Cleric can now query your MongoDB Atlas databases during investigations.
* **Splunk Integration**: Cleric can now search and analyze your Splunk logs during investigations.

**Bug Fixes**

* **Follow-up Quality**: Follow-up responses now require evidence-based reasoning before drawing conclusions, reducing unsupported answers.
* **Agent Recovery**: Fixed a bug where agents interrupted mid-investigation could not resume follow-up interactions.

## February 2026

This month focused on investigation transparency and interactive follow-up. Citations moved to general availability with direct links to data sources, memory tools are enabled for all customers, and Slack investigations gained new interactive follow-up buttons.

**New Features**

* **Citations**: Added citation links to investigation results referencing the specific data sources consulted.
* **Past Issues**: Added search over past investigations when analyzing new issues. Cleric references prior investigations to identify recurring patterns.
* **Memory Tools**: Added explicit save and delete memory tools during investigations. You can now tell Cleric to "remember" and "forget".
* **Dynamic Follow-up Prompts**: Added dynamic context-specific prompt suggestions to investigation responses in both web and Slack.
* **Copy Investigation Summary**: Added a copy button to the issue view in the web, so you can easily transfer the investigation summary to your chosen coding agent.
* **Integration Enable/Disable**: Added the ability to enable or disable individual toolkits without removing the integration configuration.
* **Integration Health Status**: Added an integration health status indicator to the sidenav, making it more visible when an integration connection is unhealthy.

## January 2026

This month focused on extensibility and integration expansion, with custom skills for environment-specific workflows, Confluence integration for documentation search, and GitHub Enterprise support for self-hosted instances.

**New Features**

* **Custom Skills**: Added Skills management in the UI to teach Cleric environment-specific knowledge and workflows. Cleric suggests new Skills when it encounters unfamiliar tasks.
* **Confluence Integration**: Added support for searching and analyzing Confluence documentation during investigations.
* **GitHub Enterprise Support**: Added support for self-hosted GitHub Enterprise instances for code analysis in air-gapped or on-premise environments.
* **AWS CloudWatch Skill**: Added CloudWatch metrics and logs analysis to diagnose infrastructure issues on AWS.
* **Slack File Attachments**: Added support for attaching files to Slack messages when providing context for investigations.

**Bug Fixes**

* **Response Previews**: Fixed Slack notification previews to display the agent's response instead of generic placeholder text.
* **Agent State Recovery**: Resolved issues with restoring investigation sessions that could prevent follow-up interactions from working correctly.

## December 2025

This month we focused on resilience and infrastructure expansion. We introduced automatic investigation recovery, expanded cloud infrastructure support with an EKS integration, and improved how alert responses are configured.

**New Features**

* **EKS Integration**: Added support for AWS EKS toolkit to investigate issues in your Kubernetes clusters running on Amazon EKS
* **Alert Processing Rules**: Alert processing rules are now fully configurable with keywords, making it easier to manage which alerts Cleric responds to in Slack

**Bug Fixes**

* **Database Stability**: Resolved connection pool exhaustion issues that could cause service disruptions during high load
* **Slack Feedback Submission**: Fixed errors that prevented feedback modal submissions from completing successfully

## November 2025

This month focused on expanding integration capabilities and improving investigation control. We introduced new cloud infrastructure integrations, enhanced the onboarding experience, and added the ability to interrupt investigations when needed.

**New Features**

* **AWS Integration**: Added support for AWS toolkit with role-based access to EC2, CloudWatch, EKS, and other AWS services for investigating infrastructure issues
* **Cancel Investigation**: You can now pause an in-progress investigation when you no longer need Cleric to continue analyzing an issue
* **Enhanced Onboarding**: New guided signup flow with a 4-step onboarding process makes it easier to get started with Cleric

**Bug Fixes**

* **Follow-up Reliability**: Resolved problems with subagent initialization that could prevent Cleric from responding properly to follow-up questions
* **GitHub Integration Cleanup**: GitHub app is now properly uninstalled from the organization when removing the GitHub toolkit

## October 2025

This month focused on enhancing investigation interactivity and expanding regional support. We introduced a new activity log view for better visibility into investigation progress and enabled follow-up conversations to continue collaborating with Cleric after the initial investigation.

**New Features**

* **Activity Log View**: New interface on the Issue Details page provides a chronological view of all investigation steps, making it easier to understand Cleric's reasoning process and progress
* **Follow-up Interactions**: You can now continue conversations with Cleric in Slack threads after the initial investigation completes, enabling iterative debugging and clarification
* **EU Region Support**: Added AWS Bedrock support so model inference for EU-hosted instances runs on EU infrastructure. See [EU Hosting & Data Processing](/security/eu-hosting-data-processing.md) for where each category of data is processed
* **Enhanced GitHub Integration**: Improved GitHub CLI integration enables more comprehensive code analysis during investigations

**Bug Fixes**

* **Slack Message Formatting**: Fixed errors that occurred when investigation responses exceeded Slack's message length limits by automatically truncating long messages
* **Follow-up Processing**: Resolved issues where alert thread messages with mentions weren't being properly processed, ensuring Cleric responds reliably to all follow-up questions
* **Investigation State Tracking**: Fixed a bug where follow-up interactions weren't correctly updating the investigation state, ensuring all conversation context is preserved

## September 2025

This month focused on enhancing collaboration workflows and improving investigation reliability. We introduced new ways to interact with Cleric directly in Slack and streamlined the integration setup process.

**New Features**

* **Slack Response Interaction**: You can now interact directly with Cleric's investigation responses in Slack, making it easier to collaborate and provide feedback without switching contexts
* **GitHub App Integration**: New streamlined GitHub app installation flow simplifies connecting your repositories for code analysis during investigations
* **All Observations Tab**: Added a dedicated tab to the Issue Details page to view all observations collected during an investigation in one place

## August 2025

With this update we shipped a handful of small security enhancements and experience improvements. Most updates were internal infrastructure, testing, or development workflow changes that don't affect customers directly.

**New Features**

* **Enhanced Investigation Display**: Streamlined the observations view with improved hypotheses and evidence presentation for clearer investigation results
* **Elasticsearch Integration**: Added log search and analysis capabilities for customers with Elasticsearch deployments
* **Enhanced Security**: Implemented HTTP security headers and refresh token support to strengthen authentication and session management

**Bug Fixes**

* **Investigation Error Visibility**: Error messages are now displayed in the UI when Cleric fails to investigate an issue, providing better transparency into investigation status
* **Investigation Confidence**: Resolved over-confidence calculation issues to ensure investigation confidence scores accurately reflect the strength of evidence

## July 2025

July focused on strengthening security, rearchitecting Cleric's initial investigation result, and improving the onboarding experience.

**New Features**

* **Improved Issue Details View**: New Canvas layout that replaces Findings with Hypotheses and Observations. In the UI, you can view Cleric's hypotheses about the issue's potential root cause, and hover over citations to preview the referenced observations.
* **Guided Onboarding Process**: New users now see a progress tracker that shows which integrations need setup and provides clear next steps to get fully configured
* **Enhanced Data Isolation**: We added organization-level access controls as an additional layer on top of our existing tenant isolation to further ensure your investigation data and configurations remain separate from other customers

**Bug Fixes**

* **Authentication Security Update**: Migrated to PyJWT to address CVE-2024-23342, a token validation vulnerability that could potentially affect session security
* **Investigation Confidence**: Resolved calculation errors that could show investigations as less confident than they actually were based on the evidence gathered
* **Investigation Result Display**: Fixed a race condition that would occasionally prevent investigation results from displaying after completion
* **Large Log Processing**: Reduced maximum log processing size to prevent timeouts when analyzing very verbose application logs