Overview
Several mechanisms appear across the workflows.
Skills provide procedural instructions.
A browser-use skill, for example, tells the agent how to perform browser actions. The skill explains the workflow; it is not the browser connection itself.
Plugins or integrations provide external capability.
The system can install connections for functions such as databases, repositories, hosting, media generation, academic data, or other services. Installation may require login, an access token, or approval of permissions.
Local execution provides file and application access.
A desktop agent can work in local folders and use local applications. Because it can change local files, it may also delete or overwrite them. The system therefore exposes a permission choice: ask before each action or grant full access.
Browser control provides direct interaction with a web session.
A browser extension can connect the agent to a browser. The controlled tab is visibly marked, and removing the extension removes the agent's browser-control capability.
Recovery mechanisms provide a way back.
The cloud-agent setup included restart, reset, backup, and restore controls. These mechanisms matter because agent processes can become stuck or produce unwanted changes.