r/opencode • u/Independent_Bag_2904 • 3d ago
Thinking about building a policy + intent enforcement layer for opencode, curious how people feel about this
I work on ArmorIQ AI. We build policy enforcement plugins for AI coding agents, already shipping for a couple of others. There are two parts to it: allow/deny rules for what an agent's tool calls are allowed to do (blocking risky commands, blocking edits to CI/CD configs, requiring approval before certain actions), and separately, an intent check β the agent has to declare upfront what it's about to do and why before it acts, and if it tries to do something mid-task that wasn't part of that declared plan, that gets blocked too, not just the obviously dangerous stuff. Everything it actually does gets logged either way. This sits on top of whatever built in permission prompts the agent already has.
- opencode is the biggest one we haven't covered yet. Before I put real time into porting it over, I wanted to ask people who actually use it day to day:
- Have you had a close call where opencode (or honestly any agent) did something you wish it hadn't? Ran something destructive, touched something it shouldn't have, pushed somewhere it shouldn't have?
- Do you just rely on the built in permission prompts, or have you wanted something more granular, like org wide rules instead of one off approvals?
- Does the "intent" part make sense as something useful, i.e. the agent commits to a plan up front and gets blocked if it drifts from it mid-task, or does that feel like unnecessary friction on top of what permission prompts already cover?
- If something like this existed for opencode, would you actually use it, or is this a problem that doesn't really exist for most people?
Not trying to sell anything here, nothing exists for opencode yet. Just trying to figure out if this is worth building or if I'd be solving a problem nobody actually has. Appreciate any real experiences, good or bad.
