adk

Botpress ADK conventions require placing code in a src/ directory structure with actions, tools, workflows, conversations, tables, triggers, and knowledge bases. Features rely on frontmatter, exports, and agent.config.ts to register automatically for reliable discovery.

To convert Botpress actions to tools, follow ADK guidelines that outline necessary frontmatter, exports, and file structure. This standardizes how features are built and organized, ensuring tools are properly exposed for reliable execution in ADK-powered bots.

Yes, Botpress ADK integrates with the Zai library and other runtime utilities. The ADK guidelines outline how to adopt this integration, providing practical patterns and examples to accelerate development, debugging, and maintenance of your ADK-powered bots.

Scaffold your ADK feature by placing code under proper directories like src/actions and src/workflows. Rely on frontmatter, exports, and convention-based layouts to register features automatically, accelerating development while ensuring consistent structure across all primitives.

Yes, you can manage knowledge bases and conversation tables using Botpress ADK. The framework provides a centralized reference for these primitives, outlining necessary frontmatter and file structures to standardize how features are built, organized, and discovered.

ADK features may not be discovered if they lack necessary frontmatter, exports, or correct file structure under the src/ directory. The ADK guidelines codify official practices to standardize these elements, ensuring reliable discovery and execution of your actions and workflows.