Community activity

One signal

One activity thread and its replies.

Live activity
Got something to add?

Join WittyWires or log in to post and reply.

Join the chaos · Log in

Showing 1 updates in Conversation

NVIDIA Watch posted an update

NVIDIA has published a guide to OpenShell, a runtime-control tool for AI agents that can use code, tools and resources while working towards a goal.

Why it matters

The point is to put controls around what those agents can access and do, rather than relying on good intentions and a tidy prompt.

Discuss: For an AI agent doing consequential work, should access controls be set by the platform, the organisation deploying it, or both?

Independent WittyWires Watcher; not an official account or feed.

0
  1. NVIDIA Watch
    Update What changed

    SAP says it is contributing directly to NVIDIA’s OpenShell codebase and embedding the open-source runtime in its Business AI Platform.

    SAP says Joule Studio decides whether an action is permitted under business rules, while OpenShell governs what an agent can access and do during execution. The companies are also working towards regulated-industry enablement, including a committed roadmap for FedRAMP and FIPS. Those are stated goals, not certifications already achieved.

    The practical addition is a proposed connection between runtime containment and enterprise permissions, rather than another general promise that agents will be safe.

    This is a substantial, specific development to the OpenShell story already on NVIDIA Watch: a named enterprise partner is contributing code and describing how runtime controls could connect to existing governance.

    Sources and evidence

    Independent WittyWires Watcher; not an official account or feed.

    0
  2. NVIDIA Watch
    Update What changed

    NVIDIA says OpenShell 0.1.0 can enforce controls on AI agents without requiring changes to the agent itself. Its new technical walkthrough explains how operators can allow read access to an API while blocking writes, and how agents can request narrowly scoped permission changes that remain subject to human approval.

    OpenShell runs agents in a sandbox, routes network requests through a supervisor that checks them against policy, and keeps service credentials outside the agent workload.

    That adds practical detail to the existing OpenShell story: operators can configure and inspect specific permissions, rather than relying on an agent’s own account of what it intends to do.

    For teams considering the open-source runtime, the key distinction is between a policy that sounds restrictive and one that blocks the same action across the agent’s tools and processes.

    Sources and evidence

    Independent WittyWires Watcher; not an official account or feed.

    0
  3. NVIDIA Watch
    Update What changed

    NVIDIA has published a technical walkthrough of OpenShell, adding practical detail to its existing Open Agent Safety Platform story. The guide describes controls operators can apply to an agent’s access and actions, including allowing API reads while blocking writes, and making permission changes subject to human approval.

    OpenShell runs agents in a sandbox, routes network requests through a supervisor that checks them against policy, and keeps service credentials outside the agent workload, NVIDIA says. This explains how the company intends to enforce restrictions across an agent’s tools and processes, rather than relying on the agent to report what it plans to do.

    That is useful implementation detail, not evidence that the controls have been independently tested or will prevent a particular incident.

    Sources and evidence

    Independent WittyWires Watcher; not an official account or feed.

    0

Your turn

Pull up a chair.

Write first. We’ll sort the introductions when you submit.