Skip to main content
AI
  • Get started with AI

    • Red Hat AI

      Accelerate the development and deployment of enterprise AI solutions.

    • AI learning hub

      Explore learning materials and tools, organized by task.

    • AI interactive demos

      Click through scenarios with Red Hat AI, including training LLMs and more.

    • AI/ML learning paths

      Expand your Red Hat OpenShift AI knowledge using these learning resources.

    • AI quickstarts

      Focused AI use cases designed for fast deployment on Red Hat AI platforms.

    • No-cost AI training

      Foundational Red Hat AI training.

  • Featured resources

    • Red Hat OpenShift AI
    • Open source AI for developers
    • AI product application development
    • Open source-powered AI/ML for hybrid cloud
    • AI and Node.js cheat sheet

Red Hat AI Factory with NVIDIA

Red Hat AI Factory with NVIDIA is a co-engineered, enterprise-grade AI solution for building, deploying, and managing AI at scale across hybrid cloud environments.

Learn
  • Self-guided

    • Documentation

      Find answers, get step-by-step guidance, and learn how to use Red Hat products.

    • Learning paths

      Explore curated walkthroughs for common development tasks.

    • Guided learning

      Receive custom learning paths powered by our AI assistant.

    • See all learning
  • Hands-on

    • Developer Sandbox

      Spin up Red Hat's products and technologies without setup or configuration.

    • Interactive labs

      Learn by doing in these hands-on, browser-based experiences.

    • Interactive demos

      Click through product features in these guided tours.

  • Browse by topic

    • AI/ML
    • Automation
    • Java
    • Kubernetes
    • Linux
    • See all topics
  • Training & certifications

    • Courses and exams
    • Certifications
    • Skills assessments
    • Red Hat Academy
    • Learning subscription
    • Explore training
Build
  • Get started

    • Red Hat build of Podman Desktop

      A downloadable, local development hub to experiment with our products and builds.

    • Developer Sandbox

      Spin up Red Hat's products and technologies without setup or configuration.

  • Download products

    • Red Hat Enterprise Linux
    • Red Hat AI
    • Red Hat OpenShift
    • Red Hat Ansible Automation Platform
    • See all products
  • Featured

    • Red Hat build of OpenJDK
    • Red Hat JBoss Enterprise Application Platform
    • Red Hat OpenShift Dev Spaces
    • Red Hat Developer Toolset
  • References

    • E-books
    • Documentation
    • Cheat sheets
    • Architecture center
Community
  • Get involved

    • Events
    • Live AI events
    • Red Hat Summit
    • Red Hat Accelerators
    • Community discussions
  • Follow along

    • Articles & blogs
    • Developer newsletter
    • Videos
    • Github
  • Get help

    • Customer service
    • Customer support
    • Regional contacts
    • Find a partner

Join the Red Hat Developer program

Download Red Hat products and project builds, access support documentation, learning content, and more.

ConsoleDocsSupport Search
New For you

Recommended

We'll recommend resources you may like as you browse. Try these suggestions for now.

  • Product downloads
  • Cheat sheets
  • Red Hat Developer learning portal
  • Developer blog
  • E-books
  • Developer Sandbox
Log in

Get more with a Red Hat Developer account

  • Product downloads
  • Console access
  • Event registration
  • Training & trials
Explore more account benefitsLog in or register

A subscription may be required for some services.

Contact us

Securing third-party AI agents on Red Hat AI with OpenShell

An Omnigent case study

November 17, 2026
Sean Condon
Related topics:
Security
Related products:
Red Hat AI

    The AgentOps strategy in Red Hat AI 3.6 is bring your own agent (BYOA), providing a sandbox environment for running agent harnesses through the addition of the OpenShell open source project.

    In this article, I demonstrate the Omnigent project, a "meta-harness" for AI agents that gives a common UI layer over Claude Code, Codex, Pi, Goose, and others. You can swap or combine harnesses without rewrites, keep them in check with policies and sandboxing, and collaborate in real time on the same live session, from any device.

    Omnigent can work in server mode so session data can be saved, shared between team members and forked, while preserving access to the underlying agent. Figure 1 provides an overview of the architecture.

    The system routes incoming requests from various command line and custom agents through a secure runner sandbox into a central server. The server manages policies and catalogs before distributing data to multiple user interfaces and back-end services.
    Figure 1: The system routes incoming requests from various command line and custom agents through a secure runner sandbox into a central server. The server manages policies and catalogs before distributing data to multiple user interfaces and back-end services.

    Implementation

    While Omnigent can work with many sandbox providers, this article focuses on running it through OpenShell on Red Hat OpenShift to take advantage of BYOA. The documented path for Omnigent on OpenShell gives a basic integration, but for Red Hat OpenShift extra steps are needed. You can follow along with this exercise by implementing everything in my example GitHub repository, referenced throughout this article.

    1. Create a custom sandbox image

    First, create a custom sandbox image using the components in the images directory in my GitHub repository, to ensure we're not exposing anything beyond what's needed. The requirements take compatibility and security into account.

    For compatibility:

    • Meets the OpenShell requirements for sandbox users
    • Contains the Omnigent runtime client
    • Contains the only the agent harnesses required

    For security:

    • Contains the base OpenShell Policy locked down as much as possible
    • Contains specific harness configuration when required
    • Based on a Universal Base Image (UBI)

    2. Configure OpenShell

    Next, configure these OpenShell profiles and providers to load credentials (through OpenShell terminal or API). While Omnigent works with several different harnesses, like Pi and Goose, this exercise focuses on 4, to demonstrate how OpenShell standardizes credential injection and governance across diverse tools.

    You can think of a profile as a snippet of an OpenShell policy, with a placeholder for a credential. The provider then adds that credential.

    Profiles and providers

    • Antigravity, scondon-antigravity
    • OpenAI, scondon-openai
    • Claude Code, scondon-claude-code
    • LiteMaaS, scondon-litemaas
    • GitHub, scondon-github

    Use the script scripts/load-openshell-profiles.sh to automate the loading of these from your local environment variables.

    3. Configure Omnigent

    Using Git, clone my Omnigent fork and modify the Kustomization overlay (openshift-openshell) in the branch scShiftShell.

    $ git clone -b scShiftShell git@github.com:aicatalyst-team/omnigent.git 
    $ cd deploy/kubernetes/overlays/openshift-openshell

    First inspect server-config.yaml, which allows us to specify how we want sandboxes to be created, setting the image to use, an optional OpenShell workspace, node selector labels, and optionally changing the runtime class. This config must include the names of OpenShell providers created in the previous step.

    apiVersion: v1
    kind: ConfigMap
    metadata:
      name: omnigent-server-config
      labels:
        app: omnigent
    data:
      config.yaml: |
        sandbox:
          provider: openshell
          server_url: http://omnigent.omnigent.svc.cluster.local
          openshell:
            providers:
            - scondon-openai
            - scondon-github
            - scondon-litemaas
            - scondon-antigravity
            # node_selector:
            #  kata-install: "true"
            workspace: omnigent
            image: quay.io/aicatalyst/omnigent-host-openshell-ubi:latest
            env:
              - OMNIGENT_RUNNER_ENV_PASSTHROUGH

    Copy secrets.env.example to a secrets.env and adjust it to connect to a local OIDC server (for example, Keycloak). Alternatively, omit the OIDC values to allow the built in account manager to operate.

    To enable access to Omnigent at an external URL, change the host name in route.yaml.

    Adjust IP addresses in the network policy as necessary. Deploy the Kustomization with:

    oc apply -k deploy/kubernetes/overlays/openshift-openshell

    Omnigent features

    Accessing the UI at the URL configured in the route.yaml, and logging in as a pre-configured user (for example, Alice), allows you to start a session and share it with other logins (for example, Bob).

    Alice's new session (Figure 2) creates a new OpenShell sandbox instance with Codex as the main process. The important features of the integration are highlighted:

    1. Before starting the session, this drop down allows choosing the harness and typing in a prompt to start the session. Once started, this presents a list of models to use with that harness.
    2. The share button allows sharing this session with other users. Here Alice has given Bob write access to this session, and we can see his inputs in the chat. Being able to share conversations like this is one of the main advantages of Omnigent in Server mode, and is the feature that most benefits from a sandbox.
    3. A bash shell session into the sandbox allows interaction with it directly in this tab. The prompt reflects the OpenShell sandbox name.
    4. The custom sandbox image for this demo is based on UBI.
    5. The gh tool is already logged in because of the scondon-github OpenShell provider, which includes GH_TOKEN.
    6. The GH_TOKEN and the API keys passed in through the OpenShell providers are masked, and will be replaced by the OpenShell network proxy when a call is made.
    7. File system access is locked down by default with exceptions being allowed in the OpenShell Policy as necessary.
    8. The processes run as a user sandbox as required by OpenShell.
    9. Network access to external endpoints, such as omnigent.ai, is blocked by default, unless an exception is given in an OpenShell policy or provider.
    The user interface features a chat session with an AI model alongside a live terminal panel on the right displaying sandbox status and system outputs. The navigation sidebar provides access to sessions, automations, and projects.
    Figure 2: The user interface features a chat session with an AI model alongside a live terminal panel on the right displaying sandbox status and system outputs. The navigation sidebar provides access to sessions, automations, and projects.

    OpenShell view

    From the OpenShell side, the configuration can be viewed in the OpenShell terminal, as shown in Figure 3.

    The OpenShell terminal interface displays the dashboard for the active workspace, detailing the status of the gateways, the configured providers with their policies, and the active sandboxes.
    Figure 3: The OpenShell terminal interface displays the dashboard for the active workspace, detailing the status of the gateways, the configured providers with their policies, and the active sandboxes.

    The OpenShell terminal shows the dashboard for this omnigent workspace:

    1. The OpenShell providers pre-configured and the profile they're based on. Each brings in a credential and some policy rules to extend the policy that's baked into the sandbox image.
    2. Policy violations detected. In this case it's because we tried to access omnigent.ai in the session and it was refused. The violation can be reviewed and approved through this terminal on a live sandbox without any interruption to the Omnigent session.

    Analysis

    The integration of Omnigent with OpenShell is a comprehensive reference for the BYOA strategy of Red Hat AI. By integrating the OpenShell SDK directly, Omnigent can access the full breadth of OpenShell's features, without modifying agent source code.

    The upcoming integration of OpenShell into Red Hat AI in 3.6 will add sandbox fast-provisioning, UX integration, the ability to choose the runtime class (like Kata containers), native multitenancy.

    For Omnigent itself, there is a lot more to explore, like configuring MCP servers, how sharing of agentic sessions enables building Team Agents, and the many other ways in which you can connect to your sessions using mobile, terminal, and APIs.

    Configuration files and the sandbox image

    The interface between Omnigent and OpenShell by design does not allow passing of files, only environment variables. This requires that the configuration files are present in the sandbox image when it is built, but can be tweaked with environment variables when required, as shown in the example for configuring LiteMaaS. This restriction creates a good separation of concerns, avoiding the inadvertent loading of files at runtime, even if it requires some more maintenance of sandbox images.

    Defense in depth

    Inside an Omnigent host, agents are run with BubbleWrap, giving them further defense in depth on top of what OpenShell provides. This isolates the agent from the Omnigent host processes and the WebSocket it uses to call back to the Omnigent server.

    Future improvements

    While Omnigent's integration is secure, I've suggested some feature requests to their roadmap, to improve the security posture:

    • Allow a different sandbox image per harness type. With this, the image could be built to only support that harness, reducing the configuration to only what's needed.
    • Allow external CLI connections directly from the omni attach command. Currently, CLI connection is only possible from inside the OpenShell sandbox CLI.
    • When Stop Session is selected in the Omnigent UI, the corresponding OpenShell sandbox should be suspended.
    • Omnigent sandbox configuration should allow the ability to choose user_namespaces in OpenShell.

    Conclusion

    While Omnigent remains a community project rather than part of the Red Hat AI roadmap, it exemplifies the power of BYOA. Explore our proof-of-concept repo on Github to test these sandbox policies in your own development clusters, and the OpenShell docs on security best practices.

    Related Posts

    • Run decision models on vLLM and Red Hat AI using DiffusionGemma

    • Build a multi-agent supervisor pattern on Red Hat AI

    • Add NeMo Guardrails to a LangGraph agent on OpenShift AI

    • Deploy NeMo Guardrails on Red Hat OpenShift AI

    • Every layer counts: Defense in depth for AI agents with Red Hat AI

    Recent Posts

    • GitOps Promoter: Declare, deploy, deliver

    • Securing third-party AI agents on Red Hat AI with OpenShell

    • Red Hat Enterprise Linux GitHub hosted runner images now generally available

    • Streamlining Red Hat OpenShift support with the new support log gather operator

    • A day in the life of an NVIDIA H100 on Red Hat OpenShift 5

    What’s up next?

    Learning Path TensorFlow-Onnx-LP-featured-image

    Build and evaluate a fraud detection model with TensorFlow and ONNX

    Learn how to deploy a trained model with Red Hat OpenShift AI and use its...
    Red Hat Developers logo

    Platforms

    • Red Hat AI
    • Red Hat Enterprise Linux
    • Red Hat OpenShift
    • Red Hat Ansible Automation Platform
    • See all products

    Build

    • Developer Sandbox
    • Developer tools
    • Interactive tutorials
    • API catalog

    Quicklinks

    • Learning resources
    • E-books
    • Cheat sheets
    • Blog
    • Events
    • Newsletter

    Communicate

    • About us
    • Contact sales
    • Find a partner
    • Report a website issue
    • Site status dashboard
    • Report a security problem

    Red Hat Developer

    Build here. Go anywhere.

    We serve the builders. The problem solvers who create careers with code.

    Join us if you’re a developer, software engineer, web designer, front-end designer, UX designer, computer scientist, architect, tester, product manager, project manager or team lead.

    Sign me up

    Red Hat legal and privacy links

    • About Red Hat
    • Jobs
    • Events
    • Locations
    • Contact Red Hat
    • Red Hat Blog
    • Inclusion at Red Hat
    • Cool Stuff Store
    • Red Hat Summit
    © 2026 Red Hat

    Red Hat legal and privacy links

    • Privacy statement
    • Terms of use
    • All policies and guidelines
    • Digital accessibility
    Ask AI