Graph Routing Based On User Input #3

Open
opened 2025-09-30 10:10:17 +00:00 by aditya · 0 comments
Member

Description
As a user, I want graph routing to evaluate my original input correctly so that agents respond to what I actually said, not their own responses. Graph edge conditions should evaluate against the user's original message content, not agent responses, ensuring accurate routing based on user intent and input.

Acceptance Criteria

  • Edge conditions check the last user message (role: "user") for routing decisions
  • content_contains and content_not_contains ignore agent response content
  • Routing logic prioritizes user commands and topics over system-generated text
  • Agent transitions occur based on actual user input patterns

Definition of Done

  • Node.evaluate_edge_condition() filters messages by role: "user"
  • Edge evaluation logic separates user input from agent output
  • Routing tests verify conditions against user messages only
  • Graph flows follow user intent rather than agent response content
**Description** As a user, I want graph routing to evaluate my original input correctly so that agents respond to what I actually said, not their own responses. Graph edge conditions should evaluate against the user's original message content, not agent responses, ensuring accurate routing based on user intent and input. **Acceptance Criteria** - Edge conditions check the last user message (role: "user") for routing decisions - content_contains and content_not_contains ignore agent response content - Routing logic prioritizes user commands and topics over system-generated text - Agent transitions occur based on actual user input patterns **Definition of Done** - Node.evaluate_edge_condition() filters messages by role: "user" - Edge evaluation logic separates user input from agent output - Routing tests verify conditions against user messages only - Graph flows follow user intent rather than agent response content
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: cleveragents/cleveragents-core#3
No description provided.