Obeo AI for Capella — Release Notes

Optional Capella startup prompt. Clients that expose MCP prompts can select capella_init to insert the packaged initial instructions into the conversation. The prompt itself does not connect to Capella or load the extended guidance; follow its instructions before starting a modeling task.

Capella top-down transitions through MCP. Discover the transitions available for a semantic selection, then execute the chosen action. Supported families include functions, interfaces, data, state machines, actors, capabilities, and transitions between logical components, physical components, and configuration items, where applicable in Capella. Transitions do not automatically save the session.

Explicit selections for palette tools. Discover candidates and preselected elements, then supply the selection without opening the tool’s dialog. Supported tools include function allocation from a LAB diagram.

Incremental EMF model exploration. Navigate from session roots to properties and references, with filters for feature kind, feature name, element name, and metaclass. Results expose parent, type, and child-presence information without recursively expanding the entire model. Returned semantic identifiers can be reused across calls.

Capella guidance and Arcadia context delivered through MCP. Initialization instructions, dedicated resources, and the capella_get_agent_guidance fallback tool provide the agent’s operating guidance. The normal setup no longer requires copying a complete AGENTS.md into each workspace. Actual guidance retrieval depends on the MCP client.

Simpler AQL input. Expressions without an AQL prefix receive one automatically.

Capella edge-tool preconditions now use the same source, target, view, and diagram context as native Sirius execution, correcting selection-candidate discovery for edge tools.

Structured MCP results are normalized as JSON objects, with matching text content. JSON-RPC error handling and MCP failure reporting are improved.

MCP and JSON-RPC call logging, consistent CLI/MCP logging configuration, and optional rotating log files. In the final configuration, file logging is disabled by default; warnings and errors remain on stderr.

Clearer creation computeId lifecycle: single use, expiration after two minutes, and actionable errors prompting clients to repeat discovery.

Fixes for palette tool availability, failed transition reporting, and logical actor counts.

Public documentation moves to Antora. The web documentation replaces the former CI-generated guide PDFs and brings the quick start, user manual, installation guide, LLM client configuration, MCP reference, feature catalogue, and release notes together. PDF and Eclipse exports remain available through the local Antora scripts.

Product guides are available online. The agent archive no longer includes the public AsciiDoc guide sources under docs/product/. Use the online-help links in the packaged README and installers. Agent guidance templates, client resources, examples, and experimental JShell documentation remain packaged.

Guides separate modeling tasks from technical reference. Working with Capella covers conversation startup, guidance loading, model and diagram changes, realization links, and review and save workflows. MCP Reference covers tool contracts and diagnostics, while Features brings capabilities and the compact tool catalogue together.

Installation requirements and access are documented. The supported environment covers Windows, Linux and macOS, host permissions, agentic client requirements, and external connections. The installation guide explains stdio/HTTP access rights and how they relate to server profiles. Get Obeo AI for Capella explains how to obtain download links from your Obeo contact and request and install a personalized license.

Client setup includes a working VS Code Windows example. The stdio configuration launches the MCP server through cmd.exe with an explicit working directory and includes startup diagnostics. Generic examples use <installation-folder-absolute-path>, Windows executable names, and documented Linux/macOS equivalents. The VS Code trial validates stdio setup; it does not establish HTTP compatibility or a fixed tool count.

Agent guidance now describes Functional Chain construction through Functional Chain Description palette tools and recommends discovering representation types from the target element’s context.

Capella 7.1.0 becomes the documented target version, while installation paths for 7.0.1 and 6.1.0 remain available. MCP and CLI tools require Java 21 with every supported Capella version. Launchers can reuse Java 21 bundled with a standard Capella 7.1.0 distribution.

ELK and its dependencies install from the bundled repository for Capella 7.0.1 and 7.1.0; the 6.1.0 installation path continues to skip ELK. Distribution archives now extract tools/ and updateSite/ directly at the extraction root.

Expanded quick-start and user guides cover modeling from requirements, using Arcadia transitions, and selecting the optional capella_init startup prompt in supporting clients, with a Claude Code example. User Manual navigation follows the modeling guide’s reading order; unfinished requirements, scaling, administration and migration pages are hidden from navigation.

More MCP edits remain pending until you save. Updating Capella element descriptions or realization links, renaming elements through diagram views, creating representations, and updating diagram descriptions no longer automatically save the Sirius session. Adding semantic resources and selecting viewpoints during these operations also leave the session unsaved. Review the changes and explicitly save the session when ready.

Updated the End User Licence Agreement documentation and packaged HTML license text.

Standardized source, script, build/configuration, and bundle/feature copyright notices on the complete 2026 Obeo notice. Agent contribution guidance now prescribes the same notice.

Multiple operations in a single MCP call. Batch tools cover palette creation, representation management, diagram operations, EMF inspection and edits, and selected Capella edits. The main tools are sirius_apply_palette_tools, sirius_manage_representations, sirius_manage_diagrams, emf_describe_model, emf_apply_edits, and capella_apply_model_edits.

Sirius collaboration diagnostics. Session and representation results expose collaborative state and lock information, with clearer edit-denial reporting and handling of frozen representations. Diagram refresh is added to MCP operations.

Grouped palette descriptions make the available tools easier to discover within a diagram description.

Obeo license management, Obeo AI for Capella product branding, and the associated EULA are integrated into the distribution.

Legacy preview features are removed during installation.

A feature catalogue and tool deprecation metadata identify recommended replacements. Client and developer documentation are separated.

HTTPS bearer authentication receives tests and documentation. This strengthens a transport already present in 0.7.0.

Several single-operation tools are replaced with batch tools. LAB wrappers that duplicated Sirius operations are removed in favor of the generic tools.

Module, artifact, and Java package identifiers move to fr.obeo.ai.*. Existing Java integrations must update their references.

Batches stop at the first error. Earlier successful changes may remain applied; a batch call does not provide automatic rollback of the entire operation.

EMF MCP tools backed by Sirius sessions. Inspect types and properties; create, rename, update, move, and delete elements. This MCP surface complements the existing EMF Java API.

Discovery and execution of Capella semantic creation actions. Create child elements without creating a view in a diagram.

Richer Sirius creation-tool descriptors expose tool identifiers and parameters before execution.

Fixes for diagram node creation and shared diagram handles. Diagram creation selects the shared analysis in collaborative contexts.

Better preservation of semantic identifiers, use of session identifiers when available, and more resilient runtime metadata cleanup.

Incompatible automation protocol versions are detected and rejected.

Fixes for null selectors and Capella inspection errors. Installation scripts support updates, distribution packaging is simplified, and JShell is explicitly documented as experimental.