Open-sourcing a shell-level security layer for AI agents

Reddit r/AI_Agents 05/21/26, 09:05 AM Tools

security ai-agents open-source shell safety dev-tool agent-security

Summary

Open-sourcing a shell-level control layer that blocks dangerous commands, exposes fake secrets, and enforces runtime policies to make AI agents safer and more deterministic in developer environments.

After working with AI agents for a while, I kept running into the same issue: eventually the agent ignores boundaries, reads `.env` files, touches production resources, or uses secrets it was never supposed to access. Even with MCP read-only setups and carefully written prompts, the shell itself is still trusted too much. So I started building a shell-level control layer for AI agents: * block or sanitize dangerous commands * expose virtual/fake secrets instead of real ones * separate DEV / PROD access policies * restrict network/domain access * enforce runtime policies instead of relying only on prompts The goal is to make agents safer and more deterministic inside real developer environments. I’m now open-sourcing it and looking for people who use Claude Code, Codex, Cursor, etc. to try breaking it on real workflows. Feedback, criticism, and attack ideas are very welcome. link to PyPI in the comments

Original Article

Similar Articles

@ClementDelangue: From what we know (take with a grain of salt, we need much more transparency!), if @OpenAI had been running this on the…

X AI KOLs Timeline

NVIDIA introduces OpenShell, an open-source runtime for secure AI agent execution with kernel-level enforcement and formal verification to prevent unauthorized actions.

How Autonomous AI Agents Become Secure by Design With NVIDIA OpenShell

NVIDIA Blog

NVIDIA launches OpenShell, a secure-by-design runtime for autonomous AI agents that isolates agent operations in sandboxes and enforces security policies at the system level rather than relying on behavioral prompts. The toolkit, part of NVIDIA Agent Toolkit, enables enterprises to run coding agents and agentic workflows with unified policy management and compliance oversight.

Would an open-source CLI orchestration layer for AI agents make sense?

Reddit r/AI_Agents

The article explores the idea of an open-source layer to orchestrate CLI usage by AI agents, addressing challenges like permissions, sandboxing, and audit trails when agents interact with multiple CLIs.

Before giving a local AI agent shell access, what security boundary should you enforce?

Reddit r/AI_Agents

A discussion on security boundaries for local AI agents with shell access, covering isolation, least privilege, credential protection, network egress controls, and human approval gates. The author emphasizes that prompt-level instructions are not a real security boundary and asks the community about practical setups.

What we have learned at OpenShell applying formal methods to control AI agents

Hacker News Top

The article addresses the challenges of scaling human oversight for AI agents and demonstrates using formal methods with the Z3 library to verify that agent policy changes stay within approved permissions.