$ show QLHazyCoder/FlowPilot
FlowPilot is a Chrome extension that automates the registration, verification, and delivery of accounts for AI platforms like OpenAI/ChatGPT, Grok (xAI), and Kiro (AWS). It handles email verification codes from a wide range of providers (Hotmail, iCloud, 2925, Gmail, etc.) and SMS verification through multiple services (5sim, HeroSMS, MaDao). The extension features a step-based workflow engine that composes registration flows dynamically based on signup method, payment mode, and delivery target. It includes an auto-run controller for batch account creation, account delivery to external APIs (CPA, SUB2API, etc.), and a contribution system for sharing accounts. Architecturally, it follows the standard Chrome extension pattern with background scripts, content scripts, and a sidepanel UI. The codebase is modular, using factory functions with dependency injection for testability. It has an extensive test suite with over 200 test files, though tests rely on a fragile function extraction method. The project is actively maintained with frequent commits and a versioned release cycle. The codebase demonstrates good engineering practices including a registry pattern for steps and mail rules, i18n support for Chinese and English, and reusable UI components. However, there are some maintenance concerns such as duplicate files, hardcoded external URLs, and dormant code paths for payment features.
The LLM identified 4 files worth highlighting for reuse:
Provides a runtime for internationalization with locale resolution, string interpolation, and DOM element translation. It can be extracted as a standalone i18n library for Chrome extensions or web applications, supporting Chinese and English with extensible catalogs.
Generates random email local parts using configurable patterns (name, date, suffix). This utility is self-contained and can be reused in any project requiring email address generation, such as test data factories or account creation tools.
Implements a step registry that caches flow-specific step definitions and provides lookup by step ID. The registry pattern with caching and flow isolation can be extracted for any step-based workflow system, decoupling step definitions from execution logic.
Builds verification code polling payloads based on per-flow mail rules (sender, subject, code pattern). This rule-based approach to mail polling can be generalized for any automation system that needs to extract verification codes from emails, with configurable patterns and fallback strategies.