Skip to content

Sprint 213: Auto Update base Agents — merge feature/CODUX-213-auto-update-base-agents into dev - #2923

Merged
numnx merged 8 commits into
devfrom
feature/CODUX-213-auto-update-base-agents
Jul 11, 2026
Merged

Sprint 213: Auto Update base Agents — merge feature/CODUX-213-auto-update-base-agents into dev#2923
numnx merged 8 commits into
devfrom
feature/CODUX-213-auto-update-base-agents

Conversation

@numnx

@numnx numnx commented Jul 11, 2026

Copy link
Copy Markdown
Collaborator

🚀 Sprint Completion: Sprint 213 · Auto Update base Agents

Automated sprint completion PR opened by Code UX.

📋 Summary

Sprint: Sprint 213 · Auto Update base Agents Tasks: 4/4 completed

🔗 Linked Issues

  • Jira CODUX-120: Check for updated base Agent Instructions

🧭 Planning

Planning provider Codex CLI
Planning model gpt-5.6-luna
Metric Value
Input tokens 1,274,244
Cached input tokens 9,160,704
Output tokens 53,878
Total tokens 10,488,826
Invocations 8
Tool calls 107
Active time 25m 9s

Included 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

  • T01: Persist base-agent baselines and detect revisions — codex (PR)
  • T02: Add guarded provider-assisted base updates — codex (PR)
  • T03: Render base-agent update notices — codex (PR)
  • T04: Document base-agent update behavior — codex (PR)

👥 Provider Breakdown

4 by codex

⏱️ Sprint Timing

Started 2026-07-11 09:40:11 UTC
Finished 2026-07-11 10:47:11 UTC
Duration 1h 7m 0s

📊 Aggregate CLI Token Usage

Metric Value
Input tokens 2,092,952
Cached input tokens 28,058,624
Output tokens 138,419
Total tokens 30,289,995
Invocations 13
Tool calls 318
Active time 1h 3m 16s

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: dev
Head: feature/CODUX-213-auto-update-base-agents


🤖 Generated by Code UX

Code UX and others added 8 commits July 11, 2026 09:52
…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
@numnx
numnx merged commit 6504716 into dev Jul 11, 2026
40 checks passed
@numnx
numnx deleted the feature/CODUX-213-auto-update-base-agents branch July 11, 2026 10:51
@numnx numnx mentioned this pull request Jul 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant