Skip to content

fix(ui): store evolving code messages under short key for downstream consumers#1373

Open
JasonOA888 wants to merge 1 commit intomicrosoft:mainfrom
JasonOA888:fix/issue-1021-evolving-code-ui
Open

fix(ui): store evolving code messages under short key for downstream consumers#1373
JasonOA888 wants to merge 1 commit intomicrosoft:mainfrom
JasonOA888:fix/issue-1021-evolving-code-ui

Conversation

@JasonOA888
Copy link
Copy Markdown

@JasonOA888 JasonOA888 commented Apr 1, 2026

Fixes #1021

The get_msgs_until function stores messages under state.msgs[lround][msg.tag], where msg.tag is the full tag string (e.g. "development.evoving code"). However, downstream consumers read from state.msgs[round]["evolving code"] (lines 474, 476, 700), which never gets populated.

This fix explicitly appends evolving code messages under the short "evolving code" key so the UI can display them correctly.

Changes:

  • In the "evolving code" in tags branch of get_msgs_until, also append to state.msgs[lround]["evolving code"]

Testing:

  • Manually verified the fix produces the expected behavior described in the issue

📚 Documentation preview 📚: https://RDAgent--1373.org.readthedocs.build/en/1373/

…consumers

Messages tagged with 'evolving code' were stored under the full msg.tag
key (e.g. 'development.evoving code') but downstream code reads from
state.msgs[round]['evolving code']. This caused the UI to always show
an empty evolving code list.

Fixes microsoft#1021
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.

handling of "evolving code" in get_msgs_until

1 participant