feat(agents): port eval-tuned muster prompt into sre-agent systemMessage#182
Merged
Conversation
Give the bundled sre-agent the same muster meta-tool contract that was eval-tuned for the Backstage devportal AI chat (giantswarm/backstage#1775): prefer a single-call workflow_<name> discovered via filter_tools(query=…), the exact x_kubernetes_* argument contract (management_cluster: <mc>-mcp-kubernetes, resourceType, podName, tailLines), and the cheap-listing recipe. The agent shares muster's meta-tool interface with the devportal chat, so the same guidance cuts wrong-arg retries and avoidable tool round trips. Clusters that enable the agent without overriding systemMessage (e.g. glean) inherit the improved default. Co-authored-by: Cursor <cursoragent@cursor.com>
2 tasks
teemow
added a commit
that referenced
this pull request
Jun 23, 2026
#183) PR #182 updated only the connectivity sub-chart's default systemMessage, but the umbrella agentic-platform chart forwards its OWN values to the connectivity HelmRelease via forwardAllValues — so in meta-package installs (every deployed cluster, e.g. glean) the umbrella copy shadows the sub-chart default and the prompt change never reached the agent. Apply the identical prompt to helm/agentic-platform/values.yaml and add a reciprocal keep-in-sync note to both files. Co-authored-by: Cursor <cursoragent@cursor.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
sre-agent's defaultsystemMessage.filter_tools/describe_tool/call_toolwrappingx_kubernetes_*/x_prometheus_*) as the devportal chat, so the same guidance applies: prefer a single-callworkflow_<name>(discovered viafilter_tools(query=…)), the exactx_kubernetes_*argument contract (management_cluster: <mc>-mcp-kubernetes,resourceType,podName,tailLines), and the cheap-listing recipe (summary,fieldSelector: status.phase!=Running,reason=BackOfffor CrashLoopBackOff).systemMessage(e.g. glean) inherit the improved default.Why
The devportal eval showed this contract eliminates wrong-argument retries (missing/bare
management_cluster,name→podName,tail→tailLines,kind→resourceType) and the mid-task schema-discovery tax, and steers single-call workflow resolution where a workflow exists. The sre-agent talks to the same muster aggregator, so it benefits from the identical steer.Test plan
helm templaterenders thesre-agentAgent CR with the newsystemMessage(correct YAML block scalar / nindent).values.yamlis valid YAML.Made with Cursor