This release expands how you can install, access, and use the SiMa.ai Neat SDK. It adds an offline installation path, browser-based SDK Code access, updated Neat components, and a more reliable SDK-to-DevKit synchronization flow.
If you develop with a Modalix DevKit or need to install the SDK in a constrained or disconnected environment, this release is recommended.
What is new
Offline SDK installation bundles
The SDK can now be packaged as a downloadable offline bundle. The bundle contains the SDK container image and installation resources so setup can proceed without pulling the image from a registry at install time.
This gives teams a practical installation option for controlled networks, air-gapped workflows, and environments where registry access is restricted or unreliable. The offline package is built from the promoted SDK image and preserves the same SDK setup experience after it is loaded locally.
Browser-based SDK Code access
The SDK now includes OpenVSCode Server, providing browser-based access to the SDK development environment. After SDK setup, SDK Code is available through the host port reported by the sima-cli setup flow, so you can work in the SDK without installing a local desktop editor.
Updated Neat components
The SDK now includes:
- Neat Core
v0.3.0 - Neat Insight
v0.0.6
These versions are selected by the SDK dependency manifest, giving SDK 2.1 users the latest compatible Core and Insight capabilities in this release line.
More reliable SDK-to-DevKit synchronization
When the SDK updates Neat packages on a connected DevKit, it now transfers the complete Core DEB bundle rather than a limited filename allowlist. This includes the required memory-library packages and supporting payloads needed by the Core installer.
This prevents a class of DevKit installation failures where the SDK copied the main Neat packages but omitted required bundled dependencies.
Improved install and extension setup
The standard SDK package install flow is more resilient when sima-cli is installed in its managed location but is not present on the invoking shell PATH. The bundled installer now discovers the executable before starting setup and supports an explicit SIMA_CLI=/path/to/sima-cli override.
This release also improves installation of the SiMa Neat VS Code extension during SDK setup, including support for the browser-based editor environment.
Why this matters
SDK development often spans the host machine, the SDK container, and a connected DevKit. Installation constraints, editor availability, dependency alignment, and package synchronization can all interrupt that workflow.
This release makes the experience more flexible and dependable: you can prepare for offline installation, access the SDK through a browser, and rely on a more complete package handoff to the DevKit.
User benefits
- Install the SDK from an offline bundle in controlled or disconnected environments.
- Use SDK Code in a browser without a locally installed desktop editor.
- Develop with Neat Core
v0.3.0and Neat Insightv0.0.6. - Avoid DevKit sync failures caused by missing bundled Core dependencies.
- Get a more robust
sima-cli-based SDK and extension installation experience.
Compatibility
This release remains on the SDK 2.1.2 platform baseline. The SDK release version is v2.1.2.3; compatible DevKit images continue to use platform version 2.1.2.
Use the SDK and DevKit platform versions together as documented for the 2.1.2 line.
Included changes
- Add offline SDK bundle creation and publishing in #104 and #109.
- Add browser-based SDK Code access in #110.
- Improve browser-editor extension installation in #113.
- Update Neat Core to
v0.3.0and Neat Insight tov0.0.6in #119. - Synchronize the complete Core DEB bundle to DevKit in #122.
- Keep branch-specific SDK artifact channels isolated in #124.
Full Changelog: v2.1.2.2...v2.1.2.3