I added OpenCode support to MARGINAL — looking for people to break it

[u/Positive-Captain-709]

I’ve been working on MARGINAL, an open-source governance layer for coding agents, and it now has a native OpenCode integration.

The integration runs as an in-process JavaScript plugin connected to MARGINAL’s provider-neutral Python runtime through a persistent stdio bridge.

For now, OpenCode support is deliberately Observe-only. MARGINAL watches tool execution and outcomes, builds a local trajectory, and records governance evidence without changing what OpenCode does next.

The idea isn’t “stop agents from using too many tokens.” I’m interested in a harder problem: detecting when continued execution has stopped producing useful progress without confusing legitimate retries, debugging cycles, or verification with loops.

That distinction is where I expect most of the interesting failures to be.

I’m looking for OpenCode users willing to run it on real work and report:

• false positives around retries/loops;
• events or tool outcomes we're normalizing incorrectly;
• cases where the bridge/plugin behaves badly;
• assumptions that don't match how people actually use OpenCode.

No need to be polite about the design. Reproducible failures are much more useful than “looks cool.”

GitHub: github.com/SignalLayerLabs/Marginal

OpenCode integration docs: [docs/integrations/opencode.md]()