fix(agents): apply eval-tuned muster prompt to the umbrella values too#183
Merged
Conversation
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
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
Follow-up to #182. That PR updated only
helm/agentic-platform-connectivity/values.yaml, but the umbrellaagentic-platformchart forwards its own values tree to theagentic-platform-connectivityHelmRelease viaforwardAllValues. In meta-package installs (every deployed cluster, e.g. glean) that umbrella copy shadows the connectivity sub-chart default, so #182's change never reached the runningsre-agent.This applies the identical eval-tuned muster prompt to
helm/agentic-platform/values.yamland adds a reciprocal keep-in-sync note to bothvalues.yamlfiles.Verified
helm template helm/agentic-platform --set agents.definitions.sre-agent.enabled=truenow renders the newsystemMessage(Prefer a workflow, thex_kubernetes_*contract, cheap-listing) inside the forwardedagentic-platform-connectivityHelmReleasespec.values.spec.values.agents.definitions.sre-agent.systemMessagewas the old text despite reconciling connectivity1.15.0(which feat(agents): port eval-tuned muster prompt into sre-agent systemMessage #182 fixed) — because the umbrella forwards its own copy.Test plan
values.yamlare valid YAML; umbrella render carries the new prompt into the forwarded values.kubectl get agent sre-agent -n kagent -o jsonpath='{.spec.declarative.systemMessage}'shows the workflow/contract guidance.Made with Cursor