May 30, 2026
Sealed, stamped, and side-eyed
Show HN: Open Envelope – an open schema for defining AI agent teams
A new way to organize AI helpers lands, and the crowd instantly starts arguing over who should control it
TLDR: Open Envelope wants to create an open recipe for teams of AI helpers so companies aren’t stuck with one vendor’s system. Commenters instantly split between cheering the independence and arguing the approach is too rigid, turning the launch into a fight over openness versus convenience.
A new Show HN post is pitching Open Envelope as a shared rulebook for building teams of AI helpers — basically a way to describe who does what, how they talk, what they can access, and when a human has to step in. The pitch is that this should be open, reusable, and not locked to one company’s app. Sounds neat and orderly. Naturally, the comments immediately turned into a mini cage match over whether this is the future or just another layer of paperwork.
The biggest tension? Open freedom versus big-platform convenience. One commenter pointed straight at Claude Code workflows and basically said, "Uh, isn’t a giant AI company already trying to own this whole space?" That framed Envelope as the rebel move: a vendor-neutral alternative for people who don’t want one company deciding how all their AI assistants work. But then came the classic builder backlash. Another commenter declared the project’s core philosophy "kinda wrong," arguing that writing everything as a static rule sheet can feel clunky, and that more flexible code-first approaches often win in the real world.
So yes, the launch got the full internet treatment: part hopeful open-standard cheerleading, part eye-rolling "we’ve seen this movie before," and part nerdy turf war over the "right" way to build tools. The jokes weren’t loud, but the subtext was deliciously spicy: do we really need an open envelope, or is this just more AI bureaucracy with nicer branding?
Key Points
- •Envelope publishes a schema reference for defining AI agent teams.
- •The documentation emphasizes a declarative, open-schema approach and includes sections on why the schema is open sourced and how builders use it.
- •The schema supports use in editors, local validation workflows, CI/CD pipelines, and version-controlled environments.
- •Its reference covers team definitions, workspaces, agent definitions, role and adapter types, access policies, human gates, and pricing-related structures.
- •The documentation also specifies runtime and operational features such as installation contracts, invocation modes, authentication, streaming via SSE, validation, scheduling, and inbound webhooks.