Task Description
There is a working desktop program for Windows that successfully:
🖥️ launched real Chrome profiles;
👤 logged into Three+ accounts;
🎁 clicked Get Reward;
📄 navigated to My Codes;
🔢 read a code of the type TH3DC\d{9,};
💾 saved it in CSV.
After the Chrome update, the program stopped working (connection error to CDP).
⚠️ Important:
The project is NOT from scratch.
90% of the logic and infrastructure is already ready and can be used.
What Needs to Be Done
⚙️ adapt Chrome launch to the new version
⚙️ adapt CDP for Puppeteer/Playwright
⚙️ test the work with profiles
⚙️ build into .exe
⚙️ make minimal adjustments for stability
The algorithm, DOM parsing, transitions, delays — are already implemented in the old version.
Input Materials Provided
📂 full source code of the old program
📂 example CSV and settings.json
📂 test Chrome profiles
📂 technical task
📂 list of profiles and paths
So the work is adaptation, not full development.
Main Requirements
🪟 Windows desktop (.exe)
🦊 Puppeteer or Playwright
🗂️ real Chrome (user-data-dir + profile-directory)
🚫 not headless
🚫 no Selenium
🚫 no HTTP requests
🔍 code is read through the DOM from the My Codes page
💻 write to CSV
🖱️ simulate clicks
⏳ delays
Expected Result
✔️ working .exe (not a strict requirement — direct launch through node index.js is allowed if it is more convenient and faster)
📄 README
Estimated Complexity of Work
⏱️ 2–4 hours for a developer who has worked with Chrome CDP.
Ideal Candidate
🎯 Puppeteer / Playwright
🎯 CDP
🎯 experience working with Chrome profiles
Please indicate in your application:
🛠️ which tool you will use (Puppeteer or Playwright)
⏳ estimated timeframe
💰 budget
If needed, I will provide:
📦 archive of the old program
Ready to answer questions and test.
💸 I expect a low-cost implementation
(including — because the site changes several times a month — I will regularly reach out to you for payment for minor adjustments)
🔥 Cost:
The development of the original version cost here £34
🏗️ How the program was built (what already exists)
Technologies:
🟢 Node.js
🟢 Puppeteer (Chrome DevTools Protocol)
🟢 CSV reading/writing
🟢 Working with real Chrome profiles (user-data-dir + profile-directory)
❌ No Selenium
❌ No headless
❌ No API requests
Algorithm of the old version:
1️⃣ Loading settings.json
2️⃣ Loading CSV
3️⃣ Determining profiles without code
4️⃣ Launching Chrome with parameters:
--user-data-dir
--profile-directory
5️⃣ Opening rewards_url
6️⃣ Clicking Get Reward (simulating a real click)
7️⃣ Navigating to My Codes
8️⃣ Reading a code of the type TH3DC\d{9,} through the DOM
9️⃣ Writing to CSV
🔟 Delay of 20–40 seconds
1️⃣1️⃣ Moving to the next profile
Features:
❌ no headless
❌ no Selenium/WebDriver
❌ no HTTP API
✅ real profiles (authorization already saved)
✅ the program does not trigger SMS confirmation
✅ code is read only from the My Codes page
What it already has:
📂 class structures
📂 CSV processing
📂 JSON configuration
❌ UI is not needed
📋 logging
⏳ delays (human-like)
🔀 code for transitions
📁 examples of profiles
📄 test CSV
So the logic is approximately 90% ready.
