Released Seiro MCP v0.3.0, Which Can Track Detailed Build Diagnostics
v0.3.1 has already been released, so this is quite late, but I had not written an article yet, so I am writing one now. I chose the version number v0.3.0 because it added a new feature that is genuinely useful.
First, about v0.3.0.
In this release, I added a read-only MCP tool called inspect_build_diagnostics for investigating causes of visionOS build failures that cannot be understood from normal error messages. By using it, detailed information can be retrieved using the job_id that the AI side already has as the key, including file, line, and column information when available.
Until now, when a build failed and the cause was unclear, there was work involved in trying hard to obtain information through shell operations and similar methods. This release has moved that responsibility into MCP. Thanks to that, the AI side should now be able to focus on investigating the cause itself based on detailed information.
Without this feature, the AI would work hard to investigate various things using tools such as xcrun swiftc. When Seiro MCP is introduced, the Skill guidance makes it possible to benefit preferentially from investigation using Seiro MCP.
The main additions in the v0.3.0 release are below.
- New read-only MCP tool:
inspect_build_diagnostics - Added structured build error:
destination_ambiguous
I will also explain destination_ambiguous. This is a node added when build_visionos_app fails to run. For example, depending on the environment, multiple simulators with the same name may be found. In that case, an interaction occurs where the AI chooses again, but Codex can sometimes get confused at that point. To prepare for those cases, the tool returns matched_devices, available_destinations, and suggested_destination as information, allowing the AI side to proceed smoothly with the build by using suggested_destination.
There are also the following smaller improvements.
- When using the Skill, guidance now helps reference the following tools:
- In the phase that checks for project existence,
.xcodeproj/.xcworkspaceare now treated as directory packages build_visionos_appnow accepts lowercaseconfigurationvalues, while also acceptingDebug/Releaseas backward-compatible input aliases- Minor style fixes and related updates were made to the public documentation
For compatibility, the provided tools are unchanged from previous versions, so I suspect there should not be any AI confusion. That said, Seiro MCP is evolving in a direction where installing its Skills is assumed.
Addendum: About v0.3.1
v0.3.1 is a very small change, adding dedicated metadata and an icon to the Skill. This resolved the issue where it appeared with a generic icon in the Codex App skill list. The Skill installer now also installs the metadata and icon at the same time.