agentcontract Ships Portable JSON Permissions Across AI Coding Agents
Key insights
- agentcontract v0.0.1 lets teams define AI coding agent permissions once in JSON, covering Claude Code, Codex, and Hermes.
- The project directly targets the absence of any shared permission standard across today's fragmented AI coding agent market.
- The open-source spec encodes allowed operations, forbidden file paths, and budget constraints in a single portable config file.
Why this matters
The AI coding agent market is fragmenting permission management the same way early cloud fragmented IAM, creating compounding compliance debt for teams running multiple agents in parallel. A portable permission contract, if adopted broadly, shifts governance from individual vendor siloes to a shared abstraction layer that teams can audit, version, and enforce consistently across their toolchain. For enterprise buyers evaluating Claude Code, Codex, or Hermes alongside each other, a vendor-neutral permission spec lowers switching cost and reframes competitive differentiation away from permission UI toward raw agent capability.
Summary
A solo developer released agentcontract v0.0.1, a declarative JSON permission spec designed to work across Claude Code, Codex, and Hermes without rewriting configs per tool.
AI coding agents currently enforce safety through incompatible proprietary APIs. agentcontract defines allowed operations, forbidden paths, and budget ceilings in one JSON file any agent harness can parse, replacing three separate permission models with a single portable contract.
Essentially: (Claude Code, Codex, Hermes) each require separate permission models today; agentcontract is a proposed common layer.
- v0.0.1 ships on GitHub with integration examples for all three platforms.
- The spec covers allowed operations, forbidden paths, and budget constraints in one config.
- The project is open-source and product-agnostic by design.
If agent permission sprawl follows API key management's trajectory, a portable contract standard could become core infrastructure for multi-agent enterprise deployments.
Potential risks and opportunities
Risks
- Without adoption from Anthropic, OpenAI, or Hermes maintainers, agentcontract risks becoming an unmaintained shim that lags behind rapidly evolving native permission APIs.
- Enterprise teams standardizing on agentcontract v0.0.1 may face breaking changes if the spec evolves without a formal governance process or versioning commitment from the solo maintainer.
- A single-developer open-source permission layer governing AI agent operations could attract security scrutiny; any parsing vulnerability in agentcontract would expose the full operation surface of any agent it controls.
Opportunities
- Enterprise AI platform vendors (Cursor, Codeium, GitHub Copilot) could adopt agentcontract as a default permission layer to differentiate on safety and multi-agent compatibility before rivals do.
- Security tooling companies (Snyk, Semgrep) could integrate agentcontract spec validation into existing developer security workflows as AI coding agent adoption in regulated industries accelerates.
- Anthropic or OpenAI could gain first-mover advantage by formally endorsing or extending agentcontract, effectively setting the default semantics for cross-agent permission standards before a competitor does.
What we don't know yet
- Whether Anthropic, OpenAI, or Hermes maintainers have acknowledged agentcontract or signaled any intention to natively support the spec.
- How agentcontract handles permission conflicts when agents chain or delegate tasks across multiple sub-agents in a single session.
- Whether v0.0.1's budget constraint mechanism integrates with token-level billing APIs from OpenAI or Anthropic, or operates as a fully independent layer.
Originally reported by reddit.com
Read the original article →Original headline: r/AI_Agents: Developer Ships agentcontract v0.0.1 — Product-Agnostic JSON Permission Layer for AI Coding Agents Spanning Claude Code, Codex, and Hermes