(feat-redraw)MVP for dynamic graph rendering with feature parity#657
Merged
Conversation
Remove the static-id-map early return so the agentic graph always renders from backend topology: always apply and refetch on SSE, highlight only in the dynamic React Flow id namespace, and patch transport-name labels on dynamic nodes/edges via the new dynamicTransportLabels helper. Co-authored-by: Cursor <cursoragent@cursor.com> Signed-off-by: pdobrei <pdobrei@cisco.com> Co-authored-by: Cursor <cursoragent@cursor.com>
Resolve recruiter/directory stream authors and the auction animation sequence through a canonical node slug (getOasfSlugFromNodeData) so chat highlighting targets live API-driven ids instead of authored NODE_IDS/ EDGE_IDS. useMainArea now translates the static animation sequence to live ids when the graph is API-owned; feeds remain unchanged. Co-authored-by: Cursor <cursoragent@cursor.com> Signed-off-by: pdobrei <pdobrei@cisco.com> Co-authored-by: Cursor <cursoragent@cursor.com>
The static id map is unused since the renderer switched to live API topology; full static-config/NODE_IDS teardown is deferred pending the non-agentic fallback and discovery-overlay decisions. Co-authored-by: Cursor <cursoragent@cursor.com> Signed-off-by: pdobrei <pdobrei@cisco.com>
…ream highlight Use isDirectoryLabel from agenticTopologyIdentityUiMap in nodeSlugKey instead of the inlined agntcy/agent-directory heuristic, completing the label-predicate centralization for the live chat-stream highlight path. Co-authored-by: Cursor <cursoragent@cursor.com> Signed-off-by: pdobrei <pdobrei@cisco.com>
13 tasks
delthazor
changed the title
This was referenced Jun 23, 2026
mihaialexandrescu
previously approved these changes
Jun 26, 2026
delthazor
dismissed stale reviews from mihaialexandrescu, misi-bp, and pregnor
The base branch was changed.
pregnor
approved these changes
Jul 1, 2026
misi-bp
approved these changes
Jul 1, 2026
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
4 participants
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.
Description
Replaces the statically defined graph drawing with a dynamic, backend data driven one.
The change contains extra changes to reach minimal feature parity for animations, test coverage, and A2A representation of SSE processing.
Topology graphs should be rendered dynamically based on backend provided data. This was partially done before, but was mostly reverted, due to stylistic and structural reasons, e.g.: specific icons were not rendered correctly, nodes not appearing as they should, etc.
This change aims to (re-)introduce the MVP version of the backend-driven dynamic graph rendering, this time with feature parity, and correct representation. For this, a previous PR already defines necessary node data resolvers the current code aims to use for the required graph representation quality.
This PR is not a standalone change, it is a part of a chain of smaller changes reviewed independently.
The previous PR, this one immediately depends on:
#656
The follow-up PR is here:
#658
Other corresponding PRs:
#659
#661
#663
Issue Link
No specific issue was opened for the change.
Type of Change
Checklist