Skip to content

v2.1.14

Choose a tag to compare

View all tags
@github-actions github-actions released this 08 Jul 02:38
v2.1.14
8f2c8d1
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Release Summary

sima-cli v2.1.14 improves the Neat SDK setup experience for browser-based development, remote access, and changing host networks.

The main customer-facing change is first-class setup support for the SDK's browser VS Code / OpenVSCode experience. When the SDK image exposes the Code UI, sima-cli sdk setup now maps the required ports, prints the secure browser URL, opens it when a local browser is available, and can install the SiMa Neat, Claude, and Codex VS Code extensions during setup.

This release also makes SDK setup more resilient on restricted hosts, refreshes HTTPS certificates when host IPs change, and fixes package-builder exclude behavior that could remove valid artifacts by mistake.

Highlights

Browser-Based VS Code Access for the SDK

sima-cli sdk setup now understands SDK images that expose browser VS Code / OpenVSCode.

When supported by the SDK image, the setup summary includes a tokenized codeUI URL such as:

codeUI | https://<host-ip>:10000/?tkn=<token>&folder=/workspace

The CLI also attempts to open this URL in the local browser when one is available. If setup is running on a headless machine or VM without a browser, setup continues normally and prints the URL for manual use.

The printed setup panel includes a security warning because the URL contains an access token and should not be shared.

Better Local and Remote URL Reporting

The SDK port summary now uses a table format and prints browser-facing URLs with the detected host IP instead of always showing localhost.

For users on VPNs or hosts with multiple network interfaces, sima-cli now separates the browser URL host from the DevKit/WebRTC iceHost. This avoids opening SDK browser URLs with a VPN/tunnel IP that is valid for routing but not reachable from the browser.

The result is clearer output for both local and remote access:

  • Use the printed host IP when connecting from another machine.
  • Replace the host with localhost or 127.0.0.1 for local-only access when preferred.
  • Keep iceHost visible for DevKit and WebRTC debugging.

Optional VS Code Extension Installation

During SDK setup, users can choose to install the expected browser VS Code extensions:

  • SiMa Neat VS Code extension
  • Claude Code extension
  • Codex extension

The -y / yes-to-all setup path installs these extensions without prompting. Extension installation targets the SDK user's OpenVSCode extension directory and restarts OpenVSCode afterward when needed.

This helps new SDK workspaces start with the expected Neat panel and AI coding agent integrations already available in the browser Code UI.

More Robust SDK Setup on Restricted Hosts

SDK setup now handles several common host-environment problems more gracefully:

  • If mkcert cannot be installed because the user does not have sudo privileges, setup falls back to self-signed HTTPS certificates instead of failing the full setup.
  • The SDK extensions directory is checked early for create/write permission, so users can choose a different location before setup proceeds.
  • Older SDK images that do not expose browser VS Code ports no longer print misleading codeUI rows.

These changes make setup less fragile on shared servers, corporate Linux hosts, and remote development machines.

HTTPS Certificate Refresh for Network Changes

When SDK setup is rerun after a host network change, sima-cli now checks the full expected HTTPS certificate SAN set instead of only the primary routed host IP.

If any expected DNS name or IP address is missing, the Neat HTTPS certificates are reissued. This helps avoid stale browser certificate errors after DevKit re-pairing, VPN changes, or alternate host IP changes.

Safer Package Exclude Semantics

sima-cli packages build --exclude now treats extension-style excludes such as .sh, .deb, .json, and .tar.gz as filename suffix filters rather than arbitrary substring filters.

This prevents valid artifacts from being removed accidentally when a branch-derived filename happens to contain text such as .shim. Broader excludes such as debug or internals, and dot-directory excludes such as .git and .cache, continue to work as before.

Maintainer and Release Workflow Updates

This release includes repository and package publishing improvements that do not change normal CLI usage:

  • Improved package-builder regression coverage for extension-style exclude filters.
  • Updated SDK setup and network doctor tests for browser Code UI behavior.
  • Updated sima-cli neat install command documentation for repository subfolder package targets.
  • Version bumped from 2.1.13 to 2.1.14.

Upgrade Notes

Upgrade with the normal sima-cli update flow. No SDK workspace migration is required.

For the browser Code UI features, use an SDK image that exposes the OpenVSCode ports. Older SDK images remain supported, but sima-cli will hide Code UI entries when those ports are not available.

Full Changelog

v2.1.13...v2.1.14

Assets 2
Loading