<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: VIBHEESHAN NK</title>
    <description>The latest articles on DEV Community by VIBHEESHAN NK (@techsmart).</description>
    <link>https://dev.to/techsmart</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4161934%2F3dcf35a8-6b42-47f4-a145-2f41ca3025a4.png</url>
      <title>DEV Community: VIBHEESHAN NK</title>
      <link>https://dev.to/techsmart</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/techsmart"/>
    <language>en</language>
    <item>
      <title># How I Used Switch to Build AgriCommand AI: Five AI Agents Collaborating for Smarter Agriculture</title>
      <dc:creator>VIBHEESHAN NK</dc:creator>
      <pubDate>Sat, 07 Nov 2026 14:10:09 +0000</pubDate>
      <link>https://dev.to/techsmart/-how-i-used-switch-to-build-agricommand-ai-five-ai-agents-collaborating-for-smarter-agriculture-2h4i</link>
      <guid>https://dev.to/techsmart/-how-i-used-switch-to-build-agricommand-ai-five-ai-agents-collaborating-for-smarter-agriculture-2h4i</guid>
      <description>&lt;h1&gt;
  
  
  How I Used Switch to Build AgriCommand AI: Five AI Agents Collaborating for Smarter Agriculture
&lt;/h1&gt;

&lt;p&gt;What if AI agents could do more than answer individual questions?&lt;/p&gt;

&lt;p&gt;What if they could work together, exchange specialized knowledge, coordinate tasks, and help humans make better decisions?&lt;/p&gt;

&lt;p&gt;That question inspired me to build &lt;strong&gt;AgriCommand AI – A Human-AI Collaborative Agriculture Intelligence Platform&lt;/strong&gt; for the Switch Hackathon.&lt;/p&gt;

&lt;p&gt;In this article, I'll explain the problem, our solution, the five specialized AI agents, how we integrated Switch, the website features, and the technologies behind the project.&lt;/p&gt;

&lt;h2&gt;
  
  
  🌱 1. The Problem: Agricultural Decisions Are Connected
&lt;/h2&gt;

&lt;p&gt;Agriculture is not a single-problem domain.&lt;/p&gt;

&lt;p&gt;A farmer making an agricultural decision may need to consider several interconnected factors:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;🌾 Which crop is suitable for the soil?&lt;/li&gt;
&lt;li&gt;💧 Is sufficient water available?&lt;/li&gt;
&lt;li&gt;🌦️ What weather conditions and risks should be considered?&lt;/li&gt;
&lt;li&gt;📈 What are the current agricultural market trends?&lt;/li&gt;
&lt;li&gt;📋 How can different information be converted into a practical action plan?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;These decisions require different types of knowledge.&lt;/p&gt;

&lt;p&gt;A single general-purpose AI assistant may provide information, but coordinating multiple specialized responsibilities within one workflow presents a different challenge.&lt;/p&gt;

&lt;p&gt;We wanted to explore a different approach:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;A team of specialized AI agents working together with a human coordinator.&lt;/strong&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  💡 2. Introducing AgriCommand AI
&lt;/h2&gt;

&lt;p&gt;AgriCommand AI is a collaborative agricultural intelligence platform designed to support farmers and agricultural coordinators.&lt;/p&gt;

&lt;p&gt;Instead of depending on one AI assistant for every task, our platform uses five specialized Gemini-powered AI agents.&lt;/p&gt;

&lt;p&gt;Each agent has a specific responsibility and contributes to a shared agricultural decision-support workflow.&lt;/p&gt;

&lt;p&gt;Our objective is to bring agricultural information, AI analysis, agent collaboration, and human decision-making into one platform.&lt;/p&gt;

&lt;h2&gt;
  
  
  🤖 3. Meet Our Five Specialized AI Agents
&lt;/h2&gt;

&lt;p&gt;We designed five agents with different responsibilities.&lt;/p&gt;

&lt;h3&gt;
  
  
  1. Agri-Triage – The Workflow Coordinator
&lt;/h3&gt;

&lt;p&gt;Agri-Triage is responsible for understanding incoming farmer requests.&lt;/p&gt;

&lt;p&gt;Its responsibilities include:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Understanding farmer-submitted agricultural problems.&lt;/li&gt;
&lt;li&gt;Classifying the reported issue.&lt;/li&gt;
&lt;li&gt;Identifying priorities.&lt;/li&gt;
&lt;li&gt;Coordinating the workflow between specialized agents.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  2. CropMind – Crop Intelligence Agent
&lt;/h3&gt;

&lt;p&gt;CropMind focuses on crop suitability analysis.&lt;/p&gt;

&lt;p&gt;It considers:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Soil conditions.&lt;/li&gt;
&lt;li&gt;Water availability.&lt;/li&gt;
&lt;li&gt;Seasonal suitability.&lt;/li&gt;
&lt;li&gt;Previous cropping information.&lt;/li&gt;
&lt;li&gt;Suitable crop options.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  3. MarketPulse – Market Intelligence Agent
&lt;/h3&gt;

&lt;p&gt;MarketPulse focuses on agricultural market information.&lt;/p&gt;

&lt;p&gt;Its responsibilities include:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Analyzing mandi price information.&lt;/li&gt;
&lt;li&gt;Organizing agricultural market insights.&lt;/li&gt;
&lt;li&gt;Helping farmers understand market trends.&lt;/li&gt;
&lt;li&gt;Supporting informed selling decisions.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  4. WeatherGuard – Weather Intelligence Agent
&lt;/h3&gt;

&lt;p&gt;WeatherGuard focuses on weather-related agricultural risks.&lt;/p&gt;

&lt;p&gt;It is designed to:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Evaluate weather conditions.&lt;/li&gt;
&lt;li&gt;Identify potential agricultural risks.&lt;/li&gt;
&lt;li&gt;Provide information that supports agricultural planning.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  5. AgriReport – Reporting and Synthesis Agent
&lt;/h3&gt;

&lt;p&gt;AgriReport brings the findings together.&lt;/p&gt;

&lt;p&gt;Its responsibilities include:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Combining findings from specialized agents.&lt;/li&gt;
&lt;li&gt;Organizing agricultural analysis.&lt;/li&gt;
&lt;li&gt;Generating a consolidated agricultural action plan.&lt;/li&gt;
&lt;li&gt;Presenting information for human review.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Each agent contributes a different perspective to the same agricultural problem.&lt;/p&gt;

&lt;h2&gt;
  
  
  🔗 4. How We Used Switch
&lt;/h2&gt;

&lt;p&gt;This is one of the most important parts of our project.&lt;/p&gt;

&lt;p&gt;We used &lt;strong&gt;Switch as the collaboration layer&lt;/strong&gt; for our custom Gemini-powered agricultural agents.&lt;/p&gt;

&lt;p&gt;Through a custom Switch adapter, our application connects to a live Switch room.&lt;/p&gt;

&lt;p&gt;Our goal was to explore how specialized AI agents could collaborate rather than operate as five independent assistants.&lt;/p&gt;

&lt;h3&gt;
  
  
  Our collaborative workflow
&lt;/h3&gt;

&lt;p&gt;The intended workflow follows these steps:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;A farmer's agricultural concern enters the AgriCommand AI platform.&lt;/li&gt;
&lt;li&gt;Agri-Triage understands the request and coordinates the workflow.&lt;/li&gt;
&lt;li&gt;CropMind, MarketPulse, and WeatherGuard contribute their specialized analysis.&lt;/li&gt;
&lt;li&gt;AgriReport combines the findings into an agricultural action plan.&lt;/li&gt;
&lt;li&gt;A human agricultural coordinator reviews important recommendations.&lt;/li&gt;
&lt;li&gt;The final decision remains with the human coordinator.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;This approach explores how agent collaboration can support real-world workflows where human judgment matters.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Integration status:&lt;/strong&gt; Our current implementation uses a live Switch room. We have not yet connected external messaging platforms such as Slack, Discord, Telegram, or Microsoft Teams.&lt;/p&gt;

&lt;h2&gt;
  
  
  🖥️ 5. Exploring the AgriCommand AI Website
&lt;/h2&gt;

&lt;p&gt;We also developed a centralized web application to make the agricultural workflow accessible and understandable.&lt;/p&gt;

&lt;p&gt;The platform includes several dedicated workspaces.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Workspace&lt;/th&gt;
&lt;th&gt;Purpose&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Overview Dashboard&lt;/td&gt;
&lt;td&gt;Centralized view of agricultural activities and insights&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Farmers&lt;/td&gt;
&lt;td&gt;Organizes farmer profiles and information&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Agricultural Reports&lt;/td&gt;
&lt;td&gt;Manages farmer-submitted problems&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;AI Agent Workspace&lt;/td&gt;
&lt;td&gt;Displays specialized agents and their activities&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Crop Intelligence&lt;/td&gt;
&lt;td&gt;Presents crop suitability analysis&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Market Intelligence&lt;/td&gt;
&lt;td&gt;Organizes agricultural market insights&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Weather Intelligence&lt;/td&gt;
&lt;td&gt;Displays weather-related agricultural risks&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Collaboration Rooms&lt;/td&gt;
&lt;td&gt;Provides a shared agent collaboration environment&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Human Approvals&lt;/td&gt;
&lt;td&gt;Allows coordinators to review recommendations&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Analytics and Reports&lt;/td&gt;
&lt;td&gt;Organizes agricultural insights and reports&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Our goal is to bring the entire decision-support workflow into one platform.&lt;/p&gt;

&lt;h2&gt;
  
  
  🛠️ 6. Technology Stack
&lt;/h2&gt;

&lt;p&gt;We combined modern web technologies with AI-powered agent collaboration.&lt;/p&gt;

&lt;h3&gt;
  
  
  Frontend
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;React 19&lt;/li&gt;
&lt;li&gt;TypeScript&lt;/li&gt;
&lt;li&gt;Vite&lt;/li&gt;
&lt;li&gt;Tailwind CSS&lt;/li&gt;
&lt;li&gt;Lucide Icons&lt;/li&gt;
&lt;li&gt;Recharts&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Backend
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Node.js&lt;/li&gt;
&lt;li&gt;Express.js&lt;/li&gt;
&lt;li&gt;TypeScript&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Artificial Intelligence
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Google Gemini API&lt;/li&gt;
&lt;li&gt;Five specialized AI agent roles&lt;/li&gt;
&lt;li&gt;Multi-agent workflow orchestration&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Agent Collaboration
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Switch&lt;/li&gt;
&lt;li&gt;Custom Switch Adapter&lt;/li&gt;
&lt;li&gt;Live Switch Room&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Database Architecture
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Supabase&lt;/li&gt;
&lt;li&gt;PostgreSQL&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Supabase and PostgreSQL are the target database architecture for our migration.&lt;/p&gt;

&lt;h3&gt;
  
  
  Development and Testing
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Git&lt;/li&gt;
&lt;li&gt;GitHub&lt;/li&gt;
&lt;li&gt;Postman&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  🧠 7. What We Learned from Building with Switch
&lt;/h2&gt;

&lt;p&gt;One of our biggest takeaways was understanding the difference between building a traditional AI chatbot and building a collaborative AI workflow.&lt;/p&gt;

&lt;p&gt;A traditional chatbot primarily focuses on responding to a user's request.&lt;/p&gt;

&lt;p&gt;A collaborative agent system introduces additional responsibilities:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Assigning tasks to specialized agents.&lt;/li&gt;
&lt;li&gt;Coordinating their contributions.&lt;/li&gt;
&lt;li&gt;Sharing information across a workflow.&lt;/li&gt;
&lt;li&gt;Combining different perspectives.&lt;/li&gt;
&lt;li&gt;Keeping humans involved in important decisions.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Switch helped us explore this collaboration model and think beyond isolated AI interactions.&lt;/p&gt;

&lt;p&gt;We also learned that designing a multi-agent system requires clearly defined agent responsibilities and a well-organized workflow.&lt;/p&gt;

&lt;h2&gt;
  
  
  🌍 8. Why AgriCommand AI Matters
&lt;/h2&gt;

&lt;p&gt;We believe AI should not simply generate answers.&lt;/p&gt;

&lt;p&gt;It should help organize information, coordinate specialized capabilities, and support people in making better-informed decisions.&lt;/p&gt;

&lt;p&gt;Agriculture is one area where this approach has meaningful potential.&lt;/p&gt;

&lt;p&gt;Our vision is to make agricultural decision support more organized, accessible, and collaborative.&lt;/p&gt;

&lt;h2&gt;
  
  
  🚀 9. What's Next?
&lt;/h2&gt;

&lt;p&gt;We want to continue improving AgriCommand AI by exploring:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;More reliable agricultural data integration.&lt;/li&gt;
&lt;li&gt;Improved agent communication and coordination.&lt;/li&gt;
&lt;li&gt;Expanded agricultural intelligence.&lt;/li&gt;
&lt;li&gt;Stronger human approval workflows.&lt;/li&gt;
&lt;li&gt;External messaging platform integrations.&lt;/li&gt;
&lt;li&gt;More comprehensive reporting and analytics.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;These are future development goals, not claims about features already completed.&lt;/p&gt;

&lt;h2&gt;
  
  
  🔗 10. Explore the Project and Resources
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Project resources&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;💻 GitHub Repository: [&lt;a href="https://github.com/asusvivobook176-svg/AgriCommand_AI" rel="noopener noreferrer"&gt;https://github.com/asusvivobook176-svg/AgriCommand_AI&lt;/a&gt;]&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Technologies and documentation&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://docs.switchagents.ai/" rel="noopener noreferrer"&gt;Switch Documentation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/sandbox-quantum/switch" rel="noopener noreferrer"&gt;Switch GitHub Repository&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://ai.google.dev/gemini-api/docs" rel="noopener noreferrer"&gt;Google Gemini API Documentation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://supabase.com/docs" rel="noopener noreferrer"&gt;Supabase Documentation&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  🙌 Final Thoughts
&lt;/h2&gt;

&lt;p&gt;Building AgriCommand AI gave us an opportunity to explore a different way of developing AI-powered applications.&lt;/p&gt;

&lt;p&gt;Instead of building one assistant that attempts to do everything, we explored how multiple specialized agents can contribute to a coordinated workflow while humans remain responsible for important decisions.&lt;/p&gt;

&lt;p&gt;Our vision is simple:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;One farmer's problem.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Five specialized AI agents.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;One coordinated workflow.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Human decisions at the center.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Thank you to the Switch team for providing an opportunity to experiment with collaborative AI systems and build something meaningful.&lt;/p&gt;

&lt;p&gt;I'm excited to continue learning, building, and exploring the possibilities of multi-agent AI.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Built for the Switch Hackathon.&lt;/strong&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>hackathon</category>
      <category>webdev</category>
      <category>agents</category>
    </item>
    <item>
      <title>👻 RepoGhost AI – Bringing Forgotten Code Back to Life with Open-Source AI</title>
      <dc:creator>VIBHEESHAN NK</dc:creator>
      <pubDate>Fri, 30 Oct 2026 08:14:36 +0000</pubDate>
      <link>https://dev.to/techsmart/repoghost-ai-bringing-forgotten-code-back-to-life-with-open-source-ai-4ki4</link>
      <guid>https://dev.to/techsmart/repoghost-ai-bringing-forgotten-code-back-to-life-with-open-source-ai-4ki4</guid>
      <description>&lt;h1&gt;
  
  
  👻 RepoGhost AI – Bringing Forgotten Code Back to Life with Open-Source AI
&lt;/h1&gt;

&lt;p&gt;&lt;strong&gt;Hacktoberfest Open-Source AI Challenge: Week 4 – Ghost in the Machine&lt;/strong&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  🚀 What I Built
&lt;/h2&gt;

&lt;p&gt;Introducing &lt;strong&gt;RepoGhost AI&lt;/strong&gt;, an AI-powered codebase investigation platform designed to help developers understand, explore and rediscover the hidden history of their software projects.&lt;/p&gt;

&lt;p&gt;Every software repository has a story. Some functions are undocumented, some modules become forgotten, and important development decisions can disappear as projects evolve. Understanding an unfamiliar or older codebase can become a time-consuming challenge.&lt;/p&gt;

&lt;p&gt;RepoGhost AI aims to solve this problem by combining Git intelligence, code analysis, semantic search and open-weight AI into one developer-focused platform.&lt;/p&gt;

&lt;p&gt;Developers can explore repository structures, investigate commit histories, understand complex source code, discover potentially unused code and generate technical documentation through an intelligent interface.&lt;/p&gt;

&lt;p&gt;Inspired by the Hacktoberfest Week 4 theme, &lt;strong&gt;Ghost in the Machine&lt;/strong&gt;, RepoGhost AI brings forgotten parts of software projects back into focus.&lt;/p&gt;

&lt;h2&gt;
  
  
  💡 Inspiration
&lt;/h2&gt;

&lt;p&gt;The inspiration behind RepoGhost AI comes from a simple observation: software repositories contain more than just source code. They contain the history, decisions, experiments and knowledge of the developers who created them.&lt;/p&gt;

&lt;p&gt;When developers leave a project or when a codebase grows over time, valuable knowledge can become difficult to recover.&lt;/p&gt;

&lt;p&gt;I wanted to explore whether open-source AI could act as a digital investigator that helps developers uncover this hidden knowledge.&lt;/p&gt;

&lt;p&gt;The Ghost in the Machine theme provided the perfect inspiration. Instead of imagining ghosts as supernatural entities, I interpreted them as forgotten functions, abandoned modules, undocumented code and hidden histories inside software repositories.&lt;/p&gt;

&lt;p&gt;RepoGhost AI is my attempt to give those forgotten parts of software a voice again.&lt;/p&gt;

&lt;h2&gt;
  
  
  ✨ Key Features
&lt;/h2&gt;

&lt;h3&gt;
  
  
  1. Repository Explorer
&lt;/h3&gt;

&lt;p&gt;Explore repository structures, folders, files, programming languages and project statistics through a unified dashboard.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Ghost History – Git Intelligence
&lt;/h3&gt;

&lt;p&gt;Investigate Git commit history, contributor activity, file modifications and code evolution to understand how a project has changed over time.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Code Intelligence
&lt;/h3&gt;

&lt;p&gt;Analyze source code to identify functions, classes, complexity indicators, duplicate-code candidates and potentially unused code.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. Ghost Chat – AI Code Assistant
&lt;/h3&gt;

&lt;p&gt;Interact with an AI assistant to ask questions about repositories, explain functions, summarize files and understand project architecture.&lt;/p&gt;

&lt;h3&gt;
  
  
  5. Project Memory
&lt;/h3&gt;

&lt;p&gt;Build searchable project knowledge using embeddings and retrieval-based techniques to help developers find relevant code and documentation.&lt;/p&gt;

&lt;h3&gt;
  
  
  6. Documentation Generator
&lt;/h3&gt;

&lt;p&gt;Generate draft README files, architecture descriptions, API documentation and developer onboarding guides.&lt;/p&gt;

&lt;h3&gt;
  
  
  7. Developer Analytics
&lt;/h3&gt;

&lt;p&gt;Visualize repository activity, programming language distribution, commit trends and project health indicators.&lt;/p&gt;

&lt;h2&gt;
  
  
  🧠 Open-Source AI Integration
&lt;/h2&gt;

&lt;p&gt;Open-source AI is at the heart of RepoGhost AI.&lt;/p&gt;

&lt;p&gt;The project is designed around open-weight models and local inference to explore how developers can use AI while maintaining greater control over their source code and development environment.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Planned AI Model:&lt;/strong&gt; Google Gemma&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Model Runtime:&lt;/strong&gt; Ollama&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;AI Architecture:&lt;/strong&gt; Retrieval-Augmented Generation (RAG)&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vector Database:&lt;/strong&gt; ChromaDB&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Inference Approach:&lt;/strong&gt; Local inference&lt;/p&gt;

&lt;p&gt;The proposed AI workflow combines repository analysis, code chunking, embeddings, semantic retrieval and local model inference.&lt;/p&gt;

&lt;p&gt;When a developer asks a question, the application retrieves relevant code and documentation from the selected repository and provides that context to the language model.&lt;/p&gt;

&lt;p&gt;This approach aims to generate more relevant, repository-specific explanations instead of relying only on generic programming knowledge.&lt;/p&gt;

&lt;p&gt;The open-weight approach also provides flexibility to experiment with different models, customize the inference environment and reduce dependency on proprietary AI services.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Note: The final model integration and inference results will be documented according to the implementation actually completed.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  🏗️ Technology Stack
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Component&lt;/th&gt;
&lt;th&gt;Technology&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Frontend&lt;/td&gt;
&lt;td&gt;React + Vite&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Language&lt;/td&gt;
&lt;td&gt;TypeScript&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;UI Styling&lt;/td&gt;
&lt;td&gt;Tailwind CSS&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Backend&lt;/td&gt;
&lt;td&gt;Python + FastAPI&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Git Analysis&lt;/td&gt;
&lt;td&gt;GitPython&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Code Analysis&lt;/td&gt;
&lt;td&gt;Python AST / Tree-sitter&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;AI Model&lt;/td&gt;
&lt;td&gt;Gemma&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;AI Runtime&lt;/td&gt;
&lt;td&gt;Ollama&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Embeddings&lt;/td&gt;
&lt;td&gt;Local embedding model&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Vector Database&lt;/td&gt;
&lt;td&gt;ChromaDB&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Metadata Storage&lt;/td&gt;
&lt;td&gt;SQLite&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;API Communication&lt;/td&gt;
&lt;td&gt;REST API&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  ⚙️ How It Works
&lt;/h2&gt;

&lt;p&gt;RepoGhost AI follows a repository intelligence pipeline.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Step 1 – Repository Selection&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The developer selects a local Git repository for analysis.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Step 2 – Repository Processing&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The backend examines the directory structure, source files, documentation and available Git history.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Step 3 – Code Analysis&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The system identifies files, functions, classes, programming languages and other code-related information.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Step 4 – Knowledge Indexing&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Relevant source-code sections and documentation are divided into meaningful chunks and converted into vector embeddings.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Step 5 – AI-Powered Retrieval&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;When a developer asks a question, the application retrieves relevant repository context using semantic search.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Step 6 – Local AI Inference&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The retrieved context is supplied to the configured open-weight model through Ollama.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Step 7 – Intelligent Response&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The application presents explanations, summaries and relevant source references through the RepoGhost AI interface.&lt;/p&gt;

&lt;h2&gt;
  
  
  🔓 Why Open Innovation Matters
&lt;/h2&gt;

&lt;p&gt;Open innovation is important because developers should have greater control over the tools they use and the data they work with.&lt;/p&gt;

&lt;p&gt;For RepoGhost AI, an open-weight AI approach provides several advantages:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Privacy:&lt;/strong&gt; Local inference can help keep repository source code on the developer's machine.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Flexibility:&lt;/strong&gt; Developers can experiment with different compatible models.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Customization:&lt;/strong&gt; Open-weight models provide opportunities for model adaptation and experimentation.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Reduced dependency:&lt;/strong&gt; The application does not need to depend entirely on proprietary AI APIs.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Accessibility:&lt;/strong&gt; Developers can explore local AI without requiring a paid external inference service, subject to hardware and resource requirements.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Community collaboration:&lt;/strong&gt; Open-source tools allow developers to learn, contribute and improve the ecosystem together.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;My goal is to demonstrate how open-source AI can become a practical part of everyday software development.&lt;/p&gt;

&lt;h2&gt;
  
  
  🖥️ Screenshots and Demo
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Live Demo:&lt;/strong&gt; [&lt;a href="https://lumina-puce-ten.vercel.app/" rel="noopener noreferrer"&gt;https://lumina-puce-ten.vercel.app/&lt;/a&gt;]&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;GitHub Repository:&lt;/strong&gt; [&lt;a href="https://github.com/asusvivobook176-svg/lumina" rel="noopener noreferrer"&gt;https://github.com/asusvivobook176-svg/lumina&lt;/a&gt;]&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Screenshots:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;RepoGhost AI Dashboard&lt;/li&gt;
&lt;li&gt;Repository Explorer&lt;/li&gt;
&lt;li&gt;Ghost History&lt;/li&gt;
&lt;li&gt;Code Intelligence&lt;/li&gt;
&lt;li&gt;Ghost Chat&lt;/li&gt;
&lt;li&gt;Documentation Generator&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  🛠️ Installation and Usage
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Prerequisites
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Python&lt;/li&gt;
&lt;li&gt;Node.js and npm&lt;/li&gt;
&lt;li&gt;Git&lt;/li&gt;
&lt;li&gt;Ollama (for local AI inference)&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Clone the repository
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;git clone YOUR_REPOSITORY_URL
&lt;span class="nb"&gt;cd &lt;/span&gt;RepoGhost-AI
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Frontend setup
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;cd &lt;/span&gt;frontend
npm &lt;span class="nb"&gt;install
&lt;/span&gt;npm run dev
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Backend setup
&lt;/h3&gt;

&lt;p&gt;Open another terminal:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;cd &lt;/span&gt;backend
py &lt;span class="nt"&gt;-m&lt;/span&gt; venv venv
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Activate the virtual environment on Windows:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;venv&lt;span class="se"&gt;\S&lt;/span&gt;cripts&lt;span class="se"&gt;\a&lt;/span&gt;ctivate
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Install dependencies:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;pip &lt;span class="nb"&gt;install&lt;/span&gt; &lt;span class="nt"&gt;-r&lt;/span&gt; requirements.txt
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Start the FastAPI server:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;uvicorn app.main:app &lt;span class="nt"&gt;--reload&lt;/span&gt; &lt;span class="nt"&gt;--port&lt;/span&gt; 8000
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Local AI setup
&lt;/h3&gt;

&lt;p&gt;Install Ollama and download the selected Gemma model according to your system's available resources.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;ollama pull gemma3:1b
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Start the model:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;ollama run gemma3:1b
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The selected model and its configuration should match the model used by the application.&lt;/p&gt;

&lt;h2&gt;
  
  
  🔮 Future Improvements
&lt;/h2&gt;

&lt;p&gt;RepoGhost AI has several opportunities for further development:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Multi-language repository intelligence.&lt;/li&gt;
&lt;li&gt;Advanced code dependency visualization.&lt;/li&gt;
&lt;li&gt;More accurate unused-code detection.&lt;/li&gt;
&lt;li&gt;Multi-agent codebase investigation.&lt;/li&gt;
&lt;li&gt;Improved Git history reasoning.&lt;/li&gt;
&lt;li&gt;Repository-specific long-term memory.&lt;/li&gt;
&lt;li&gt;Automated security and code quality analysis.&lt;/li&gt;
&lt;li&gt;Team collaboration and shared project knowledge.&lt;/li&gt;
&lt;li&gt;More open-weight model integrations.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  🙌 Acknowledgements
&lt;/h2&gt;

&lt;p&gt;I would like to thank the Hacktoberfest team, DEV Community and the open-source AI ecosystem for creating opportunities to explore, experiment and build meaningful projects.&lt;/p&gt;

&lt;p&gt;This project is an exploration of how open-source AI can help developers rediscover the knowledge hidden inside their software repositories.&lt;/p&gt;




&lt;h2&gt;
  
  
  👻 Final Thoughts
&lt;/h2&gt;

&lt;p&gt;Every repository has a history. Every function has a purpose, and every project contains knowledge that deserves to be understood.&lt;/p&gt;

&lt;p&gt;With RepoGhost AI, I want to bring that hidden knowledge back to life.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Your Codebase Has a Ghost. Let AI Reveal Its History.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Project:&lt;/strong&gt; RepoGhost AI&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Theme:&lt;/strong&gt; Hacktoberfest 2026 – Ghost in the Machine&lt;/p&gt;

&lt;h1&gt;
  
  
  devchallenge #hf26challenge #Hacktoberfest #OpenSource #ArtificialIntelligence #Gemma #Python #React #FastAPI #Ollama #DeveloperTools #RAG
&lt;/h1&gt;

</description>
      <category>devchallenge</category>
      <category>hf26challenge</category>
    </item>
    <item>
      <title>Agentic GraphRAG: From RAG to Graph-Based Agentic Reasoning</title>
      <dc:creator>VIBHEESHAN NK</dc:creator>
      <pubDate>Mon, 05 Oct 2026 14:03:45 +0000</pubDate>
      <link>https://dev.to/techsmart/agentic-graphrag-from-rag-to-graph-based-agentic-reasoning-2og3</link>
      <guid>https://dev.to/techsmart/agentic-graphrag-from-rag-to-graph-based-agentic-reasoning-2og3</guid>
      <description>&lt;p&gt;Large Language Models (LLMs) can answer many questions, but answering questions over a large and complex corpus becomes difficult when the required information is spread across multiple documents or depends on relationships between different entities.&lt;br&gt;
To address this challenge, we developed Agentic GraphRAG, a system that combines:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Retrieval-Augmented Generation (RAG)&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;GraphRAG&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;TigerGraph&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Agent-based reasoning&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The project compares three retrieval and reasoning approaches under a controlled setup:&lt;br&gt;
&lt;strong&gt;RAG → GraphRAG → Agentic GraphRAG&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The goal is not simply to retrieve more information, but to understand when vector retrieval is enough, when graph relationships are useful, and when an agentic system can adapt its strategy to the question.&lt;br&gt;
Core idea: Retrieve the evidence, understand the relationships, reason over the evidence, and generate the answer.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Problem
&lt;/h2&gt;

&lt;p&gt;When a user asks a question over a large corpus, the answer may not exist as a single sentence in one document.&lt;br&gt;
For example, a question may require the system to:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Determine the athlete's result.&lt;/li&gt;
&lt;li&gt;Combine information from multiple records.&lt;/li&gt;
&lt;li&gt;Apply a condition or calculation.&lt;/li&gt;
&lt;/ul&gt;

&lt;blockquote&gt;
&lt;p&gt;A conventional vector search system can retrieve documents containing semantically related information, but it does not explicitly represent how entities are connected.&lt;/p&gt;

&lt;p&gt;Normal RAG systems may fail when a question needs information from multiple documents or relationships between different entities. They may retrieve the wrong information or miss important evidence&lt;br&gt;
.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;This creates an important challenge:&lt;/p&gt;

&lt;p&gt;How can we combine unstructured document retrieval with structured relationships and adaptive reasoning?&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fxdkweicf44n1z3iddv37.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fxdkweicf44n1z3iddv37.png" alt="Important" width="800" height="533"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Our Approach
&lt;/h2&gt;

&lt;p&gt;We propose an*&lt;em&gt;Agentic GraphRAG system&lt;/em&gt;* that combines &lt;em&gt;document search&lt;/em&gt; , a &lt;em&gt;knowledge graph&lt;/em&gt;,and &lt;em&gt;AI agents&lt;/em&gt; to find the right evidence and answer complex questions more accurately.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How Our System Works&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F3ggie68wh2uer5z613vh.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F3ggie68wh2uer5z613vh.png" alt="System Works  Flowchart" width="800" height="533"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The first approach is traditional Retrieval-Augmented Generation.&lt;/li&gt;
&lt;li&gt;The question is converted into an embedding and used to search a vector database for semantically relevant document chunks.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Why RAG?&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Vector retrieval is useful because it searches based on semantic similarity rather than requiring an exact keyword match.&lt;/li&gt;
&lt;li&gt;However, semantic similarity alone does not explicitly tell the system how different entities are related.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That becomes important for multi-hop questions.&lt;/p&gt;

&lt;h2&gt;
  
  
  GraphRAG with TigerGraph
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;The second approach is GraphRAG.&lt;/li&gt;
&lt;li&gt;Instead of relying only on document similarity, GraphRAG uses structured entities and relationships.&lt;/li&gt;
&lt;li&gt;For our implementation, the knowledge graph is represented using TigerGraph.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The graph can represent entities such as:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Athletes&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Events&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Sports&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Olympic Games&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Results or medals&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;These entities can be connected through explicit relationships.&lt;/p&gt;

&lt;p&gt;_&lt;br&gt;
&lt;strong&gt;The GraphRAG pipeline becomes:&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fbxkeo80szgz7hkf4p5rv.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fbxkeo80szgz7hkf4p5rv.png" alt="GraphRAG pipeline Flowchart" width="800" height="320"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Why use a graph?&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A graph database represents explicit relationships between entities.&lt;/li&gt;
&lt;li&gt;Instead of asking the LLM to infer every relationship from raw text, the system can retrieve relevant relationships and paths directly from the graph.&lt;/li&gt;
&lt;li&gt;This is particularly useful when a question requires multiple connected facts.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Agentic GraphRAG&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The third and most advanced approach is Agentic GraphRAG.&lt;/li&gt;
&lt;li&gt;Here, we introduce an Agent Router that determines what type of retrieval or reasoning strategy is appropriate for the question.&lt;/li&gt;
&lt;li&gt;Different questions require different strategies.&lt;/li&gt;
&lt;li&gt;A simple lookup may need direct retrieval.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A more complex question may require:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Document retrieval&lt;/li&gt;
&lt;li&gt;Graph traversal&lt;/li&gt;
&lt;li&gt;Multi-hop reasoning&lt;/li&gt;
&lt;li&gt;Aggregation&lt;/li&gt;
&lt;li&gt;Temporal reasoning&lt;/li&gt;
&lt;li&gt;Superlative reasoning&lt;/li&gt;
&lt;li&gt;Re-querying or refinement&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The system therefore does not force every question through exactly the same retrieval process.&lt;br&gt;
Instead, the router decides which agents should participate.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Flgho2efbnrksunffd6zn.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Flgho2efbnrksunffd6zn.png" alt="Agentic GraphRAG  Flowchart" width="800" height="533"&gt;&lt;/a&gt;                         &lt;/p&gt;

&lt;h2&gt;
  
  
  The agents
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Retrieval Agent:&lt;/strong&gt;&lt;br&gt;
Responsible for document lookup and vector-based retrieval.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fxvz4em9d11a6q1uyl2w3.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fxvz4em9d11a6q1uyl2w3.png" alt="Retrieval Agent" width="800" height="533"&gt;&lt;/a&gt;&lt;br&gt;
&lt;strong&gt;Graph Agent&lt;/strong&gt;&lt;br&gt;
Responsible for structured graph queries and relationship-based retrieval.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fsjuty8astrybevgzqxko.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fsjuty8astrybevgzqxko.png" alt="Graph Agent" width="800" height="533"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Reasoning Agent&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Responsible for multi-step reasoning and deciding whether further planning or refinement is required.&lt;/li&gt;
&lt;li&gt;This is useful for questions that cannot be answered by a single retrieval operation.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F7zea1nl1t43d78mr6txa.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F7zea1nl1t43d78mr6txa.png" alt=" " width="800" height="1200"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;strong&gt;Why TigerGraph?&lt;/strong&gt;
&lt;/h2&gt;

&lt;h2&gt;
  
  
  - TigerGraph plays an important role in both our GraphRAG and Agentic GraphRAG pipelines.
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;A vector database is effective for finding semantically similar document chunks.&lt;/li&gt;
&lt;li&gt;&lt;p&gt;A graph database is designed to represent explicit relationships between entities.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;These relationships can be traversed to obtain structured evidence.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The key advantage is that the system does not need the LLM to infer every relationship from text.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;TigerGraph → Structured relationships&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Vector DB  → Relevant documents&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;LLM        → Natural-language understanding and answer generation&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Agents     → Retrieval and reasoning strategy&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;This separation of responsibilities is one of the core design principles of our architecture.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Agentic Reasoning in Action&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The main difference between GraphRAG and Agentic GraphRAG is adaptive orchestration.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;GraphRAG follows a structured graph retrieval approach.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Agentic GraphRAG first considers the nature of the question and then selects an appropriate strategy.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;The system needs to:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Identify the relevant Olympic Games.&lt;/li&gt;
&lt;li&gt;Identify the relevant biathlon events.&lt;/li&gt;
&lt;li&gt;Retrieve the number of competitors for each event.&lt;/li&gt;
&lt;li&gt;Apply the condition competitors &amp;gt; 73.&lt;/li&gt;
&lt;li&gt;Count the events satisfying the condition.&lt;/li&gt;
&lt;li&gt;Generate the final natural-language answer.&lt;/li&gt;
&lt;li&gt;This is an aggregation-style question.
An agentic workflow can make these reasoning steps explicit.
**&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The Agentic Trace
&lt;/h2&gt;

&lt;p&gt;One important feature of the Agentic GraphRAG pipeline is the agentic trace.&lt;br&gt;
The trace records information about the system's process, such as:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Router decisions&lt;/li&gt;
&lt;li&gt;Agents selected&lt;/li&gt;
&lt;li&gt;Retrieval steps&lt;/li&gt;
&lt;li&gt;Evidence collected&lt;/li&gt;
&lt;li&gt;Reasoning steps&lt;/li&gt;
&lt;li&gt;Re-query or refinement actions
Conceptually:&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The trace provides additional visibility into how the system reached its answer.&lt;br&gt;
This is useful for inspecting and debugging complex retrieval workflows.&lt;/p&gt;

&lt;h2&gt;
  
  
  Controlled Comparison
&lt;/h2&gt;

&lt;p&gt;A major part of the project is the controlled comparison between the three approaches.&lt;br&gt;
The same user question is sent through:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fqhhjgwwqc16dufaq2brx.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fqhhjgwwqc16dufaq2brx.png" alt="Work flow" width="800" height="533"&gt;&lt;/a&gt;&lt;br&gt;
The goal is to change the retrieval/reasoning strategy while keeping the LLM consistent.&lt;/p&gt;

&lt;p&gt;This makes it easier to study the trade-offs between:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Simple semantic retrieval&lt;/li&gt;
&lt;li&gt;Structured graph retrieval&lt;/li&gt;
&lt;li&gt;Adaptive agentic reasoning&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Benchmark&lt;/strong&gt;&lt;br&gt;
We use a benchmark containing 100 questions.&lt;br&gt;
The questions are divided into five categories:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Category  Description&lt;/li&gt;
&lt;li&gt;Lookup           Direct information retrieval&lt;/li&gt;
&lt;li&gt;Temporal  Questions involving time or dates&lt;/li&gt;
&lt;li&gt;Aggregation   Questions requiring filtering, counting, or combining values&lt;/li&gt;
&lt;li&gt;Superlative   Questions involving highest, lowest, largest, smallest, etc.&lt;/li&gt;
&lt;li&gt;Multi-hop Questions requiring multiple connected relationships&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;We evaluate the three approaches using metrics such as:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Accuracy&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Average tokens per question&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Average latency&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For Agentic GraphRAG, we also track additional information such as:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Retrieval steps&lt;/li&gt;
&lt;li&gt;Reasoning steps&lt;/li&gt;
&lt;li&gt;Retrieval methods&lt;/li&gt;
&lt;li&gt;Processing time&lt;/li&gt;
&lt;li&gt;Agentic trace
&lt;strong&gt;Benchmark Results&lt;/strong&gt;
Important: Replace the values below with the actual results from your benchmark dashboard. Do not publish placeholder values.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ft0vfvwzyl64ocsssilj3.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ft0vfvwzyl64ocsssilj3.jpg" alt="Result" width="761" height="181"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  How to interpret the results
&lt;/h2&gt;

&lt;p&gt;The benchmark helps us understand the trade-offs between the three approaches.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;RAG provides a relatively direct retrieval pipeline.&lt;/li&gt;
&lt;li&gt;GraphRAG adds structured relationships and graph traversal.&lt;/li&gt;
&lt;li&gt;Agentic GraphRAG adds adaptive orchestration and can perform additional reasoning steps when the question requires them.&lt;/li&gt;
&lt;li&gt;The final results should be discussed using the actual benchmark measurements rather than assuming that one approach is always better.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  System Architecture
&lt;/h2&gt;

&lt;p&gt;The architecture contains three parallel pipelines that receive the same user question.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;RAG Pipeline&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ftn0jvt8lr2hozwrbgbwf.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ftn0jvt8lr2hozwrbgbwf.png" alt="RAG Pipeline" width="800" height="1200"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;GraphRAG Pipeline&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fdlkwifcn6lxl9maa4gy0.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fdlkwifcn6lxl9maa4gy0.png" alt="GraphRAG Pipeline" width="800" height="533"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Agentic GraphRAG Pipeline&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fgzi9oit23q92lg4e08xg.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fgzi9oit23q92lg4e08xg.png" alt="gentic GraphRAG Pipeline" width="800" height="533"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;All three pipelines then use the same LLM for natural-language understanding and answer synthesis.&lt;/p&gt;

&lt;h2&gt;
  
  
  Architecture Diagram
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fcxgkjb8g6z9stjp36cwp.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fcxgkjb8g6z9stjp36cwp.jpeg" alt="Architecture Diagram" width="800" height="771"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The diagram should be placed after this section so readers can visually understand the complete pipeline before reading the &lt;br&gt;
implementation details.&lt;/p&gt;

&lt;h2&gt;
  
  
  Division of Responsibilities
&lt;/h2&gt;

&lt;p&gt;A key design principle in the system is the separation of responsibilities.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fe3p76f0j71cxxge53v35.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fe3p76f0j71cxxge53v35.png" alt="Division of Responsibilities" width="800" height="533"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Demo Flow
&lt;/h2&gt;

&lt;p&gt;Our demonstration follows the same progression as the architecture.&lt;br&gt;
&lt;strong&gt;Demo 1: RAG&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;We start with a question that can be answered through semantic document retrieval.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fjuwrj2v5ul1aktwer55g.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fjuwrj2v5ul1aktwer55g.png" alt="RAG" width="800" height="267"&gt;&lt;/a&gt;&lt;br&gt;
&lt;strong&gt;Demo 2: GraphRAG&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Next, we demonstrate a question that benefits from structured relationships.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fugnhuvey9iwfm5mob8in.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fugnhuvey9iwfm5mob8in.png" alt="GraphRag" width="800" height="267"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Demo 3: Agentic GraphRAG&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Finally, we demonstrate a more complex question requiring aggregation or multi-step reasoning.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fu285l8u8qhpcadb4dai1.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fu285l8u8qhpcadb4dai1.png" alt="Agentic GraphRAG" width="800" height="267"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Key Advantages
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Better Relationship Understanding&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Graph-based retrieval can explicitly represent relationships between entities.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Flexible Reasoning&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The agentic layer can select different strategies depending on the question.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Traceability&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The agentic trace provides visibility into retrieval and reasoning steps.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Separation of Responsibilities&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The graph handles structured evidence while the LLM handles natural-language understanding and generation.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Comparative Evaluation&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Implementing RAG, GraphRAG, and Agentic GraphRAG allows us to study their strengths and trade-offs under a common evaluation setup.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Challenges We Faced
&lt;/h2&gt;

&lt;p&gt;Building the system involved several challenges.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Designing the Knowledge Graph&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt; The graph structure needs to represent the entities and relationships in the corpus correctly.&lt;/li&gt;
&lt;li&gt; Poor graph modeling can lead to incomplete or incorrect graph retrieval.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Choosing the Right Strategy&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Different questions require different retrieval and reasoning strategies.&lt;/li&gt;
&lt;li&gt;The system therefore needs to distinguish between simple lookups, temporal questions, aggregation, superlatives, and multi-hop questions.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Latency and Token Usage&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt; Additional reasoning steps can increase computational cost.&lt;/li&gt;
&lt;li&gt; An agentic system may perform more retrieval and reasoning operations than a simple RAG pipeline, so latency and token usage need to be measured.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Fair Benchmarking&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The three approaches need to be evaluated under consistent conditions.&lt;/li&gt;
&lt;li&gt;Otherwise, differences in configuration could make the comparison misleading.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Future Improvements
&lt;/h2&gt;

&lt;p&gt;There are several directions in which this project can be extended:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;More specialized reasoning agents&lt;/li&gt;
&lt;li&gt;Better query planning for complex questions&lt;/li&gt;
&lt;li&gt;Improved graph traversal strategies&lt;/li&gt;
&lt;li&gt;Larger and more diverse benchmark datasets&lt;/li&gt;
&lt;li&gt;More detailed hallucination evaluation&lt;/li&gt;
&lt;li&gt;Better evidence-grounding evaluation&lt;/li&gt;
&lt;li&gt;Improved visualization of agentic traces&lt;/li&gt;
&lt;li&gt;Adaptive selection between vector and graph retrieval&lt;/li&gt;
&lt;li&gt;More robust evidence verification&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A future version could make the router more adaptive by learning which retrieval strategy works best for different question categories.&lt;/p&gt;

&lt;h2&gt;
  
  
  Technology Stack
&lt;/h2&gt;

&lt;p&gt;The project uses the following technologies and concepts:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;TigerGraph — graph database and structured relationship retrieval&lt;/li&gt;
&lt;li&gt;Vector Database — semantic document retrieval&lt;/li&gt;
&lt;li&gt;Large Language Model (LLM) — natural-language understanding and answer synthesis&lt;/li&gt;
&lt;li&gt;Retrieval-Augmented Generation (RAG) — document-based retrieval pipeline&lt;/li&gt;
&lt;li&gt;GraphRAG — graph-based retrieval pipeline&lt;/li&gt;
&lt;li&gt;Agentic Reasoning — adaptive orchestration and multi-step reasoning&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  RAG vs GraphRAG vs Agentic GraphRAG
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fal1t5szo398xg4rr2wsg.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fal1t5szo398xg4rr2wsg.png" alt="RAG vs GraphRAG vs Agentic GraphRAG&lt;br&gt;
" width="800" height="400"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What We Learned
&lt;/h2&gt;

&lt;p&gt;This project helped us understand that retrieval quality is not only about finding text that looks similar to a question.&lt;br&gt;
For complex questions, the system may also need to understand:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Which entities are involved&lt;/li&gt;
&lt;li&gt;How those entities are connected&lt;/li&gt;
&lt;li&gt;Which evidence is relevant&lt;/li&gt;
&lt;li&gt;Which reasoning strategy should be used&lt;/li&gt;
&lt;li&gt;Whether additional retrieval is required&lt;/li&gt;
&lt;/ul&gt;

&lt;blockquote&gt;
&lt;p&gt;RAG provides a strong foundation for semantic retrieval.&lt;/p&gt;

&lt;p&gt;GraphRAG adds structured relationships.&lt;br&gt;
Agentic GraphRAG adds adaptive orchestration on top of retrieval and graph-based evidence.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;p&gt;Our project demonstrates the progression:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;RAG focuses on retrieving relevant documents.&lt;/li&gt;
&lt;li&gt;GraphRAG adds structured relationships through a knowledge graph.&lt;/li&gt;
&lt;li&gt;Agentic GraphRAG adds adaptive orchestration and reasoning strategies on top of retrieval and graph-based evidence.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fnogr18xl54az948k5oje.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fnogr18xl54az948k5oje.png" alt="Conclusion" width="800" height="533"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;The central idea of the project is:&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Retrieve the evidence, understand the relationships, reason over the evidence, and generate the answer.&lt;br&gt;
By combining vector retrieval, graph-based knowledge, LLMs, and agentic reasoning, we explore a more structured and traceable approach&lt;/p&gt;
&lt;/blockquote&gt;

</description>
      <category>agents</category>
      <category>ai</category>
      <category>llm</category>
      <category>rag</category>
    </item>
  </channel>
</rss>
