The Belief-Desire-Intention (BDI) model is a prominent software architecture for intelligent agents based on the philosophical theory of practical reasoning, where an agent's behavior is governed by its beliefs about the world, its desires (goals), and its intentions (committed plans). This model provides a clean abstraction for building agents that can reason about their actions, select plans from a library to achieve goals, and commit to executing those plans while continuously monitoring for success or failure.
Glossary
Belief-Desire-Intention (BDI) Model

What is the Belief-Desire-Intention (BDI) Model?
A foundational architecture for building rational, goal-directed autonomous agents.
In a multi-agent system, BDI agents operate through a continuous loop: they update their beliefs from percepts, generate desires from goals, filter options to form intentions, and execute intended actions. Key to its engineering utility is the separation between the agent's internal reasoning state and its plan library, enabling modular design. Frameworks like JADE and Jason implement this model, providing structures for agent communication, plan selection, and handling interruptions when beliefs change, making it a cornerstone for building explainable, deliberative agent systems.
Core Components of a BDI Agent
The BDI (Belief-Desire-Intention) model structures an intelligent agent's decision-making around three core mentalistic constructs. This architecture enables practical reasoning by continuously updating internal states and selecting plans to achieve goals.
Beliefs
Beliefs represent the agent's internal model of the world, including facts, perceptions, and inferred knowledge. This is a dynamic knowledge base that is continuously updated through sensors or communication.
- Function: Serves as the agent's informational state.
- Representation: Often implemented as a set of logical propositions or a knowledge graph (e.g.,
location(robot, room_a),battery_level(75%)). - Key Property: Beliefs can be incomplete, uncertain, or incorrect, mirroring realistic perception limitations.
Desires (Goals)
Desires, or goals, are the motivational states representing the outcomes the agent is designed to achieve. They define the agent's objectives, which may be generated internally or assigned by a user/system.
- Function: Drives the agent's planning and action selection.
- Types: Can be achievement goals (reach a target state) or maintenance goals (keep a condition true).
- Management: Goals can be added, removed, or prioritized. Conflicting goals require resolution strategies.
Intentions
Intentions are the plans of action to which the agent has committed. They represent the bridge between deliberation (choosing a plan) and means-ends reasoning (executing it).
- Function: Focuses the agent's resources on a specific course of action.
- Persistence: An intention typically persists until the goal is achieved, the plan becomes impossible, or a higher-priority goal intervenes.
- Implementation: Often a stack of partially instantiated plan steps being executed.
The Practical Reasoning Loop
The BDI agent operates via a continuous practical reasoning loop, which is the core execution cycle:
- Belief Revision: Update beliefs based on new percepts.
- Option Generation: Determine which plans (options) could achieve current goals, given updated beliefs.
- Filtering: Select which options to commit to as new intentions.
- Execution: Act on the current intention, performing the next step in the chosen plan.
This loop runs continuously, allowing the agent to be reactive to environmental changes while remaining goal-directed.
Plan Library
A plan library is a pre-defined repertoire of recipes or procedures the agent can use to achieve its goals. Plans are typically structured as condition-action rules.
- Format:
Trigger : Context <- Body. The Trigger is a goal or event, the Context is a set of beliefs that must be true for the plan to be applicable, and the Body is the sequence of actions or sub-goals. - Example Plan:
Goal(deliver(package)) : Belief(at(robot, warehouse)) <- navigate_to(loading_dock); load(package); navigate_to(destination); unload(package). - The agent selects the most relevant plan from this library during the option generation phase.
How the BDI Reasoning Cycle Works
The BDI reasoning cycle is the core execution loop of a Belief-Desire-Intention agent, a prominent architecture for intelligent agents in multi-agent systems.
The BDI reasoning cycle is a continuous, three-phase loop that governs an autonomous agent's decision-making. First, in the belief revision phase, the agent updates its internal model of the world (beliefs) based on new sensor data or messages. Next, during option generation, it evaluates its current beliefs against its overarching desires (goals) to produce a set of possible plans (options). Finally, in the filtering phase, it selects and commits to a specific, executable plan, formalizing it as an intention to be acted upon.
This cycle enables practical reasoning, balancing reactivity to environmental changes with commitment to longer-term goals. The agent's intentions persist until they are achieved, deemed impossible, or irrelevant, at which point the cycle repeats. This architecture is foundational in multi-agent system orchestration, allowing heterogeneous agents to pursue individual objectives while contributing to collective outcomes through structured interaction and agent coordination patterns.
Frequently Asked Questions
The Belief-Desire-Intention (BDI) model is a foundational software architecture for building rational, goal-driven autonomous agents. It provides a formal framework for practical reasoning, where an agent's actions are determined by its internal mental states. These FAQs address its core principles, implementation, and role in modern multi-agent systems.
The Belief-Desire-Intention (BDI) model is a software architecture and theoretical framework for designing intelligent agents based on the philosophical theory of practical reasoning. In this model, an agent's behavior is governed by three core mental attitudes: its Beliefs (its knowledge about the world, which may be incomplete or incorrect), its Desires (its overarching goals or objectives), and its Intentions (the specific plans it has committed to executing to achieve those goals). The agent continuously perceives its environment to update its beliefs, selects relevant desires (goals), and then commits to intentions (plans) that it reasons will achieve those goals, forming a continuous perception-reasoning-action loop.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
The BDI model is a foundational architecture for rational agents. These related concepts define the broader ecosystem of agent design, communication, and coordination within which BDI agents operate.
Intelligent Agent
An intelligent agent is the core abstraction: an autonomous software entity that perceives its environment, reasons about it, and acts to achieve goals. The BDI model provides one specific architecture for implementing such an agent's internal reasoning loop.
- Key Components: Sensors (input), effectors (output), and a reasoning engine.
- BDI Relationship: A BDI agent is a type of intelligent agent where reasoning is explicitly structured around beliefs, desires, and intentions.
Agent-Oriented Programming (AOP)
Agent-Oriented Programming (AOP) is a programming paradigm where the primary building blocks are autonomous agents, their mental states (like beliefs and intentions), and their communication acts. It provides the linguistic and methodological framework for implementing architectures like BDI.
- Core Abstraction: Agents as entities with mentalistic attitudes.
- Implementation: Languages like Jason or platforms like JADE provide AOP environments where BDI concepts are first-class citizens.
Agent Architecture
Agent architecture defines the internal structural blueprint of an agent. The BDI model is a prominent deliberative architecture, contrasting with purely reactive or hybrid models.
- Reactive Architecture: Uses simple condition-action rules (e.g., if percept then action).
- Deliberative (BDI) Architecture: Involves symbolic reasoning, planning, and commitment to goals.
- Hybrid Architecture: Combines reactive layers for speed with deliberative layers for complex planning.
Agent Communication Language (ACL)
An Agent Communication Language (ACL) is a standardized language for message exchange between agents, enabling interoperability. BDI agents use ACLs like FIPA ACL to communicate their mental states, such as informing others of beliefs or requesting actions based on intentions.
- Syntax & Semantics: Defines message structure (performative, sender, receiver, content) and meaning.
- Example: A BDI agent might send a
REQUESTperformative to delegate a sub-goal, or anINFORMto update another agent's beliefs.
Practical Reasoning
Practical reasoning is the philosophical and computational process of deciding what to do. It is the theoretical foundation of the BDI model, splitting the process into two stages:
- Deliberation: Deciding which goals to pursue (desires -> intentions).
- Means-Ends Reasoning: Deciding how to achieve them (intentions -> plans).
This mirrors the BDI cycle: filtering desires based on beliefs to form intentions, then selecting plans to fulfill those intentions.
Plan Library
A plan library is a predefined set of recipes or procedures that a BDI agent uses to achieve its intentions. Each plan is typically structured as a triggering condition, a context condition (based on beliefs), and a sequence of actions or sub-goals.
- Function: Provides the "how-to" knowledge for the agent.
- Selection: The agent's reasoning engine matches current intentions and beliefs to select an applicable plan from the library.
- Example: A delivery robot's plan library contains plans for
navigate_to(point),pick_up(package), andavoid_obstacle().

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us