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've been running Ota against real-world repos to see how it handles messy setup, drifted docs, hidden dependencies, and inconsistent run paths.
If you want to see what Ota would surface in your repo, drop the Github link below. We'll pressure-test it, draft an `ota.yaml`, and open a PR so you can see exactly what it found and how the execution contract takes shape.
If you ve been following along and want to support us, we d really appreciate a GitHub star:
https://github.com/ota-run/ota
We just crossed 50 followers here on Product Hunt! Thank you so much for every follow, comment, question, and bit of feedback. For an early product, it really does mean a lot.
As a small gesture of appreciation, here s a fun little backstory: we chose an otter as our logo because otters sleep floating on water while holding hands so they don t drift away with the current.
Most repos already contain the command you need. The hard part is knowing which one is actually intended.
There may be scripts, Make targets, Docker commands, CI-only paths, and old setup notes. Some still work. Some are stale. Some only work after other services are already running.
Ota brings execution governance to every software repository through a machine-readable execution contract for humans and AI agents. It replaces scattered setup instructions, execution drift, and AI guesswork with one source of truth for how software should run, verify, and evolve.
This release makes repo readiness clearer before anything even runs.
Ota now does a better job checking the right version, tools, OS setup, Python/uv support, Windows requirements, dry-run status, and agent safety boundaries.
The goal is simple: make repo execution easier to trust.