How cyberpradeep/elone_agent works
This repository implements a LangGraph support-ticket agent: it collects or clarifies ticket details, retrieves a matching SOP, plans and validates actions, executes steps through provider tools, checks outcomes, and produces a response or escalation. main_graph.py establishes intake as the entry point; agents then use state updates and dynamic routing. The map also shows the tool-provider layer and shared LLM configuration. Evidence is limited to the supplied excerpts and SOURCE INDEX; unsampled behavior and some routing details are not asserted.
Main entry points: orchestration/node.py Orchestration agent · llm_config.py LLM configuration · retrieval/node.py SOP retrieval · tool_catalog.py Tool catalog
Components 22
Workflow control
- Workflow graph
main_graph.py - Support state
shared/state.py - Orchestration agent
agents/orchestration/node.py - Workflow router
agents/orchestration/router.py
Ticket processing
- Ticket intake
agents/intake/node.py - SOP retrieval
agents/retrieval/node.py - Qdrant index
Plan and execution
- Execution planning
agents/execution_planning/node.py - Plan validation
agents/plan_validator/node.py - Step execution
agents/execution/node.py - Tool dispatch
agents/execution/dispatch.py - Outcome evaluation
agents/execution_result/node.py - Human escalation
agents/escalation/node.py - Resolution summary
agents/summarization/node.py
Shared integrations
- Tool catalog
shared/tool_catalog.py - Mock provider
shared/providers/mock.py - Auth0 provider
shared/providers/auth0.py - System operations
shared/providers/system_ops.py - LLM configuration
shared/llm_config.py
Other components
- Ticket submitter
- LLM services
- Auth0 service
Connections 31
- Ticket submitter → Workflow graph: submits ticket
- Workflow graph → Ticket intake: starts at
main_graph.py - Ticket intake → SOP retrieval: routes to
agents/intake/node.py - SOP retrieval → Qdrant index: queries index
agents/retrieval/node.py - Ticket intake → Qdrant index: loads intents
agents/intake/node.py - SOP retrieval → Orchestration agent: routes to
agents/retrieval/node.py - Orchestration agent → Workflow router: selects route
agents/orchestration/node.py - Orchestration agent → SOP retrieval: routes to
- Orchestration agent → Execution planning: routes to
- Orchestration agent → Plan validation: routes to
- Orchestration agent → Step execution: routes to
- Orchestration agent → Human escalation: routes to
- Execution planning → Orchestration agent: returns plan
agents/execution_planning/node.py - Step execution → Tool dispatch: calls tool
agents/execution/node.py - Tool dispatch → Tool catalog: uses catalog
agents/execution/dispatch.py - Execution planning → Tool catalog: selects tools
agents/execution_planning/node.py - Tool catalog → Mock provider: registers tools
shared/tool_catalog.py - Tool catalog → Auth0 provider: registers tools
shared/tool_catalog.py - Tool catalog → System operations: registers tools
shared/tool_catalog.py - Step execution → Orchestration agent: returns result
agents/execution/node.py - Outcome evaluation → Orchestration agent: returns decision
agents/execution_result/node.py - Orchestration agent → Outcome evaluation: routes to
- Orchestration agent → Resolution summary: routes to
- Orchestration agent → Support state: updates state
- Ticket intake → LLM configuration: gets model
agents/intake/node.py - SOP retrieval → LLM configuration: gets model
agents/retrieval/node.py - Execution planning → LLM configuration: gets model
agents/execution_planning/node.py - Outcome evaluation → LLM configuration: gets model
agents/execution_result/node.py - Resolution summary → LLM configuration: gets model
agents/summarization/node.py - LLM configuration → LLM services: builds clients
shared/llm_config.py - Auth0 provider → Auth0 service: calls API
shared/providers/auth0.py