Objo Studio 26.8.5 Released
The latest and greatest version of Objo Studio is available to download now:
This is a particularly big release. It fixes all 24 reported bugs and adds 18 new features and improvements. Two additions stand out: the new Worker project type and support for external coding agents through the Model Context Protocol (MCP).
Together, they significantly expand both what you can build with Objo and how you can build it.
The full changelog has every detail, but I want to introduce these two headline features here. I’ll also be publishing separate articles exploring each of them in much greater depth.
Worker projects: real multicore Objo applications
Objo applications can now distribute work across multiple processor cores using Worker projects.
A Worker is a new project type that lives alongside the Desktop and Command Line projects in your solution. Each Worker runs in its own child process with a separate Objo VM, heap, globals and standard-library state. A WorkerPool can keep several of these processes running simultaneously, allowing genuinely parallel execution across the available CPU cores.
This is ideal for CPU-intensive or blocking workloads such as crawling websites, parsing large datasets, indexing content, compressing files, processing media or performing expensive calculations. The controlling application remains responsive while the Workers handle jobs in the background.
Workers are deliberately straightforward to use. This is not just a basic process-launching API. Worker pools have bounded queues, progress reporting, cooperative and forced cancellation, dynamic resizing, retries for unexpected process failures and detailed remote error information. If a process crashes, the pool replaces it so later jobs can continue.
Workers are also fully integrated with Studio’s debugger. You can place breakpoints and watchpoints inside Worker code, step through an individual Worker, inspect its call stack and variables, and switch between several running processes from the debugger. Remote debugging works too, without opening additional ports.
Workers are one of the largest additions to the Objo runtime so far, and I’ll be covering their design and practical use in a dedicated follow-up article.
External coding agents through MCP
The second headline feature completes the groundwork introduced in 26.8.4: Objo Studio can now connect external coding agents to a live solution through the Model Context Protocol.
This allows tools such as Codex, Claude Code, Visual Studio Code and other MCP-compatible clients to work with Studio directly. Rather than treating an Objo solution as an arbitrary collection of files, an agent can use Studio’s own understanding of projects, source items, editor buffers, diagnostics and documentation.
An authorised agent can inspect the current solution, read saved or unsaved editor contents, see the current selection and member context, search the documentation bundled with Studio, compile a project and examine its structured diagnostics. With additional permissions it can make version-checked edits, create, move or rename source items, open documents in the editor and save the solution.
Security and control have been central to the design. External access is disabled by default, and every new client begins with read-only access. Additional abilities are granted separately from within Studio.
Setup is handled from Settings > External Agents. Studio generates private configuration for Codex, Claude Code, Visual Studio Code or another MCP client, including the path to the companion bundled with that exact Studio installation.
This opens up some extremely powerful workflows. You can ask an external agent to investigate a compiler error using the live diagnostics, explain unfamiliar code using the bundled Objo documentation, make a carefully scoped edit and then compile the result through Studio all while retaining control over what it may read, change or save.
I’ll be publishing a separate article showing how to configure an external agent and what it can do in practice.
More improvements throughout Studio
There is plenty more in 26.8.5 beyond Workers and MCP. Some other highlights include:
- The Hierarchy view can be pinned beside both the visual designer and code editor.
- Windows Command Line applications can be published as portable ZIP archives.
- Deprecated APIs are identified in code completion and hover information.
- Debugger controls have moved to the top toolbar in the IDE.
MessageDialogcan show only the buttons you configure.
The release also includes fixes across the compiler, editor, visual designer, debugger and desktop runtime, including improved high-DPI Canvas drawing, correct HTMLViewer colours on Linux and visible error reporting when a desktop application encounters an unhandled runtime exception.
Summary
Objo Studio 26.8.5 is a major release. Worker projects bring robust multicore processing to Objo applications, while MCP gives external coding agents a secure and deeply integrated way to work with Studio.
I’m incredibly excited to see what people build with both of these features.
Download Objo Studio 26.8.5 or read the complete changelog.