How mslolita/grass works
Grass Auto Reger&Farm automates account registration, verification and wallet setup, or runs accounts to farm and claim points. Users configure accounts, proxies, wallets and mode flags, then start the console or UI; main.py loads inputs and dispatches account workers through AutoReger. Each worker delegates Grass operations to the client, which handles REST actions and the extension-style WebSocket farming session. The README also documents email approval, wallet linking, points checks and reward claiming. Edges follow the sampled calls and documented modes; some internal wiring is unsampled, so uncertain links are omitted.
Main entry points: main.py Runner and worker · grass.py Grass client · autoreger.py Account scheduler · extension.py Extension session
Components 20
Run orchestration
- Runner and worker
main.py - Account scheduler
core/autoreger.py - Desktop UI
interface.py
Account operations
- Grass client
core/grass.py - Grass REST API
core/grass_sdk/website.py - Captcha solver
core/utils/captcha_service.py - Email approval
core/utils/mail/mail.py - Profile generation
core/utils/generate/person.py
Farming runtime
- Extension session
core/grass_sdk/extension.py
Inputs and state
- Account inputs
data/accounts.txt - Proxy inputs
data/proxies.txt - Wallet inputs
data/wallets.txt - Mode configuration
data/config.py - Proxy database
core/utils/accounts_db.py - Run results
core/autoreger.py
Other components
- Operator
- Grass service
- Grass director
- Email provider
- Captcha provider
Connections 23
- Operator → Runner and worker: starts run
- Operator → Desktop UI: starts UI
- Desktop UI → Runner and worker: starts UI mode
- Runner and worker → Account inputs: reads accounts
- Runner and worker → Proxy inputs: reads proxies
- Runner and worker → Wallet inputs: reads wallets
- Runner and worker → Mode configuration: reads modes
- Runner and worker → Proxy database: loads proxies
- Runner and worker → Account scheduler: builds and starts
- Account scheduler → Runner and worker: dispatches worker
- Account scheduler → Run results: writes results
- Runner and worker → Grass client: runs account actions
- Runner and worker → Profile generation: generates credentials
- Grass client → Grass REST API: calls REST handlers
- Grass REST API → Grass service: sends API requests
- Grass client → Extension session: starts farming session
- Extension session → Grass director: requests connection
- Extension session → Grass service: exchanges WebSocket traffic
- Grass client → Proxy database: gets replacement proxies
- Runner and worker → Email approval: email approval mode
- Email approval → Email provider: searches approval mail
- Runner and worker → Captcha solver: registration mode
- Captcha solver → Captcha provider: requests solve token