If you've been following along and would like to support us we would appreciate a star of GitHub: https://github.com/ota-run/ota
Ota now supports refusal canaries. Repositories declare tasks that must remain unavailable to agents, and CI verifies that the real execution boundary rejects them with `--expect-refusal`.
In the AI era, governance cannot stop at documenting what agents may do. Teams also need negative tests proving that forbidden execution remains forbidden.
We're live! If repo setup drift, execution inconsistency, or governing what AI agents are allowed to run in a codebase is something you've thought about, today is a good day to check out what we've been building.
You can find us here: https://www.producthunt.com/prod...
Two months ago, we launched Ota on Product Hunt for the first time.
It was an amazing experience. We met developers, founders, and open source maintainers who helped us see the problem more clearly. Since then, we've shipped dozens of improvements, refined the product, improved onboarding, and listened closely to feedback from real repositories.
So we're coming back this Friday.
If you've ever joined a repo and wondered "what am I actually supposed to run?" or "why does this work locally but fail elsewhere?", that's the problem we're tackling.
Ota
