graph LR
Registry["Registry"]
ActionRegistry["ActionRegistry"]
RegisteredAction["RegisteredAction"]
ActionModel["ActionModel"]
SpecialActionParameters["SpecialActionParameters"]
MCP_Controller["MCP Controller"]
MCP_Client["MCP Client"]
Agent_Core_Controller["Agent Core/Controller"]
Registry -- "uses" --> ActionRegistry
Registry -- "manages" --> RegisteredAction
ActionRegistry -- "stores" --> RegisteredAction
RegisteredAction -- "encapsulates" --> ActionModel
SpecialActionParameters -- "extends or complements" --> ActionModel
MCP_Controller -- "registers tools with" --> Registry
MCP_Client -- "registers tools with" --> Registry
Agent_Core_Controller -- "queries" --> Registry
Agent_Core_Controller -- "executes actions from" --> Registry
click Registry href "https://github.com/CodeBoarding/GeneratedOnBoardings/blob/main/browser-use/Registry.md" "Details"
The Registry acts as the central hub for managing actions within the system, leveraging ActionRegistry for storage and RegisteredAction to encapsulate action details. ActionModel serves as the foundational Pydantic model for defining action parameters, ensuring data integrity. External components like MCP Controller and MCP Client interact with the Registry to register new tools, while the Agent Core/Controller queries the Registry to discover and execute available actions, forming the core operational flow of the system.
Registry [Expand]
The core service responsible for the lifecycle management of actions, including registration, normalization, and retrieval. It acts as the primary interface for defining and accessing the Agent's capabilities.
Related Classes/Methods:
browser_use.controller.registry.views:ActionRegistrybrowser_use.controller.registry.views:RegisteredAction
A data structure that serves as the repository for all registered actions, providing efficient lookup and storage.
Related Classes/Methods:
A data model representing a single action registered with the system. It encapsulates the action's metadata, including its name, description, and input parameters.
Related Classes/Methods:
The base Pydantic model for defining the input parameters of any registered action, ensuring type safety and validation. It includes methods for getting and setting an action's index.
Related Classes/Methods:
Defines the types and structure of context-specific parameters that are automatically injected into actions by the Agent's Controller during execution.
Related Classes/Methods:
A component responsible for integrating external tools defined via the Model Context Protocol (MCP) into the internal action registry by calling the Registry service.
Related Classes/Methods:
A component that also interacts with the Registry to register tools, likely for tools it discovers or provides to an MCP server, ensuring they are available to the Agent.
Related Classes/Methods:
The main Agent's Controller component that queries the Registry to discover available actions and then orchestrates their execution based on the Agent's reasoning.
Related Classes/Methods: