Dynamiq Docs
  • Welcome to Dynamiq
  • Low-Code Builder
    • Extractors and Transformers
    • Chat
    • Basics
    • Connecting Nodes
    • Conditional Nodes and Multiple Outputs
    • Input and Output Transformers
    • Error Handling and Retries
    • LLM Nodes
    • Validator Nodes
    • RAG Nodes
      • Indexing Workflow
        • Pre-processing Nodes
        • Document Splitting
        • Document Embedders
        • Document Writers
      • Inference RAG workflow
        • Text embedders
        • Document retrievers
          • Complex retrievers
        • LLM Answer Generators
    • LLM Agents
      • Basics
      • Guide to Implementing LLM Agents: ReAct and Simple Agents
      • Guide to Agent Orchestration: Linear and Adaptive Orchestrators
      • Guide to Advanced Agent Orchestration: Graph Orchestrator
    • Audio and voice
    • Tools and External Integrations
    • Python Code in Workflows
    • Memory
    • Guardrails
  • Deployments
    • Workflows
      • Tracing Workflow Execution
    • LLMs
      • Fine-tuned Adapters
      • Supported Models
    • Vector Databases
  • Prompts
    • Prompt Playground
  • Connections
  • LLM Fine-tuning
    • Basics
    • Using Adapters
    • Preparing Data
    • Supported Models
    • Parameters Guide
  • Knowledge Bases
  • Evaluations
    • Metrics
      • LLM-as-a-Judge
      • Predefined metrics
        • Faithfulness
        • Context Precision
        • Context Recall
        • Factual Correctness
        • Answer Correctness
      • Python Code Metrics
    • Datasets
    • Evaluation Runs
    • Examples
      • Build Accurate vs. Inaccurate Workflows
  • Examples
    • Building a Search Assistant
      • Approach 1: Single Agent with a Defined Role
      • Approach 2: Adaptive Orchestrator with Multiple Agents
      • Approach 3: Custom Logic Pipeline with a Straightforward Workflow
    • Building a Code Assistant
  • Platform Settings
    • Access Keys
    • Organizations
    • Settings
    • Billing
  • On-premise Deployment
    • AWS
    • IBM
    • Red Hat OpenShift
  • Support Center
Powered by GitBook
On this page
  • Core Components of LLM Agents
  • Key Features
  • Workflow Orchestration
  1. Low-Code Builder
  2. LLM Agents

Basics

PreviousLLM AgentsNextGuide to Implementing LLM Agents: ReAct and Simple Agents

Last updated 1 month ago

LLM agents represent an advanced AI paradigm where large language models are augmented with tools, memory, and decision-making processes to tackle complex tasks. Each agent functions autonomously, performing specific roles, interacting with tools, and dynamically adapting to achieve defined goals. These agents can be customized, and orchestrated to form cohesive workflows.

Core Components of LLM Agents

Base LLM

  • Acts as the primary language-processing engine.

  • Processes natural language inputs and generates relevant outputs.

  • Makes decisions and provides responses based on predefined prompts and roles.

Agents can leverage various tools to extend their capabilities:

Search Category

  • Tavily: For semantic search and general web information retrieval

  • Jina: AI-powered search capabilities

  • Exa: Knowledge-focused search tool

  • ScaleSerp: Structured search results from multiple engines

Scraping Category

  • ZenRows: Advanced web scraping with anti-bot protection

  • Jina: Intelligent content extraction

  • Firecrawl: High-performance web crawling and extraction

Execution Category

  • E2B Interpreter: For secure and isolated code execution

  • Python: For embedding custom logic, performing API calls, and running complex workflows

  • SQL Executor: For database querying and management

  • HTTP API Call: For connecting with external services or internal APIs

Tool Usage Examples

  1. Search Category: Use Tavily or ScaleSerp when the agent needs to retrieve real-time data from the web, like finding the latest news or gathering information on a specific topic.

  2. Scraping Category: Use ZenRows or FireCrawl to extract data from specific URLs when structured data from websites is required, such as collecting information from a list of articles or scraping details from an e-commerce site.

  3. Execution Category:

    • E2B is used for secure and isolated code execution where agents need to perform calculations or data transformations.

    • Python is ideal for embedding custom logic, performing API calls, and running complex workflows that involve data processing or integrating other custom functions.

  4. API Requests: Use the HTTP API tool to allow agents to connect with external services or internal APIs, supporting seamless integration with a wide range of web services.

Agent Types:

  • Simple Agent:

    • Handles straightforward input/output processing in single-turn interactions.

    • Limited to basic prompt handling without tool utilization.

  • ReAct Agent:

    • Designed for sophisticated, multi-step reasoning tasks.

    • Combines decision-making and execution in a single workflow.

    • Capable of handling more complex tasks and better tool utilization.

    • Includes configurations for iterative processing (e.g., max loops) and complex error handling.

  • Reflection Agent:

Enhances reasoning by adding self-assessment capabilities, allowing the agent to evaluate its own responses before finalizing outputs

Key Features

Memory Systems

  • Supports short-term memory for tracking conversation context within a single session.

  • Long-term memory for retaining important knowledge across sessions, enhancing personalization and continuity.

  • Context window management allows agents to summarize information and avoid memory overflow.

Prompting Mechanisms

  • Role-based prompting (e.g., "helpful AI assistant") specifies the general behavior and tone of the agent.

  • Task-specific instructions guide agents on how to execute particular types of requests.

  • System prompts enable developers to control agent behavior, providing an additional layer of customization.

Reflection Capabilities

  • Allows agents to evaluate their responses and adjust strategies accordingly.

  • Built-in error handling for more robust interaction.

  • Self-improvement mechanism enables agents to learn from past interactions and enhance response quality over time.

Configuring Agents for Specific Roles and Goals

Agents can be tailored for specialized tasks by defining their roles and goals explicitly. For example:

  • Role: Specifies the primary function or task focus (e.g., “Market Analyst” or “Customer Support Assistant”). Provides an objective, guiding the agent’s decision-making process (e.g., “Analyze sales trends” or “Assist users with account inquiries”)

Workflow Orchestration

Linear Orchestrator

  • Manages agents in a sequential, predefined flow

  • Ideal for tasks that follow a strict order

Adaptive Orchestrator

  • Allows dynamic branching based on real-time results

  • Enables conditional paths through the workflow

  • Adapts processing based on intermediate outputs

Graph Orchestrator

  • Provides the most flexible workflow management

  • Supports complex, non-linear agent interactions

  • Enables parallel processing and sophisticated decision trees

  • Allows for feedback loops and iterative refinement

Workflow orchestration allows developers to structure complex, multi-agent workflows where agents can pass information to each other, delegate tasks, or engage in sequential decision-making.

Tool Integration