Repository navigation
Status check: does current main generate video reliably after the 2026-09-22 Flow change? (question for maintainer and users) #74
Description
Before we update our installation, we would like to confirm whether current main works end to end again. Several related issues were closed as "fixed" (#58, #63, #67, #71) without a test result attached, and at least one report after the fix still shows refusals. A short status from the maintainer, and from anyone running FlowKit today, would help many users decide whether it is safe to update.
What we hit (one Google AI Ultra account, Windows):
- From 2026-09-12: 401 on every call after Flow moved to flow.google.com and batchexecute (no more Bearer token). Fixed for us by pulling Feat/flow batchexecute migration #39.
- 2026-09-07: intermittent 403 on video generation, where the job itself usually completed shortly after (similar to Bug: repeated API_403 on GENERATE_VIDEO even with MAX_CONCURRENT_REQUESTS=1, no retry, and 1s cooldown #11 and Bug: repeated API_403 on GENERATE_VIDEO even with MAX_CONCURRENT_REQUESTS=1, no retry, and 1s cooldown #12).
- From 2026-09-22, between 16:45 and 17:52 UTC: every captcha-gated submit refused with
PUBLIC_ERROR_UNUSUAL_ACTIVITY(timeline in Every captcha-gated RPC returns PUBLIC_ERROR_UNUSUAL_ACTIVITY since the Flow frontend build of 2026-09-22, while the UI itself still works #58). Our checkout predates fix(extension): mint reCAPTCHA via hidden widget — unblocks generate after the 2026-09-22 build #62 and feat: bypass extension_hijack_detected + Trusted Types CSP #64, so we have not tested those fixes ourselves. We paused FlowKit on 2026-09-28 because of [HIGH PRIORITY][WARNING] Persistent "unusual activity" account block after FlowKit testing (manual Flow UI blocked) #67.
Questions for @crisng95:
- On current
main(latest commit 2026-10-06), have you generated video successfully after fix(extension): mint reCAPTCHA via hidden widget — unblocks generate after the 2026-09-22 build #62? Which date, which model (Veo 3.1 Fast, Quality, Lite, or Omni Flash), and how many submits in a row? - Does the fix(extension): mint reCAPTCHA via hidden widget — unblocks generate after the 2026-09-22 build #62 hidden-widget mint keep working after a full Chrome and agent restart? In Every captcha-gated RPC returns PUBLIC_ERROR_UNUSUAL_ACTIVITY since the Flow frontend build of 2026-09-22, while the UI itself still works #58, @Bl0ck154 reported that it stopped working after a restart.
- Is the feat: bypass extension_hijack_detected + Trusted Types CSP #64
extension_hijack_detectedbypass active by default? Given [HIGH PRIORITY][WARNING] Persistent "unusual activity" account block after FlowKit testing (manual Flow UI blocked) #67, can it be turned off, and what do you recommend? - Which values of
FLOW_MAX_CONCURRENTandFLOW_COOLDOWN_Sdo you consider safe for an Ultra account? - Is Gate Flow CAPTCHA generation after account-safety reports #68 (persistent safety hold) planned for merge?
- For the account-level block described in [HIGH PRIORITY][WARNING] Persistent "unusual activity" account block after FlowKit testing (manual Flow UI blocked) #67, is any recovery known?
For other users running current main: if FlowKit works for you today, could you reply with the date, the commit you run, the model, roughly how many submits per hour, whether you hit any UNUSUAL_ACTIVITY, and whether the #64 bypass is on? Failure reports are just as useful.
Thank you for maintaining FlowKit.
Activity
buiminhhieu-svg commentedon Oct 15, 2026
Quick check-in for anyone still running FlowKit, about a week after #67.
Our status, for comparison: FlowKit has been fully stopped on our side since 2026-09-28. As of 2026-10-10, our Ultra account still generated normally in the manual Flow UI.
Even a one-line "still working" or "blocked since X" helps others decide whether it is safe to update. Please do not paste cookies, tokens or account identifiers.
crisng95 commentedon Oct 24, 2026
Thanks for keeping this thread going — maintainer status below.
main(b09e783) on one paid account: reference images, scene images and an 8s video all completed. Six Flow generate submits in total, none refused withUNUSUAL_ACTIVITY. The only failure was theNARWHALimage model, which Google has retired ([5] NOT_FOUND);NANO_BANANA_2will map toBELUGA.On safety: an audit confirmed the concern raised in #67. A failed reCAPTCHA bypass (
extension_hijack_detected) was retried without a limit, and the unusual-activity hold was in-memory with a 120s default. #75 fixes both: hijack failures stop after 3 attempts, and the hold now defaults to 1 hour and survives an agent restart. It takes the persistent-hold idea from #68 onto the current transport. Until it is merged, settingFLOW_UNUSUAL_ACTIVITY_COOLDOWN_S=86400is a reasonable precaution.crisng95 commentedon Oct 25, 2026
Update: #75 (persistent unusual-activity hold, 1h default; hijack retries capped at 3) and #76 (
NANO_BANANA_2→BELUGA) are merged intomain(6844a88). Pull and restart the agent to get them — theFLOW_UNUSUAL_ACTIVITY_COOLDOWN_Soverride is no longer needed unless you want a longer hold. Leaving this open for status reports from other users.