AutoFlowBoss

Support and FAQ

Last updated: 2026-05-15

Support Scope

AutoFlowBoss supports automation workflows on supported Flow pages at labs.google.

Support topics include:

  • installation and loading the extension
  • license activation and validation
  • prompt and reference-image setup
  • batch start and stop behavior
  • gallery scan and downloads
  • understanding Chrome permission prompts and debugger infobar behavior

Quick Start

  1. Open a supported Flow page on labs.google.
  2. Open AutoFlowBoss from the toolbar popup or side panel.
  3. Go to the License tab and activate a valid license key.
  4. Add one or more reference images.
  5. Enter a prompt or load a .txt prompt file.
  6. Adjust settings such as output count, orientation, model, and loop count.
  7. Click Start Process.
  8. Review generated results in the Gallery tab or Downloads folder.

FAQ

What websites does AutoFlowBoss support?

AutoFlowBoss is designed only for supported Flow pages on labs.google.

Is AutoFlowBoss an official Google product?

No. AutoFlowBoss is an independent product and is not affiliated with or endorsed by Google.

Why does Chrome show a debugging warning or infobar?

The current extension build uses the Chrome Debugger API as a fallback interaction method for parts of the Flow page when standard click methods are not reliable enough. Chrome may show a debugger-related infobar as a result.

Why does the extension ask for download permission?

The extension uses the browser Downloads API to save generated outputs to the user's Downloads folder as part of the core workflow.

Why does the extension need access to labs.google?

The extension only operates on supported Flow pages. It needs access to those pages to automate the workflow, detect state changes, capture outputs, and coordinate downloads.

Why does the extension contact an external server?

The extension contacts the license service to activate, validate, and deactivate product licenses.

What data is sent to the license service?

The current extension build sends license-related fields needed for licensing, such as:

  • licenseKey
  • deviceId
  • sessionToken
  • appVersion

Are prompts or images uploaded to the license server?

In the current extension build, no code path was found that sends prompt text, selected reference images, or generated output images to the developer license endpoint.

Where are my settings and gallery stored?

The extension stores settings, queue metadata, gallery data, logs, and license state locally in the browser profile.

What should I do if the license activation fails?

Check the following:

  • the license key format
  • internet connectivity
  • whether the license service is reachable
  • whether the device was already activated elsewhere

If the problem continues, contact support through the public contact method that you choose to publish for AutoFlowBoss.

What should I do if Flow is open but the extension says it cannot find the tab?

Make sure:

  • the page is a supported Flow page on labs.google
  • the tab is fully loaded
  • the extension is enabled
  • the browser session has not disabled the extension

Can I stop a running process?

Yes. The current UI provides Stop Process while a batch is running.

Where are downloaded files saved?

Generated files are saved to the browser Downloads folder, or to the selected Downloads subfolder if you set one in the extension UI.

Support Contact

Support contact: zhoeydev@gmail.com