> For the complete documentation index, see [llms.txt](https://docs.ilert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ilert.com/changelog/2026/august-2026.md). # August 2026 ### New features and improvements * 🎉 **Dark mode** 🌙 has arrived for the web UI — after porting almost the entire web app to our new frontend stack, ilert now comes in a dark theme * 🎉 We launched the **ilert CLI** — open source at [github.com/iLert/ilert-cli](https://github.com/iLert/ilert-cli) and a power-house in combination with your favorite coding agent. It ships with migration skills that help you move your setup from **PagerDuty** or **Opsgenie** to ilert * **Declared incidents can now create their own Slack, Microsoft Teams and Google Chat channels**, just like alerts could * The **Incident Compass** now also shows what has already been done on an incident, not only the next steps * **AI SRE** can now hand over straight into incident response: from a conversation or root cause analysis, it previews a declared incident for you, creates it on confirmation, moves the chat over to the incident and links the RCA * You can now **stop AI SRE investigations** mid-run and continue with more context, and agents show their thinking state between tool calls. New users get guidance when creating their first agent * We added a **PostgreSQL MCP server** to the ilert MCP Connector, giving your AI SRE agents access to your PostgreSQL databases * Recurring on-call schedules can now **follow a support hour**, so your schedule layers automatically respect its weekly windows and **holidays** * **Services support multiple aliases**, and so do routing keys in alert source routing * When a service's internal status differs from its public status, the service edit view now flags it and lets you **publish the diverged status** right away * The alert list has new **Severity** and **Affected Services** filters, and **High and Low priority alerts** are now easier to tell apart at a glance * In the alert detail view, **alert tags are shown inline** next to the description, and ilert remembers whether you last looked at the **Timeline or Comments** tab * **User pickers now also search by email address**, across the web app and the mobile apps * The call flow **route call node** can now **target teams** * Accepting or resolving alerts from **Slack and Microsoft Teams** now respects the user's ilert role, whenever the chat user is also an ilert user * Mobile: long-press the ilert app icon for **quick actions** (iOS Home Screen actions and Android app shortcuts), and choose to **open external links in your default browser** instead of the in-app browser ### Integration updates * We have introduced a new inbound integration: **DBmarlin** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.ilert.com/changelog/2026/august-2026.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.