Table of contents
Official Content

The following sections describe the main features and projects currently under development by the GeneXus team.

Upcoming deliveries (late April / early May)

GeneXus for Agents: Support for GeneXus 18 Knowledge Bases

Since the publication of GeneXus Next 2026.01 (Preview) on March 31, GeneXus for Agents supports only GeneXus Next Knowledge Bases. Support for GeneXus 18 Knowledge Bases is currently being implemented.

(*) GeneXus 18 Knowledge Bases can be used by performing a checkout with GeneXus Next, working on the resulting working copy, and then committing the changes back to GeneXus Server. Several projects are already using this approach. This feature refers to full and direct work with V18 KBs.

Knowledge Base (KB) folders

When using GeneXus Next, Knowledge Bases are currently accessible only through a predefined folder configured through the settings.json file. Support is being implemented to allow creating and opening Knowledge Bases from any folder on the computer, similar to how it works in GeneXus 18.

Note: Available in the Canary channel.

Improvements to Nexa (built into the IDE)

GeneXus Next includes an assistant called Nexa, which can be used directly from the IDE. Several improvements are being implemented to enhance its capabilities and user experience.

Note: Available in the Canary channel.

Support for creating Knowledge Bases in backend-only mode

A backend-only KB is a Knowledge Base focused exclusively on backend functionality (DB, APIs, procedures, data providers, business logic), without UI/frontend-related components. This reduces the number of objects included by default in the KB, and improves efficiency during generation, compilation, and related processes.

When creating a KB through the MCP Server, it is backend-only by default (parameter BackendOnly: "true"). In the IDE, the KB type depends on whether you select any frontend options in the dialog. When using the MSBuild task, a regular KB (backend and frontend) is created by default. If needed, use the BackendOnly="true" parameter.

Note: Available in the Canary channel.

Access to the KB through a command-based CLI

We are moving from using MCP to directly executing commands (CLI/Bash) in order to gain better feedback in the CLI (streaming) and improved connection stability.

Warning: This is a breaking change. MCP will no longer run on port 8001 and will instead be accessed directly through a command path. MCP registration is no longer required.
Note: Available in the Canary channel.

Architectural changes

Since GXWEB_BL_VERSION = bl-185-services1.2.80 (May 8, 2026), the GeneXus MCP Server is no longer hosted inside the GeneXus services host on port 8001. It now runs as an independent process, GeneXus.PIA.McpServer.exe, using port 1989 by default, with its own /mcp endpoint.

The 404 error returned by :8001/mcp is expected because that route no longer exists there.

How to connect
http://localhost:1989/mcp

Additionally, the BL log is now generated separately in the logs folder as a file independent from the IDE log.

For more information about these changes, see How to: Install and use the GeneXus MCP server.

Note: Available in the Canary channel.

Planned/working on

GeneXus for Agents: Form support

When using GeneXus for Agents, object forms are exported and imported as part of the GeneXus objects. However, Nexa is currently unable to create or modify these forms. Support for this functionality is being implemented.

Improvements to KB objects generated as text

The text file structure is being updated to improve clarity, simplify the structure, and increase the completeness of the files that represent the Knowledge Base (e.g., support for Image and DataView objects).

Adding GAM to available skills

As of April 2026, published skills do not include GAM knowledge. As a result, the CLI/LLM relies on public internet sources. A dedicated GAM skill will reduce inaccuracies and hallucinations.

Last update: December 2025 | © GeneXus. All rights reserved. GeneXus Powered by Globant