What HolmesGPT/holmesgpt shipped
Written by FoxPlug from the repository's own releases; not affiliated with Holmesgpt. Paste your own repository in the box below and FoxPlug writes the same weekly update for your product. This page is an automatic summary of the releases, pull requests and commits in github.com/HolmesGPT/holmesgpt; Holmesgpt did not write it and does not use or endorse FoxPlug. Every line links to the change it describes.
Get a weekly update like this for your product, free
Week of October 5, 2026
What shipped
- Released version 0.43.0, which brings constraints on impact claims in the narrative to observed evidence, binds conversation worker identity to the Conversations row owner, and documents baseline setup, among other changes. Release
- Fast mode is now the default, with TodoWrite planning made opt-in. Pull request #2471
- The auto executor now defaults to running one conversation at a time instead of two, so background work such as auto-triage, bulk investigations and triggered workflows no longer runs concurrently with itself. Pull request #2566
- Conversations now run on named executors, manual and auto, separating live user chats from alert-triage investigations and triggered workflows. Pull request #2482
- Added per-user Dex auth for the Kubernetes MCP addon with private CA support, and documented a Per-User Auth with Dex (OIDC) section on the Kubernetes MCP page. Pull request #2554
- The model cost map now refreshes when a model lookup misses, so a model released while Holmes is running does not sit on the fallback 200K context window, 64K max output and zero cost until a restart. Pull request #2553
- Robusta models whose upstream name is not provider/id are now priced, fixing
total_coststaying zero in Holmes usage. Pull request #2546 - Free-form object parameters are kept out of strict tool calls instead of being closed with additionalProperties false, which under strict decoding only admitted an empty object. Pull request #2544
- A toolset can now set its own status refresh interval, instead of Holmes re-checking every enabled toolset on each periodic refresh. Pull request #2539
- The deprecated FastAPI shutdown handler was replaced with lifespan, removing the DeprecationWarning logged at import time in every Holmes pod. Pull request #2535
Why it matters
This week brought release 0.43.0 along with changes that affect how conversations run day to day: fast mode is now the default, the auto executor runs one conversation at a time, and conversations run on named executors that separate user chats from alert triage. The Kubernetes MCP addon gained per-user Dex auth with private CA support, and several fixes make usage pricing and tool calls more reliable.
Changelog entry
- Release 0.43.0. Release
- Made fast mode the default; TodoWrite planning is now opt-in. Pull request #2471
- Defaulted the auto executor to one conversation at a time. Pull request #2566
- Run conversations on named executors for manual chats and auto triage. Pull request #2482
- Added per-user Dex auth for the Kubernetes MCP addon with private CA support. Pull request #2554
- Refreshed the model cost map when a model lookup misses. Pull request #2553
- Priced Robusta models whose upstream name is not provider/id. Pull request #2546
- Handled multi-choice responses by merging choices before processing. Pull request #2556
- Kept free-form object parameters out of strict tool calls. Pull request #2544
- Let a toolset set its own status refresh interval. Pull request #2539
- Replaced the deprecated FastAPI shutdown handler with lifespan. Pull request #2535
- Added an advanced benchmark tier and fixed test namespace conflicts. Pull request #2548
Holmes 0.43.0 is out. Fast mode is now the default, the auto executor runs one conversation at a time, and conversations run on named executors for manual chats and auto triage. Per-user Dex auth for the Kubernetes MCP addon is documented. Details in the repo.
Holmes 0.43.0 is out this week. Fast mode is now the default and TodoWrite planning is opt-in. The auto executor defaults to one conversation at a time, so background triage, bulk investigations and triggered workflows no longer run concurrently, and conversations now run on named executors that separate live user chats from alert-triage work. The Kubernetes MCP addon gained per-user Dex auth with private CA support, with setup documented on the MCP page. On the reliability side, the model cost map refreshes on a lookup miss so recently released models are priced while Holmes is running, Robusta models whose upstream name is not provider/id are now priced, and free-form object parameters are kept out of strict tool calls.
Week of September 28, 2026
What shipped
- Removed the kubectl-run toolset after all runs in the last 90 days failed across six accounts. Pull request #2532
- Fixed a security issue where /eval and /list endpoints were not gated on repository permissions, allowing PR comments to execute with full secret access. Pull request #2530
- Fixed TLS certificate validation failure when using pyOpenSSL >= 26.2 with the SQL Server connector. Pull request #2505
- Added X-Robusta-Model header to platform MCP calls so the Robusta Alert Triage drawer can display which model investigated an alert. Pull request #2506
- Added automated tests to enforce consistent deployment tab formatting across all model provider and data source documentation pages. Pull request #2516
- Fixed documentation examples that failed when followed as written, including invalid Helm values keys and rejected configurations. Pull request #2507
- Standardized deployment tab layouts on all model provider pages so readers see consistent steps across every page. Pull request #2508
- Standardized deployment tab layouts on observability and ticketing data source pages. Pull request #2513
- Standardized deployment tab layouts on all database connector pages. Pull request #2514
- Converted deployment and multi-instance documentation fences to markdown format. Pull request #2510
Why it matters
This week focused on fixing security issues and improving documentation consistency. The security fix for /eval endpoints prevents unauthorized code execution from pull request comments, while the widespread documentation standardization ensures readers follow the same reliable steps regardless of which integration they're setting up.
Changelog entry
- Removed kubectl-run toolset due to consistent failures Pull request #2532
- Security: gated /eval and /list endpoints on repository permissions to prevent unauthorized code execution Pull request #2530
- Added X-Robusta-Model header to platform MCP calls for alert triage integration Pull request #2506
- Fixed SQL Server connector TLS certificate validation with pyOpenSSL >= 26.2 Pull request #2505
- Added automated tests for deployment tab format consistency in documentation Pull request #2516
- Fixed documentation examples that failed when followed as written Pull request #2507
- Standardized deployment tab layouts on model provider pages Pull request #2508
- Standardized deployment tab layouts on observability and ticketing pages Pull request #2513
- Standardized deployment tab layouts on database pages Pull request #2514
- Converted deployment documentation fences to markdown format Pull request #2510
This week: fixed a security issue in /eval and /list endpoints, removed the broken kubectl-run toolset, fixed SQL Server TLS validation, and standardized deployment documentation across 40+ integration pages.
This week's updates to HolmesGPT focused on security and documentation reliability. We fixed a critical issue where /eval and /list endpoints weren't properly gated on repository permissions, removed the kubectl-run toolset after consistent failures, resolved TLS certificate validation problems with pyOpenSSL 26.2, and standardized deployment instructions across 40+ integration pages to ensure readers get consistent, working steps every time.
Week of September 21, 2026
What shipped
- Bash parsing now requires approval for complex syntax including loops, conditionals, and case statements, with dangerous arguments and write redirects checked regardless of parseability. Pull request #2500
- Six Critical/High CVEs in grpc, x/crypto, and Helm dependencies were patched in the Holmes image. Pull request #2494
- The agent now respects account-level opt-out settings that prevent data from reaching hosted models. Pull request #2486
- Kubernetes-remediation MCP image was upgraded from 1.3.0 to 1.4.0. Pull request #2481
- Bash toolset documentation now shows actual allow-list prefix examples and explains scoping options. Pull request #2495
Why it matters
This week brings security hardening for bash command execution, vulnerability patches in core dependencies, and better alignment between the agent and platform settings. Documentation improvements make bash configuration clearer for users.
Changelog entry
- Bash commands with loops, conditionals, and case statements now require approval; dangerous arguments and write redirects are checked even when parsing fails Pull request #2500
- Patched six Critical/High CVEs in grpc, x/crypto, and Helm dependencies Pull request #2494
- Agent now reads and enforces account-level opt-out settings for hosted models Pull request #2486
- Bumped kubernetes-remediation MCP image to 1.4.0 Pull request #2481
- Bash toolset documentation now shows real allow-list prefix examples and scoping options Pull request #2495
Bash approval rules tightened for complex syntax. Six CVEs patched. Account opt-out settings now honored. kubernetes-remediation MCP 1.4.0. Bash docs clarified.
This week's HolmesGPT updates focus on security and reliability. Bash command execution now requires approval for complex syntax patterns. Six Critical/High CVEs in dependencies were resolved. The agent respects account-level opt-out settings for hosted models. kubernetes-remediation MCP upgraded to 1.4.0. Bash toolset documentation improved with real prefix examples.
Week of September 14, 2026
What shipped
- Fixed command injection vulnerability where propagated HTTP headers bypassed parameter sanitization in the YAML tool shell. Pull request #2467
- Fixed privilege escalation where conversation worker identity was not bound to the Conversations row owner. Pull request #2480
- Constrained impact claims in narratives to observed evidence, removing invented consequences from failure analysis. Pull request #2449
- Removed kube-lineage entirely from the repository as part of dependency cleanup. Pull request #2464
- Hardened kubernetes-remediation file-read policy defaults in the Helm chart to restrict auto-approved container file reads. Pull request #2479
- Fixed Coralogix UI permalinks to use the correct team UI hostname for US2 and other regions. Pull request #2474
- Added GPU node diagnostics support to kubernetes-remediation MCP for debugging GPU nodes without GPU allocation. Pull request #2462
- Added namespaceScopedRBAC Helm value to support namespace-scoped Holmes installations. Pull request #2469
- Added configurable request timeout for New Relic toolset via
timeout_secondsparameter. Pull request #2457 - Stopped the LLM from claiming a rejected command is awaiting approval when approval flow is unavailable. Pull request #2461
Why it matters
This week addresses multiple security issues including command injection and privilege escalation vulnerabilities. The fixes improve reliability of failure analysis by constraining claims to observed evidence, and expand capabilities with GPU diagnostics and regional support for observability platforms.
Changelog entry
- Security: Fixed command injection in propagated HTTP headers reaching YAML tool shell (CWE-78) Pull request #2467
- Security: Fixed privilege escalation where conversation worker identity was not bound to row owner (CWE-639/862/863) Pull request #2480
- Security: Hardened kubernetes-remediation file-read policy defaults in Helm chart (ROB-973) Pull request #2479
- Improved failure narratives to constrain impact claims to observed evidence only Pull request #2449
- Added GPU node diagnostics support to kubernetes-remediation MCP Pull request #2462
- Added namespaceScopedRBAC Helm value for namespace-scoped installations Pull request #2469
- Fixed Coralogix UI permalinks for US2 and other regions Pull request #2474
- Added configurable request timeout for New Relic toolset Pull request #2457
- Fixed LLM messaging when tool approval is not available Pull request #2461
- Removed kube-lineage dependency from repository Pull request #2464
- Documented Baseten Model APIs as a provider Pull request #2483
0.42.0 ships security fixes for command injection and privilege escalation, hardened file-read policies, GPU diagnostics, and corrected failure analysis to constrain claims to evidence.
0.42.0 is out. This release hardens security with fixes for command injection and privilege escalation vulnerabilities, tightens file-read policy defaults, adds GPU node diagnostics, supports namespace-scoped deployments, and improves failure narratives by constraining claims to observed evidence only.