GeneXus Next 2026.01 is expected to be officially released soon. A preview of this version was published on July 2, 2026, including Legacy - GeneXus for Agents as a key component.
Version: IDE 1.2.101 - BL version=19.2.362 - SERVICES 1.2.119
Download this version from the GeneXus Next Preview Channel
Below are described the main features.
Legacy - GeneXus for Agents supports GeneXus 18 Knowledge Bases.
With GeneXus for Agents you are not limited to Knowledge Bases created or opened with GeneXus Next: you can also open GeneXus 18 Knowledge Bases and develop changes to their objects, without needing the GeneXus Next IDE. Builds are run with the same GeneXus 18 installation that the Knowledge Base belongs to.
Learn more about this topic in Knowledge Base textual representation.
gxnext CLI is a new component of Legacy - GeneXus for Agents. It acts as an intermediary layer between the agentic CLI (for example, CODA CLI, Claude Code CLI, Codex CLI, or others) and the GeneXus MCP Server. You make natural-language requests to an agentic CLI, it executes gxnext commands, and gxnext CLI manages communication with the GeneXus MCP Server.
Note: The
gxnext CLI is installed automatically when you interact with the Agentic CLI using natural language, as the
Nexa skill contains the knowledge required to perform this task.
You can now start the GeneXus MCP Server directly from the IDE by selecting Tools > MCP Server > Start Server.
You can also stop it from Tools > MCP Server > Stop Server.
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.
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.
A /version endpoint is available to verify the GeneXus Business Logic (BL) version currently loaded by the MCP Server. Read more at: GeneXus version (BL used by the GeneXus MCP Server).
The BL and MCP log are now generated separately in the logs folder as a file independent from the IDE log.
For more information about these changes, see How to: start, configure, and use the GeneXus MCP server.
MCP Server and the BL now share the same settings.json file. Separate GeneXus MCP Server configuration files are no longer supported.
Note: This is a breaking change: MCP Server and BL configuration now use a shared settings.json file with a nested schema. Existing custom settings.json and settings-overrides.json files based on the previous format must be updated.
The settings-overrides.json file now has the highest precedence: its values override every other configuration source, including the environment variables injected at process start.
The text file structure has been updated to improve clarity, simplify the structure, and increase the completeness of the files that represent the Knowledge Base.
New supported objects include: Data View, Panel, XML Report, Image and Language.
Warning: This is a breaking change. You must delete the src, src.ns, and ref folders before starting to work with the new format. Be aware that any object that exists only in text format and has not yet been imported into the Knowledge Base may be lost during this process. Therefore, it is recommended to verify beforehand that all relevant changes have been incorporated into the KB before deleting these directories.
This change impacts Team Development workflows, text export/import processes, branch diff comparisons, and any custom scripts or automations based on the previous format, which may require updates.
Read more at Knowledge Base textual representation.
When you log in to GeneXus Next, your organizations and teams are listed so you can select the ones you want to work with.
If you already have an organization, it is listed at login as usual. If you are a new user who does not have an organization yet, one is now created for you automatically, so the organization list is never empty when you start working.
The active organization and team are shown in the status bar (with icons and tooltips); clicking them lets you switch your organization or team at any time
The GeneXus Next Desktop installer for Windows now installs its own prerequisites:
- .NET 8
- Visual C++ 2015-2022 runtime
- SQL Server LocalDB (optional)
The setup also sets the GXNEXT_MCP_SERVER_EXE environment variable on install.
This version supports the creation of Backend-Only Knowledge Base for projects that do not require a user interface (UI) or that use other technologies to implement the UI.
The New Environment flow is also Backend-Only aware: when the current KB is Backend-Only, frontend generators are automatically unchecked and disabled, and the default frontend generator is locked.
Read more at Backend-Only Knowledge Base
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
The new File > Open Knowledge Base submenu lets you open KBs from arbitrary paths via .gxw selection. In addition, the new KB dialog lets you pick the target directory on the native desktop, and an ad-hoc catalog records non-default locations so they survive reinstalls.
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.
When creating a Knowledge Base from GeneXus Server, you can now select where the local copy of the Knowledge Base will be stored, either in the Default GeneXus Next location or in a Custom directory. For more information, read: SAC #61571.
When creating a Knowledge Base, GeneXus Next can now discover local and remote SQL Server instances across platforms. There is an advanced tab where you can select and configure the target instance.
- OpenAPI TAG property on API objects
Allows customization of the tag value emitted in the OpenAPI definition, including support for multiple tags.
- Expanded source syntax
Support added for Boolean and date constants, constants for enumerated domains, and case-insensitive parameter prefixes (in:, inout:, out:).
GeneXus Next no longer seeds hidden data store defaults (such as sql / SA) on the Windows platform. You now configure the database explicitly on the first build, instead of inheriting bundled defaults that were not visible.
Before any build or run that touches the database, GeneXus Next detects when the environment's data store is missing required connection properties and opens a configurator dialog so you can set them up inline, instead of failing midway through the operation. Each property is shown with the appropriate input control (text, password, checkbox, combo, etc.).
Direct access to IDE diagnostics from the Help menu.
The Start Page (desktop app on Windows) now displays the KB path next to its name when the KB lives outside the default directory, making KBs in custom locations easier to identify.
- Disable implicit analytics data collection
- New AnalyticsImplicitDataCollectionEnabled mobile property turns off automatic data collection by the analytics provider.
- Support for gradients defined in the Design System Object (DSO).
- New optional scale parameter added for decimal conversion in the iOS generator.
- New Swift collection methods supported by the Swift generator.
- The macOS x64 installer is no longer distributed, while the macOS arm64 version remains available. The decision was based on the low adoption rate of the macOS x64 version and the availability of an alternative: GeneXus Next Desktop Browser App (containerized and browser-based). (SAC #61528(https://www.genexus.com/en/developers/websac?data=61528;;))
First bits of this version
- .NET MCP Server for API Objects
- MySQL 9 with embedding data type