Xojo 2026r3 Adds Agentic Mode for Claude Code, 3 Agents [2026]
![Xojo 2026r3 Adds Agentic Mode for Claude Code, 3 Agents [2026]](https://trendintech.com/wp-content/uploads/2026/10/xojo-2026r3-agentic-mode-ai-coding-agents-2026-gen.webp)
Xojo, Inc. shipped Xojo 2026 Release 3 on October 20, 2026, and the headline feature is not a new control or a faster compiler. It is Agentic Mode, a capability that lets AI coding agents such as Claude Code write, run, and fix Xojo applications from inside the IDE itself. The move puts a 30-year-old cross-platform development tool squarely in the middle of the industry’s biggest argument: whether AI agents belong inside the editor, or whether they should stay in a terminal window next to it.
Xojo is a niche player next to Microsoft’s Visual Studio Code or Cursor, but its move is a useful signal. Smaller, independent tool vendors are now racing to wire agentic AI directly into their IDEs rather than waiting for AI labs to build universal plugins. For developers tracking the broader shift toward AI-assisted coding, covered recently in pieces on GitHub Copilot’s race against Cursor and the rise of local AI agent routing tools, Xojo 2026r3 is a small but telling data point about how fast “agent inside the IDE” is becoming the default expectation rather than a novelty.
Don't miss new tech stories on Google
Add TrendinTech once in the Google app and our stories appear in your news suggestions.
What Xojo 2026 Release 3 Actually Changes
Xojo’s official announcement, published October 20, 2026 and picked up by Yahoo Finance and PR Newswire, describes Agentic Mode as a feature that lets a developer’s “favorite coding agent” work directly with the Xojo IDE rather than being limited to editing text files from outside it. In practice, that means an AI agent connected to Xojo can modify a project’s source, trigger the IDE to automatically reload whatever changed (either the whole project or just the individual items that were edited on disk), run the application, and read back any compiler errors it produces.
That loop, write code, run it, read the compiler’s output, try again, is the mechanism Xojo founder and CEO Geoff Perlman described when the release went live: “An agent can write code, run the project, read the compiler’s feedback, and keep going, freeing developers to focus on the creative work,” according to the company’s announcement carried by PR Newswire. Perlman also framed the feature as a continuation of the company’s long-standing design philosophy, saying “Xojo has always aimed to abstract users from the complexity of development, and Agentic Mode is our next big step.”
Developers can turn the feature on through File > Agentic Mode inside the IDE. Xojo has not published a separate price for the feature, and the company’s existing pricing structure stays in place: Xojo remains free for learning, for development, and for building Linux and Raspberry Pi applications, while Xojo Pro and Pro Plus licenses start at $999, per the company’s own release materials cited by Yahoo Finance.
Agentic Mode vs. Jade: Two Different AI Features, Not One
It is easy to conflate Agentic Mode with Jade, Xojo’s existing built-in AI assistant, but the company is keeping them as separate capabilities. Jade was introduced with Xojo 2025 Release 3 in December 2025 and has been iterated on steadily since: Xojo 2026 Release 1 in March 2026 switched Jade’s default model to Anthropic’s Claude Sonnet 4.6 and added conversation compaction, and Xojo 2026 Release 2 in July 2026 gave Jade support for OpenAI GPT models, local models, and awareness of project context such as source files and compilation errors.
Release 3 does not replace Jade with Agentic Mode. Instead, Jade gets incremental reliability work in this release: better copy-and-paste support to and from text, improved handling of special characters on Windows, and more dependable handling of longer-running AI requests. Agentic Mode, by contrast, is built for external agents, including Claude Code, Google’s Gemini Code Assist, and OpenAI’s Codex, to drive the IDE from outside rather than chat with a developer inside a side panel. Xojo signaled this direction back on April 1, 2026, when it marked the company’s 30th anniversary and said it was adapting the IDE to work with those three agent ecosystems specifically.
Xojo blog author Ricardo Cruz summed up the release’s priority plainly: “Agentic Mode is one of the big additions in 2026r3,” according to the company’s own blog. The distinction between an assistant that talks to a human and an agent that drives the IDE directly is the same split showing up across the industry, from VS Code’s agent host policies to standalone orchestration layers built to run several coding agents side by side.
The Compiler Feedback Loop, Explained
The technical core of Agentic Mode is what Xojo calls a compiler-feedback loop, and it is worth walking through because it is the part other IDE vendors will likely copy. In a conventional AI-coding setup, an agent edits a file, and a human (or a separate automated process) has to compile or run that file to see if it works. Agentic Mode collapses that gap inside Xojo’s own IDE:
- The agent edits one or more files in a Xojo project on disk.
- The Xojo IDE detects the change and reloads either the entire project or just the modified items, without the developer needing to reopen anything.
- The agent triggers a run of the project directly from the IDE.
- If the code does not compile, the IDE surfaces the compiler error back to the agent.
- The agent reads that error and attempts another fix, repeating the cycle until the project runs.
Xojo documents the mechanics of this handshake in a companion GitHub repository called the Xojo Project Format Reference, which the company updated on October 20, 2026 alongside the main release. The repository is explicitly described as a reference for AI agents that need to understand valid Xojo project file structures and syntax, not a set of starter templates for human developers. Xojo also published updated release notes at documentation.xojo.com detailing the surrounding Xojo Web changes that shipped in the same build.
What Else Shipped in 2026 Release 3
Agentic Mode got the headline, but Release 3 is also a substantial Xojo Web update on its own. According to Xojo’s official blog post dated October 20, 2026, the release adds a new WebApplication.AddURLRoute method for handling URL-based routing inside Xojo web apps, expands the WebFileUploader control with new methods and properties, and adds layout-editor canvas previews for WebCanvas. The same post reports more than 40 bug fixes specific to the Web framework.
One change is being called out by Xojo itself as behavior-breaking: in 2026r3, an unhandled exception now terminates a running web application outright, unless the relevant UnhandledException event explicitly returns True. In earlier Xojo Web releases, an unhandled exception did not necessarily take the whole app down. Developers upgrading existing Xojo Web projects will want to check their exception handlers before deploying a 2026r3 build to production, since the default behavior has flipped from tolerant to strict.
Community members on the Xojo forum have already started sharing examples built with a new DesktopTable control that shipped in the same release, and a separate forum thread from early October reported that a WebKit-related missing-library issue affecting iOS targets was addressed during the 2026r3 beta cycle, though that fix was discussed by developers on the forum rather than confirmed in Xojo’s own release notes.
Table: Xojo 2026 Release Timeline
| Release | Date | Key AI-related change |
|---|---|---|
| Xojo 2025 Release 3 | December 9, 2025 | Jade, Xojo’s built-in AI assistant, introduced |
| Xojo 2026 Release 1 | March 31, 2026 | Jade’s default model switched to Claude Sonnet 4.6; conversation compaction added |
| Xojo 2026 Release 2 | July 2026 | Jade gains OpenAI GPT support, local model support, and project-context awareness |
| Xojo 2026 Release 3 | October 20, 2026 | Agentic Mode launches for external coding agents; Jade gets reliability fixes |
How Agentic Mode Compares to Other Agent-in-the-IDE Approaches
Xojo is a small vendor compared to Microsoft, GitHub, or Cursor’s parent Anysphere, but the underlying design question it is answering, how deeply should an AI agent be allowed to reach into an IDE’s build and run cycle, is the same one playing out across much larger products. Microsoft’s own experiment in this space, covered in Microsoft Scope’s open-sourced coding-agent testing framework, focuses on letting multiple agents be evaluated against the same codebase rather than wiring one agent permanently into a single editor’s run loop. VS Code’s newer agent host policies, meanwhile, are aimed at letting organizations control which agents are allowed to act autonomously inside a shared developer environment, a governance problem Xojo’s single-vendor, single-IDE model does not yet have to solve at scale.
Tools built specifically to coordinate several coding agents at once, like the orchestration layer described in coverage of BAND’s agent coordination platform, point to a different future: one where a developer’s IDE is agent-agnostic and a separate orchestration layer decides which agent handles which task. Xojo’s approach is narrower by design. Agentic Mode is built into one IDE for one language ecosystem, and it explicitly supports a short list of named agents (Claude Code, Gemini Code Assist, and OpenAI Codex) rather than acting as a universal connector.
That narrower scope has a practical upside: Xojo controls both sides of the handshake, the IDE and the project file format, so it can guarantee the compiler-feedback loop actually works end to end. Broader, cross-editor agent frameworks have to handle many more edge cases because they were not designed by the same team that owns the compiler.
Table: Agentic Mode vs. Jade, Side by Side
| Feature | Agentic Mode | Jade |
|---|---|---|
| Introduced | October 20, 2026 (Xojo 2026r3) | December 9, 2025 (Xojo 2025r3) |
| Who drives it | External coding agents (Claude Code, Gemini Code Assist, OpenAI Codex) | Developer, chatting directly inside the IDE |
| Core function | Edit, reload, run, and read compiler errors on a Xojo project | Conversational AI assistance with project context |
| Model support | Depends on the connected external agent | Anthropic Claude (default), OpenAI GPT, OpenRouter, local models |
| Access point | File > Agentic Mode | Built-in Jade panel |
| Separate price | None confirmed; included with Xojo license | None confirmed; included with Xojo license |
Historical Context: 30 Years of Xojo
Xojo, Inc. marked its 30th anniversary on April 1, 2026, a milestone the company used to frame where it sees itself headed next. The company’s own anniversary post noted that only about 5% of businesses last 30 years, and that the figure drops closer to 1% in the technology industry specifically, a point Xojo made while describing itself as a member of that small group. Founder and CEO Geoff Perlman has led the company since it began building what was originally a Visual Basic-style cross-platform tool, long before “cross-platform” meant shipping to desktop, web, iOS, and Raspberry Pi targets from one codebase, which is the scope Xojo covers today.
That anniversary post is also where Xojo first signaled its AI direction in public, stating plans to adapt the IDE to work with Claude Code, Gemini Code Assist, and OpenAI Codex months before Agentic Mode actually shipped. Jade’s own history traces a similar arc: it launched supporting a single default model, then expanded release by release to add alternate providers, local-model support, and finally project-context awareness in July 2026, before Agentic Mode arrived as a separate, more hands-off capability in October.
Seen against that history, Agentic Mode looks less like a sudden pivot and more like the next step in a roadmap Xojo had already been building toward for at least six months. The company’s willingness to let outside agents, not just its own Jade assistant, operate the IDE is the bigger shift, and it mirrors how tools once built around a single in-house AI feature are increasingly opening the door to whichever agent a developer already prefers, a pattern also visible in the broader AI coding tools market tracked in reporting on the ongoing contest between Cursor and Claude Code.
Market Impact: What This Means for Independent IDE Vendors
Xojo’s addressable market is small compared to Visual Studio Code’s installed base, but Agentic Mode matters as a signal of where the pressure in developer tooling is coming from. Independent, paid IDE vendors like Xojo do not have the resources to build their own frontier AI models, so their competitive strategy increasingly has to be: build the best possible handshake between an IDE’s own compiler and whichever agent a developer already pays for elsewhere. That is a meaningfully different bet than trying to out-build Microsoft’s or Google’s in-house coding assistants.
It also raises the bar for what “AI support” means in a developer tool listing. A chat sidebar that answers questions about a codebase, which is roughly what first-generation IDE AI assistants like the original Jade did, is no longer the ceiling. The expectation Xojo is now setting, an agent that can edit code, trigger a build, read the actual compiler output, and retry without a human relaying each step, is a harder target, and it is one that smaller vendors in adjacent tool categories (database IDEs, API testing tools, niche language ecosystems) will likely feel pressure to match over the next year.
For teams already using Xojo in production, particularly in verticals like line-of-business desktop software where Xojo has a long-standing presence, Release 3’s non-AI changes carry real near-term weight too. The default behavior change around unhandled exceptions in Web apps is the kind of thing that can break a production deployment if a team upgrades without re-checking its exception handling, independent of whatever the agent-facing headline feature does.
The Emerging Third-Party Ecosystem Around Agentic Mode
Xojo’s community has not waited for Agentic Mode to be officially released to start building around the idea of agents driving the IDE. A community-built plugin called xojo-tools appeared on the Xojo forum in late August 2026, adding agent skills for editing Xojo projects, controlling the IDE, looking up documentation, and migrating code between Xojo’s older API 1.0 and newer API 2.0. That kind of grassroots tooling, built before the official feature even shipped, suggests real developer demand for exactly the capability Xojo formalized in Release 3.
Third-party plugin maker MonkeyBread Software also released version 26.4 of its MBS Xojo Plugins on September 22, 2026, and a separate community project, XPackager, a free macOS installer builder written in Xojo, appeared in early October. None of these are official Xojo releases, but together they show an ecosystem that has kept building steadily around Xojo through 2026, even as the broader developer-tools conversation has been dominated by much larger players.
Risks and Open Questions
Xojo has not published pricing specific to Agentic Mode, which leaves open whether heavier agent usage, more frequent project reloads, more automated run-and-fix cycles, could eventually come with its own cost tier, the way AI features at larger software vendors often do after an initial free rollout. The company has also not detailed any rate limits or safeguards on how often an agent can trigger a project run through Agentic Mode, which matters for teams worried about runaway agent loops repeatedly rebuilding a project.
There is also the open question of scope creep in the other direction: whether Agentic Mode stays focused on the compiler-feedback loop Xojo describes today, or expands toward deeper autonomous changes, like an agent restructuring a project’s architecture without a developer reviewing each step. Xojo has not announced plans either way, and the feature as documented on October 20, 2026 is scoped specifically to editing, reloading, running, and reading compiler errors, not broader autonomous refactoring.
Predictions: Where Agentic IDE Features Go Next
A few trends are likely to follow from Xojo’s move, based on the pattern already visible across the IDE market this year:
- More independent and niche IDE vendors will add a dedicated “agentic” toggle rather than folding agent access into an existing AI-assistant feature, following the same Agentic Mode vs. Jade split Xojo chose.
- Compiler-feedback loops, where an agent reads real build errors rather than relying on static analysis alone, will become a baseline expectation for any IDE marketing itself as AI-agent friendly.
- Expect more IDEs to explicitly name-check a short list of supported external agents, similar to Xojo’s references to Claude Code, Gemini Code Assist, and OpenAI Codex, rather than claiming universal agent compatibility.
- Pricing clarity for agent-driven IDE features will likely lag the features themselves by at least one or two release cycles, mirroring how Xojo has not yet published a separate Agentic Mode price.
- Community-built tooling, like Xojo’s xojo-tools plugin, will keep appearing ahead of official vendor features, since developers are not waiting for formal support to start experimenting with agent-driven workflows.
What Developers Should Check Before Upgrading
Anyone running Xojo Web projects in production should review their UnhandledException event handlers before moving to 2026r3, given the new default where an unhandled exception now terminates the app unless that event explicitly returns True. Teams on macOS should also be aware of the ListBox drag-and-drop hang reported on macOS 27.2, which affects drag operations inside the Xojo IDE itself; Xojo’s issue tracker lists the underlying bug as already addressed, though developers upgrading both their OS and their IDE around the same time should test drag interactions directly.
Teams interested in Agentic Mode specifically should start by connecting one of the three named supported agents, Claude Code, Gemini Code Assist, or OpenAI Codex, through File > Agentic Mode, and test the compiler-feedback loop on a small, non-critical project before relying on it for larger builds. Given how recently the feature shipped, best practices around how much autonomy to grant an agent inside a live project are still being worked out by the community in real time.
Frequently Asked Questions
What is Xojo’s Agentic Mode?
Agentic Mode is a feature in Xojo 2026 Release 3, launched October 20, 2026, that lets external AI coding agents, including Claude Code, Gemini Code Assist, and OpenAI Codex, modify a Xojo project, trigger the IDE to reload changes, run the project, and read compiler errors so the agent can keep iterating.
Is Agentic Mode the same thing as Jade?
No. Jade is Xojo’s built-in AI assistant, introduced in December 2025, designed for a developer to chat with directly inside the IDE. Agentic Mode is a separate capability built for external coding agents to drive the IDE on their own, and it shipped alongside incremental reliability improvements to Jade rather than replacing it.
How much does Agentic Mode cost?
Xojo has not published a separate price for Agentic Mode. The company’s existing pricing stands: Xojo is free for learning, development, and for building Linux and Raspberry Pi apps, while Xojo Pro and Pro Plus licenses start at $999, according to Xojo’s own release materials.
Which AI coding agents work with Xojo’s Agentic Mode?
Xojo has named Claude Code, Google’s Gemini Code Assist, and OpenAI’s Codex as the agents Agentic Mode is designed to work with, a direction the company first signaled in its April 2026 30th-anniversary announcement.
What else is new in Xojo 2026 Release 3?
Beyond Agentic Mode, 2026r3 adds a WebApplication.AddURLRoute method for Xojo Web routing, expands the WebFileUploader control, adds WebCanvas layout-editor previews, includes a new DesktopTable control, and ships more than 40 Web-related bug fixes. It also changes default behavior so an unhandled exception now terminates a Web app unless the UnhandledException event returns True.
Does upgrading to 2026r3 break existing Xojo Web apps?
It can, specifically around exception handling. Because an unhandled exception now terminates the app by default, developers should review their UnhandledException event handlers before deploying a 2026r3 build, since earlier versions did not necessarily shut down the whole app in that situation.
Is there a known bug with Xojo 2026r3 on macOS?
Xojo forum users reported that ListBox drag-and-drop operations could hang the IDE and other apps under macOS 27.2. Xojo’s issue tracker lists the underlying bug as addressed, but developers running both macOS 27.2 and Xojo 2026r3 should test drag interactions directly before relying on them.
How does Xojo’s approach compare to other AI-assisted IDEs?
Xojo’s Agentic Mode is narrower than cross-editor orchestration tools: it is built into a single IDE for a single company’s language ecosystem and names a short list of supported agents rather than claiming universal compatibility. That narrower scope lets Xojo guarantee its compiler-feedback loop works end to end, since the company controls both the IDE and the underlying project file format.
Related Coverage
Yusuf Demir
Yusuf Demir is the Cloud & Software Reporter at TrendinTech, where he covers cloud infrastructure, enterprise platforms, developer tools and the digital transformation of businesses in the UK and the United States. He is most interested in the gap between vendor roadmaps and the systems engineers actually run, and in what the cloud bill looks like once the free credits expire.
All stories by Yusuf Demir (407)![AI Writes Half the Code for 42% of Developers [2026]](https://trendintech.com/wp-content/uploads/2026/10/ai-writes-half-code-42-percent-developers-2026-gen-640x360.webp)
![White House S&T Plan Taps 15 Agencies for AI Coding [2026]](https://trendintech.com/wp-content/uploads/2026/10/white-house-national-security-st-strategy-ai-coding-agents-2026-gen-640x360.webp)
![TornadoVM 7.0 Hits 74x Java GPU Speedup With cuTile [2026]](https://trendintech.com/wp-content/uploads/2026/10/tornadovm-7-0-java-gpu-cuda-cutile-2026-gen-640x360.webp)