# Changelog Every month, we update this changelog with the major features and bug fixes that were shipped to our customer environments. ## 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/blob/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](/learning/skills.md) 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 for customers requiring EU-based infrastructure for data residency compliance * **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 --- # 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://docs.cleric.ai/reference/changelog.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.