Chains vs. Agents

In AI Engineering, LangChain provides a framework for managing the flow of execution steps, particularly within the context of building applications that use Large Language Models (LLMs). LangChain allows developers to set up structured workflows (chains) and dynamic, decision-making processes (agents) that operate within defined guardrails. These guardrails ensure that the AI agents follow specific guidelines or constraints while executing tasks, helping to control and optimize how LLMs are used in various applications.

What Are Chains?

Chains in LangChain are sequences of predefined steps that the AI follows in a specific order. Each step represents a task, and these tasks are connected to achieve a specific goal.

For example, consider an AI workflow designed to handle customer support emails:

Step 1: The AI reads the email content.

Step 2: It identifies the main issue (e.g., billing, technical support, or general inquiry).

Step 3: Based on the identified issue, the AI selects a relevant response template.

Step 4: The AI customizes the template with specific details from the email.

Step 5: It sends the customized response back to the customer.

In this chain, each step is predefined and must be executed in a specific order. The process is structured and predictable, ensuring that every customer email is handled consistently.

What Are Agents?

Agents in LangChain are more adaptable and intelligent. Instead of following a fixed set of steps, an agent is given a goal and determines the best way to achieve it. The agent selects the tools, decides on the steps, and adapts to any changes or unexpected information during the process.

How Can an Agent Make Such Decisions?

Even though an LLM (Large Language Model) primarily generates text, agents use several mechanisms to make decisions and handle tasks flexibly:

1) Tool Integration:

Access to External Tools: Agents are not limited to text generation. They can interact with various external tools, such as APIs, databases, or search engines. For instance, if an agent needs to gather competitor pricing, it can use a web scraping tool to collect data from different websites.

Deciding Which Tool to Use: The agent decides which tool to use based on the context provided by the user and the goal it needs to achieve. For example, if the agent recognizes that the task involves finding information online, it may decide to use a web search tool.

2) Prompt Engineering:

Dynamic Prompts: The agent uses dynamic prompts to guide the LLM. These prompts can instruct the LLM to take specific actions, like parsing information, summarizing data, or making logical inferences.

Context Awareness: The LLM within the agent uses context from previous interactions to decide what to do next. For instance, if the agent is planning a trip and realizes that a specific hotel is fully booked, the LLM can generate a prompt that instructs the agent to search for alternative accommodations.

3) Decision Logic:

Conditional Responses: The agent can be programmed with conditional logic to make decisions based on the output from the LLM. For instance, if the agent receives a response that indicates a problem (like a website being down), it can trigger alternative actions, such as retrying the connection or switching to a different data source.

Looping and Iteration: The agent can iterate through processes, refining its approach based on feedback. For example, if the initial data retrieval doesn’t provide complete information, the agent can loop through different sources until it gathers what’s needed.

Example: Extracting Insights from Customer Feedback

Imagine an agent tasked with extracting actionable insights from a diverse dataset of customer feedback collected from various sources, such as surveys, social media, and review sites, to improve a company's product.

Here’s how the agent operates, with an emphasis on decision-making:

1) Gather Data:

Decision: The agent decides which sources are most relevant based on the context and goals. It might prioritize recent reviews or focus on specific platforms where customer feedback is most detailed.

2) Extract Key Information:

Decision: As the agent processes the feedback, it chooses which aspects of the feedback are most important (e.g., sentiment, specific complaints, or feature requests). It uses natural language processing (NLP) tools to extract relevant comments and categorize them by themes.

3) Analyze and Summarize:

Decision: The agent determines which analytical methods to use. For example, it might choose sentiment analysis to gauge overall customer satisfaction and topic modeling to identify recurring themes. If sentiment analysis reveals mixed feelings about a feature, the agent may decide to perform a deeper dive into that particular aspect.

4) Handle Variations:

Decision: When encountering feedback with unusual formats or ambiguous language, the agent adjusts its approach. It might employ specialized models for slang or non-standard text or use additional tools to better interpret the feedback.

5) Generate Insights:

Decision: The agent decides which insights are most actionable based on the analysis. For example, if it identifies a recurring complaint about product usability, it might prioritize this finding and suggest specific areas for improvement. It also decides how to present these insights in a report, emphasizing the most critical findings.

Key Differences

• Chains are linear workflows, following a fixed sequence of steps that are predefined and must occur in a specific order.
• Agents are dynamic, making decisions and adapting their approach in real-time to achieve the goal, even when the process involves uncertainty or changes.

When to Use Chains or Agents?

• Use Chains when the task involves a clear, linear process with specific steps that must be followed in order, such as data transformation or routine operations with predictable inputs and outputs.
• Use Agents when the task requires flexibility, such as handling dynamic content, interacting with multiple data sources, or making decisions based on variable and evolving conditions, like extracting insights from customer feedback in the above fashion.

Additional Usage Note:

• It is possible to make a sequence of chains which is called a Sequential Chain
• It is possible to utilize a chain or a sequential chain as a tool for an agent to use
• It is also possible to make a sequence of agents which is called a Sequential Agent (There is also a distinction between Sequential Agents and Multi Agents, where Multi Agents are at a higher abstraction level than the Sequential Agents. Multi Agents are composed of a Supervisor and a number of Workers. The Supervisor is given decision power in choice of the Worker agent that carries out a dedicated task and it also steers decision making on the sequence of execution by deciding when to call a particular Worker.)

My Newsletter

In case you would like to make sure you receive an email in your inbox when I publish the next article just leave your email here.