What changed
NOVEMBER 10 V0.1.8: NVIDIA's OpenShell release notes require explicit placement for static provider credentials destined for custom headers (including x-api-key), URL parameters or path slots; unannotated credentials use Authorization only unless body/WebSocket rewrites are enabled. HTTP upgrade requests now return 403 in audit and enforce modes unless a WebSocket endpoint and handshake/message rules are configured. OCSF sandbox attribution changes from top-level container fields to device.container, resources or unmapped depending on event type, requiring SIEM remapping. Filesystem policies whose paths traverse a symlink in a writable workspace now fail sandbox launch, even best-effort; IPv4-mapped IPv6 destinations are evaluated as IPv4. Core 0.1.8 also fixes retained gateway memory after sandbox deletion, per-sandbox stream-buffer allocations, Kubernetes stop-state races and PostgreSQL outage recovery, and removes temporary AWS SigV4 session tokens from TRACE diagnostics. Upgrade gateway before supervisor and refresh already-imported gateway profiles; editing a source YAML alone does not update the gateway catalogue. EARLIER RELEASE HISTORY: On September 28, NVIDIA launched Open Agent Safety Platform, combining the broadly available OpenShell secure runtime with a Sentry reference design for BlueField-4 DPUs. OpenShell runs agents inside isolated sandboxes, applies filesystem, process, network and provider-access policy outside the agent process, and can bind credentials only to approved endpoints. Sentry moves monitoring into an isolated DPU trust domain and is designed to quarantine agents that cross policy boundaries. NVIDIA says more than 100 organizations are working with the platform technologies, while OpenShell is available as open-source software and can be extended beyond NVIDIA CPUs. On October 21, NVIDIA announced the OpenShell Reference Architecture, connecting Vera Rubin inference infrastructure, Vera CPUs for agent execution and BlueField-4 DPUs running Sentry into a fuller enterprise reference design, with edge deployment options on RTX Spark, DGX Spark and DGX Station. NVIDIA lists Canonical, Red Hat and Windows execution environments among the intended integrations. This expands the September launch's architectural scope but does not establish that the full hardware-backed enforcement stack is independently deployed and validated. On October 27 OpenShell v0.1.6 changed gateway startup to require OIDC, mTLS or JWT-based authentication unless the operator expressly opts into unauthenticated access for trusted local development. It also reversed the initial control-connection direction for new Docker, Podman, Kubernetes and VM sandboxes, requiring matched supervisor and runtime upgrades, and introduced authorization/credential-denial OCSF audit events and shared supervisor options. On November 3 v0.1.7 made native OCSF 1.8.0 records mandatory, deprecated old schema-version settings, aligned policy DNS address selection with endpoint destination checks, updated vulnerable Rust dependencies, and added configurable agent OpenTelemetry trace relay and OTLP/HTTP support. These are shipping OpenShell runtime changes, separate from NVIDIA's unvalidated BlueField Sentry reference-design claims.
Why it matters
Operators depending on OpenShell's previous permissive credential resolution, gateway-generated WebSocket traffic or OCSF field paths can see hard failures or silently broken SIEM joins after upgrading. The stricter symlink check is a deliberate sandbox fail-closed change; correcting policies to target the actual path is safer than weakening enforcement. Review and test provider placements, proxy routes, SIEM mappings and gateway/supervisor order before production rollout. The project's hardware-backed Sentry deployment remains a reference architecture, not established independent proof of complete isolation. Coding and autonomous agents increasingly need real credentials, network access and the ability to run arbitrary developer tools. Application-level prompts and model guardrails are weak boundaries when the agent itself can manipulate its environment. OpenShell makes the execution environment the enforcement point and keeps credentials away from the agent process; Sentry adds a second observer outside the host CPU. For builders, that creates a concrete alternative to trusting each agent harness to implement its own sandbox correctly. Operators now have a concrete gateway-authentication migration that can prevent startup on upgrade if credentials are not configured, and a breaking audit-schema change that can disrupt downstream security dashboards unless OCSF 1.8 is supported. The DNS policy fix is especially relevant to agent egress containment; authentication and log fidelity should be tested on the actual deployed runtime.
OpenShell v0.1.8 upgrade requires explicit credential, WebSocket and policy migration
NVIDIA's November 10 upstream release requires explicit credential placement for non-Authorization headers, query/path injection and body/WebSocket rewrites. It forbids HTTP upgrades without a declared WebSocket endpoint and rules (403), moves sandbox identities to event-type-specific OCSF fields, and fails filesystem policy paths traversing symlinks within writable workspaces even in best-effort. Operators should upgrade the gateway before supervisor, refresh imported profiles in the gateway catalogue, update SIEM parsing and test IPv4-mapped IPv6 egress rules. Additional fixes address deletion-time gateway memory leaks, excessive per-sandbox buffers, PostgreSQL readiness after outages and TRACE diagnostic token exposure.
OpenShell puts policy outside the agent
OpenShell isolates each agent and enforces filesystem, process and network rules below the harness. Outbound requests pass through policy checks, and provider credentials can be injected only for approved destinations rather than exposed directly to the agent.
Policy changes are themselves checked
NVIDIA says OpenShell includes a policy prover that uses formal verification to identify whether a proposed rule expands access beyond an allowed boundary. Riskier changes can therefore be held for human review instead of being accepted because an agent requested them.
Sentry adds an independent hardware observer
The Sentry reference design runs on BlueField-4 DPUs, outside the agent's host execution domain. NVIDIA says it correlates activity, tool access and policy decisions and can quarantine an agent in milliseconds if it attempts to move beyond its software boundary.
The runtime is already usable without the full NVIDIA stack
OpenShell is open source and supports local Linux, Apple Silicon macOS and experimental Windows WSL 2 workflows, with Docker, Podman and MicroVM-backed sandboxes. Its documented agent paths include Claude Code, Codex, OpenCode and GitHub Copilot CLI.
The strongest claims still need independent testing
The millisecond quarantine claim, minimal-overhead claim and large ecosystem adoption figures come from NVIDIA. The architecture is inspectable, but independent adversarial testing and production overhead data will matter more than launch-partner counts.
October 21 extends the reference design from runtime to enterprise and edge stacks
NVIDIA's October 21 OpenShell Reference Architecture pairs Vera Rubin for model inference with Vera CPUs for agent harnesses and tool execution, and BlueField-4 DPUs running Sentry for out-of-band monitoring and policy enforcement. It also describes edge configurations using RTX Spark, DGX Spark and DGX Station, and intended support across Linux and Windows execution containers. This is an integration reference architecture, not evidence that every component is generally available as a packaged, audited product.
v0.1.6 enforces authenticated gateways by default
From October 27, OpenShell gateways will not start unless OIDC, mTLS user/operator authentication or gateway JWTs are configured. Explicit allow_unauthenticated_users=true is intended only for trusted local development. New sandboxes now connect out to supervisors rather than the reverse; upgrading supervisor and runtime binaries together prevents compatibility failures. The release also adds OCSF authorization-denial and credential findings, plus experimental shared supervisors.
v0.1.7 makes OCSF 1.8 the audit format and tightens routing
The November 3 OpenShell 0.1.7 release emits native OCSF 1.8.0 only, deprecating the previous schema-selection configuration. Existing log pipelines expecting OCSF 1.1 or 1.3 need migration tests. The runtime corrects DNS policy destination checking for direct connections, updates vulnerable dependencies and can relay agent OpenTelemetry spans with sandbox IDs via configured collectors. These code-level changes are not evidence of a complete independent sandbox escape audit or that the BlueField Sentry design is deployed.