Changelog

Template/volume validation: validation errors now point at the exact source line (the editor annotates the offending line instead of stacking errors at the top), messages are clearer and consistently include the offending value, and additional checks are enforced — cap_add/cap_drop must be CAP_* capabilities, command must be a list, and privileged must be a boolean.

Improvements to UI

Stack name clashes on create: creating a new stack no longer silently reuses an existing stack name, which previously mixed spaces from different stack instances under one name. The CLI (knot stack create) and the web create-stack flow now refuse to create a stack whose name is already in use. Editing a normal space can still be assigned to an existing stack.

Web VNC for shared spaces: opening web VNC on a space shared with you no longer fails. VNC access now resolves against the authenticated viewer and grants access to the space owner and any user the space is shared with, matching the SSH and terminal proxies.

• Scripting library: knot.space.grep, find, sed_replace, sed_replace_pattern, sed_extract, edit_file — see knot.space reference.
• CLI: knot space grep, find, sed (with --regex / --extract / --json), edit (with --search / --replace) — see CLI reference.
• MCP tools: grep, find, sed_replace, sed_replace_pattern, sed_extract, edit_file — discoverable by default; the replace/edit ops require approval.

• scriptling.grep
• scriptling.find
• tempfile
• shutil
• shlex
• zipfile
• tarfile
• scriptling.csv
• scriptling.xml

Events system

• Route lifecycle and custom events to webhooks, scripts, or JSON-RPC methods, scoped per-user or global.
• System events fire automatically on space lifecycle transitions: space.created, space.started, space.stopped, space.deleted, space.healthy, space.unhealthy. System event payloads now include space_name and space_id (plus space_urls for created/started).
• Raise custom events from inside a space via the knot event CLI, the agent’s POST /event, or the knot.event.emit() scriptling function.
• Sinks match on glob patterns (space.*, custom.myapp.*) and deliver zone-local, in-order per sink, with at-least-once semantics. Webhook sinks render a Go template body and sign with HMAC-SHA256; script sinks run an existing scriptling server-side; JSON-RPC sinks deliver events to running script methods via events/event_sinks method annotations.
• Simplified default webhook template: just event_id, event_type, event_ts, data.
• Two new permissions: Manage Own Event Sinks and Manage Global Event Sinks.
• New endpoints: GET/POST/PUT/DELETE /api/event-sinks, POST /api/spaces/{id}/emit-event.

Space pools

• Fixed-size, self-healing pools keep a target number of identical spaces running from a template; the cluster leader reconciles membership every 15 seconds, drains method traffic before stopping members, and applies a grace period before deleting excess spaces.
• Pool members are reachable via the pool name (username--poolname--port.domain), with the proxy falling back to pool lookup and round-robining across healthy, non-drained members. TCP WebSocket proxy routing (/proxy/spaces/{name}/port/{port}) accepts pool names too.
• Manage via knot.pool scriptling functions (list, utilization, desired_count, start/stop), the /api/pools endpoints, or MCP tools create_pool, delete_pool, start_pool, stop_pool, set_pool_size.

Space methods

• Running spaces can register JSON-RPC methods backed by a long-running stdio method server, and optionally expose them as discoverable MCP tools (mcp_tool = true; dotted names are rewritten to underscores).
• Methods can be private or shared, filtered by group, discovered with GET /api/methods, and called via POST /api/methods/call.
• The server supports concurrent (default) or serial request handling, JSON-RPC notifications, and batch calls; scriptlings can serve as the server via scriptling --json-rpc.
• Register from inside a space with knot methods register <file>.toml (or .py), or from startup scripts via the agent-only knot.methods library and knot.methods.schema JSON Schema builder.
• Register methods automatically at agent startup with knot agent start --methods-file <file>.toml (or .py); also configurable via the agent.methods_file config key or KNOT_METHODS_FILE environment variable.

knot run-script server modes

• The agent embeds the Scriptling runtime, so knot run-script now mirrors the Scriptling CLI’s run modes — no separate scriptling binary needed in a space. Run a script as a stdio JSON-RPC method server (--json-rpc), an HTTP server (--listen :PORT), or an MCP server (--mcp-tools DIR), with the sandbox flags (--allowed-path, --disable-lib, --bearer-token, --web-root, --kv-storage, --tls-*). Container runtime libraries are excluded.
• Plain knot run-script <file> now exposes the full Scriptling library set (minus container) plus Knot’s own libraries.
• knot --version reports the bundled Scriptling runtime version.

User access overview Pro

• A new Access button on the users list opens a popup showing everything a user can reach, derived from their roles and groups: effective permissions (grouped by category, with the ones they lack greyed out), effective quota, owned and shared spaces, and the templates, variables, volumes, scripts, skills, and stack definitions they can access.
• Backed by GET /api/users/{user_id}/access.

• Removed template authoring tools (create_template, update_template, delete_template, get_template) — list_templates now carries custom field definitions
• Removed get_stack_definition (covered by list_stack_definitions)
• Removed space access-control tools (share_space, stop_sharing_space, transfer_space)

• Templates can allow local-container spaces to be manually reassigned to another live node while stopped
• Node selection now prefers the least-loaded eligible node when placing or migrating local-container spaces

• Zone leaders can detect failed gossip nodes and automatically restart eligible spaces on another live node
• Automatic migration requires both node migration and Auto-restart on failure to be enabled on the template
• Leader election reconciliation ensures failed-node migrations continue if the previous zone leader fails

• User profiles now support multiple SSH public keys, with one key per line
• All profile keys are copied through to SSH-enabled spaces and running spaces receive profile key updates

• Users can store an SSH private key in their profile for SSH-enabled spaces
• SSH private keys are only visible and editable by the owning user
• The key is written to ~/.ssh/id_ed25519, ~/.ssh/id_rsa, or ~/.ssh/id_ecdsa depending on key format
• Running spaces receive updates when the key changes and old keys of a different type are cleaned up

• Local-container and Nomad templates can define paths alongside volumes
• Paths are created before spaces start and removed when spaces are deleted
• ~ resolves to the server user’s home directory, absolute paths start with /, and relative paths resolve from the agent working directory

• Added Agent health check mode for monitoring whether the space agent is still transmitting state
• Agent health checks can restart local-container and Nomad spaces when Auto-restart on failure is enabled

• Templates can define named ports (TCP, HTTP, HTTPS) that spaces expose
• Defined ports are injected into spaces as KNOT_HTTP_PORT, KNOT_HTTPS_PORT, and KNOT_TCP_PORT environment variables
• Alt names can route to specific ports defined in the template

• Added DNS resolution library (scriptling.resolve) for IP lookup and SRV record resolution
• Added file provisioning library (scriptling.provision.file) for file management in scripts

• New knot scripts read and knot scripts write commands for reading and writing script files
• New knot run-script agent command for executing scripts in running spaces

• Clarified local-container migration wording in the template form
• In Pro, Auto-restart on failure is shown when node migration is enabled, making the automatic migration policy visible from the template form

• Docker, Podman, and Apple container jobs now reject undeclared named volume binds instead of allowing runtimes to silently create untracked volumes
• Host-path binds continue to work, and named volumes must be declared in the template volume definition so they can be tracked and cleaned up correctly