v0.2.32

v0.2.32: fix exec marker leak on no-newline output; prevent VM kill o…

v0.2.31

v0.2.31: fix slow REST commands on macOS (IPv4-first resolver)

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

v0.2.30

v0.2.30: fix WS connection timeout on dual-stack hosts

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

v0.2.29

v0.2.29: client hardening and performance

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

v0.2.28

v0.2.28: HTTPS support via Caddy reverse proxy

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

v0.2.27

fix: use macos-14 for x86_64 cross-compile (macos-13 deprecated)

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

v0.2.26

What's new

noid exec without a command now opens an interactive console instead of erroring. Environment variables can be injected into both exec and console sessions:

noid exec myvm -e FOO=bar           # interactive console with FOO set
noid exec myvm -e FOO=bar -- echo $FOO  # non-interactive exec (as before)
noid console myvm -e FOO=bar        # console with env vars
noid exec myvm                      # interactive console (no longer errors)

Changes

• noid exec without a command routes to the interactive console instead of erroring
• Added -e/--env flag to noid console for environment variable injection
• Centralized env var validation (validate_env_name, validate_env_vars, limits) in noid-types, shared across client, server, and core
• Server now returns 400 (not 500) for invalid env vars in both REST and WS exec endpoints
• Console env injection uses marker-based synchronization for reliable variable setup

v0.2.25

What's changed

CLI consistency fix: All commands now accept VM name as a positional argument.

Previously, exec, checkpoint, and restore required --name as a flag while other commands (destroy, info, console, checkpoints) used positional names. Now all commands are uniform:

# Before (broken/inconsistent)
noid exec --name my-vm -- uname -a
noid checkpoint --name my-vm --label foo
noid restore --name my-vm abc123

# After (consistent with all other commands)
noid exec my-vm -- uname -a
noid checkpoint my-vm --label foo
noid restore my-vm abc123

Also fixes a pre-existing bug where noid destroy --name in scripts was silently failing (destroy never had a --name flag), with cleanup errors swallowed by || true.

Breaking change

--name is no longer accepted by exec, checkpoint, or restore. Use the positional argument instead.

v0.2.24

Bug fix

• Fix noid use from home directory: Renamed the active VM marker file from .noid to .noid-vm so it no longer collides with the ~/.noid/ config directory. noid use <name> now works from any directory including $HOME.

Note: If you previously used noid use, your old .noid marker files will be ignored. Just run noid use <name> again to create the new .noid-vm marker.

v0.2.23

Bug fix

• Fix noid use crash from home directory: Running noid use <name> from $HOME failed with "Is a directory (os error 21)" because the .noid active-VM marker file collided with the ~/.noid/ config directory. Now detects the collision and shows a clear error message instead.