Budget: 400 PLN Deadline: 30 days
To ensure stable operation in 6–8 OctoBrowser windows without moving the mouse cursor, standard AHK commands like Click or ControlClick will not be sufficient, as Chromium browsers poorly handle "surface" clicks in the background.
Technical implementation strategy:
Chrome DevTools Protocol (CDP): The most reliable method for background operation is using the Chrome.ahk library. Instead of emulating the mouse, the script will communicate directly with the browser engine through the debugging port. This allows clicking on elements and scrolling pages, even if the windows are completely overlapped or minimized.
Multiprofile through ports: In the OctoBrowser settings, each profile must be assigned a unique Remote Debugging Port (for example, 9222, 9223, etc.). The script will launch separate management instances for each port, ensuring complete independence of threads.
Background scrolling and clicks:
Scrolling: Instead of Send {PgDn}, we use JS injection window.scrollBy(0, 500), which executes instantly and without focus.
Clicks: The DOM.dispatchMouseEvent method is used via CDP. This is a "genuine" click at the browser level that does not involve the Windows system cursor.
Stability (Watchdog logic): For long cycles, we will add a check for the "survivability" of the page. If the profile hangs or the page returns an error, the script will detect this through the port status and will be able to reload the tab without stopping the operation of the other 7 windows.
Clarifying question:
Do you use fixed debugging ports in the OctoBrowser profile settings, or does the script need to dynamically capture active processes through the window title?
