Is there a Turbo Flow extension?

Short answer: no — and if you are looking for one, you may be looking for a different product. This Turbo Flow (turboflow.online, by Adventure Wave Labs) is the open-source rules layer for AI-written code. It ships no browser extension, no VS Code extension, no plugin of any kind — on purpose. What installs instead is rig-lite, a bash kit that lives in your repository, and the AGENTS.md file (with its CLAUDE.md symlink) your harness reads.

Published Oct 10, 2026 · Updated Oct 10, 2026

If you want the Chrome add-on that automates Google Flow

There is a paid Chrome Web Store extension called TurboFlow (“Auto Flow on Google Flow”, published at turboflow.art) that auto-submits prompts, upscales, and downloads AI video from Google Flow. It is not this project and not this company — same name, unrelated makers. If that is what you were searching for, the Chrome Web Store listing is where it lives. We cannot help with it, its pricing, or its permissions — and this page exists partly so search engines stop blending the two products.

What “installing” this Turbo Flow actually looks like

Nothing attaches to your browser or editor. The governance ships inside your repo, so a harness that can read a markdown instruction file and run bash picks it up the same way — the kit's own compatibility rule from its README, and the loop this project runs in production: ZCode builds, Claude Code reviews, Codex backs up the review:

# from any repo you want to govern:
bash /path/to/turbo-flow/rig-lite/init-repo.sh   # writes AGENTS.md (+ CLAUDE.md symlink)
bash /path/to/turbo-flow/rig-lite/self-test.sh   # proves the kit fails closed
/path/to/turbo-flow/rig-lite/gate.sh --pr 1 --builder claude

One file, both formats — AGENTS.md for Codex and friends, CLAUDE.md (a symlink to it) for Claude Code — that is the closest thing to an “extension” in this project, and it needs no store, no plugin, and no permissions. The details: the AGENTS.md template page and the rig-lite kit. For the optional Claude Code orchestration mod (Ruflo, third-party), see the version history.

Why no extension, ever?

Because governance that lives in a browser or editor extension is governance one uninstall away from gone. The whole v5 design lesson (the pivot essay) was that the durable layer is state in the repository — the gate, the constitution, the memory — enforced by code every clone already carries. An extension would be a second place to be out of sync. So: no extension, one kit, in your repo.