Skip to content

FIX Stop Copilot and A2A targets from silently losing conversation history - #3078

Open
Utkarsh Bahuguna (u7k4rs6) wants to merge 7 commits into
microsoft:mainfrom
u7k4rs6:fix/stateful-target-history
Open

Utkarsh Bahuguna (u7k4rs6) wants to merge 7 commits into
microsoft:mainfrom
u7k4rs6:fix/stateful-target-history

Conversation

@u7k4rs6

@u7k4rs6 Utkarsh Bahuguna (u7k4rs6) commented Oct 10, 2026 •

Copy link
Copy Markdown
Contributor

GitHubCopilotTarget and A2ATarget keep the conversation on their side, and a few paths lost it without saying anything. Copilot now raises when a conversation already has turns but no live session, instead of opening a fresh session and sending only the last message. A2A sends its own contextId from the first turn, so turn 2 still continues when the agent doesn't return one, and it switches to the agent's id when it does. Repeat-send now checks that the target can replay the stored history before copying a conversation, so it fails up front instead of answering each copy blind. Richard reworked that last part into validate_history_replay on the target, so configured adapters and restore paths count too.

The new tests fail on main and pass here.

Fixes #3077

Clarify editable-history semantics and check native support, configured adapters, or WebSocket restoration before copying conversation history.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 23cf5e2b-2223-44e3-ab65-252dcc5ce4ee

This branch has not been deployed

No deployments
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.

Copilot and A2A targets lose conversation history without saying so

2 participants