Sprint 213: Auto Update base Agents — merge feature/CODUX-213-auto-update-base-agents into dev - #2923
Merged
Merged
Conversation
…ex-baab3822-mrg6ceu5 (CODUX-120) Persist base-agent baselines and detect revisions
…ex-1761f29d-mrg6xqj5 (CODUX-120) Add guarded provider-assisted base updates
…ex-d848d559-mrg7nmyu (CODUX-120) Render base-agent update notices
…ex-5691d9d9-mrg85se2 (CODUX-120) Document base-agent update behavior
Merged
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.
🚀 Sprint Completion: Sprint 213 · Auto Update base Agents
📋 Summary
Sprint: Sprint 213 · Auto Update base Agents Tasks: 4/4 completed
🔗 Linked Issues
🧭 Planning
gpt-5.6-lunaIncluded usage estimate (subscription/local login): $2.51
🎯 Original Sprint Prompt
Linked Issues
Use these imported issue details as sprint scope. Preserve acceptance criteria, constraints, and user-reported context. Close linked issues only after the sprint is finished and merged.
JIRA CODUXCODUX-120: Check for updated base Agent Instructions
Issue Body
We need to implement a check for updated base Agent instructions especially Project Manager and Planning Agent. If one of these 2 got updated we will auto update the users Agent as long as he didnt manually change it. If the user did manually change it or uses a different dashboard_reply or planning agent then we need to show a notice on the Agents Page that one of these base Agents got updated and the user can and should update his specific Agent (Project Manager or Planning Agent) to apply changes from those changes - Explain that this will invoke an agent to compare both files and just apply important instructions that are needed for system compability and doesnt changes the users main prompt or custom instructions - the invocation also needs these instructions to not touch any of the users custom instructions or behaviour but just change important system instructions like changed mcp or json schema instructions and things like that.
✅ Task Checklist
codex(PR)codex(PR)codex(PR)codex(PR)👥 Provider Breakdown
4 by codex
⏱️ Sprint Timing
📊 Aggregate CLI Token Usage
Included usage estimate (subscription/local login): $15.26
🕵️ QA Review Summary
Outcome: pass
Sprint integration passes. Focused tests, dashboard suite, lint, build, docs checks, guardrails, and live dashboard smoke test passed; one unrelated Docker-dependent backend test was unavailable.
🌿 Branch Info
Base:
devHead:
feature/CODUX-213-auto-update-base-agents🤖 Generated by Code UX