When working with GeneXus for Agents, Knowledge Base objects must be exported as plain text describing their definitions, since Large Language Models (LLMs) work with text.
The Knowledge Base textual representation enables AI agents to analyze existing objects, generate new ones, understand relationships between them, suggest modifications, and apply GeneXus best practices, among other things.
To export a Knowledge Base to its textual representation, interact with the Agentic CLI using natural language; the Agentic CLI will then interact with the other GeneXus for Agents components.
You only need to ask the Agentic CLI to open the KB (without having to open the IDE). For example, you can use the following instruction:
Open the Travel Agency KB in the current folder
Note: The "current folder" is interpreted as the AI agent's working directory, so the TravelAgency KB is opened and the file representation of TravelAgency is synced into that directory.
The first time you request to open the KB, you are asked whether you want to export the KB objects as text files.
With the text files available on disk, you can ask anything about the KB: what objects it contains, how a particular object is structured, or how the objects relate to one another, and even edit existing objects or create new ones.
Note: After the KB is exported, the agent determines the GeneXus version by reading the ProductVersion value under the #Version region of the *.kb.gx file. It then uses that version to open the KB with the appropriate GeneXus installation.
The textual representation is organized into two subdirectories within the Knowledge Base structure :
The src subdirectory contains the exported Knowledge Base content.
- Directories prefixed with # represent system items, such as attributes, domains, files, images, and localization, among other types of content.
- Directories called @Name represent Folders objects, while Module objects are regular directories (without any prefix).
- Each module includes a module.toml file containing information such as its canonical name, identifiers, and relevant properties. Optionally, a README.md file can also be included for additional documentation.
- Objects contained within a module are stored inside that module's structure.
- Objects that do not belong to a folder or module are stored directly under the root of the src directory.
- Objects are represented by files called {name}.gx.
src
│
├─ #attributes
│ ├─ CountryId.gx
│ └─ CountryName.gx
│
├─ #categories
│ └─ MainPrograms.gx
│
├─ #designsystems
│ └─ TravelAgency.gx
│
├─ #documentation
│ └─ MainDocument.md
│
├─ #domains
│ └─ Id.gx
│
├─ #files
│ ├─ Monserrat.gx
│ └─ Monserrat.ttf
│
├─ #images
│ ├─ TravelAgencyLogo
│ │ ├─ TravelAgencyLogo@1x.png
│ │ ├─ TravelAgencyLogo@2x.png
│ │ └─ TravelAgencyLogo@3x.png
│ └─ TravelAgencyLogo.gx
│
├─ #localization
│ ├─ English.gx
│ └─ Spanish.gx
│
├─ #patternsettings
│ └─ WorkWith.gx
│
├─ #preferences
│ ├─ DevNETSQLServer.env.gx
│ ├─ DevNETSQLServer.local.env.gx
│ ├─ TravelAgency.kb.gx
│ └─ TravelAgency.local.kb.gx
│
├─ #tables
│ └─ Country.gx
│
├─ @Backoffice
│ ├─ Country
│ │ ├─ Country_DataProvider.gx
│ │ └─ WorkWithCountry.gx
│ └─ Country.gx
│
├─ @CustomerFacing
│ ├─ TravelAgency.gx
│ ├─ TravelAgency.md
│ └─ TravelAgency.xml
│
├─ General
│ ├─ #domains
│ │ └─ ...
│ ├─ Security
│ │ └─ ...
│ ├─ Services
│ │ └─ ...
│ ├─ GlobalEvents.gx
│ └─ module.toml
│
├─ AssistantAgent.gx
└─ CountryAPI.gx
The ref subdirectory contains referenced modules. For example:
ref
├─ GeneXus
│ ├─ Client
│ └─ Common
│ └─ Server
│ └─ Social
├─ (other installed modules)
Note: This content is read-only.