Automated Chrome-Thunderbird Installer Development
Budget: $30 – $250 USD
PROJECT OBJECTIVE.
Develop a robust Windows installer that sets up my existing automation so that it runs reliably on any Windows 11 laptop with Google Chrome and Mozilla Thunderbird installed. The automation currently comprises a Chrome Tampermonkey userscript and Thunderbird-side components. The installer must place the right files in the right locations, register any scheduled tasks or services needed, and ensure the system runs on startup without manual steps.
WHAT IS DOES
In Mozilla Thunderbird, a custom "Open in CRM" button is added to every inbox message (script attached). When clicked, it launches ChatGPT in Google Chrome and opens the conversation associated with the message's sender email on the next available Windows virtual desktop above the current one, without switching the user to that desktop. Inside that ChatGPT tab, a custom "Open" button (via a Tampermonkey script, available on request) loads the client's files and opens the relevant ChatGPT chat in Google Drive.
BIDDING
All bids are final.
WHAT YOU WILL CREATE
2(a) A zip archive of the current working materials.
2(b) Contents include the Tampermonkey userscript, helper scripts (PowerShell and batch where applicable), configuration files, and any Thunderbird add-on or script stubs now in use. (all attached here, they work)
WHAT THE SYSTEM MUST DO.
3(a) In Chrome, the Tampermonkey userscript must detect the relevant pages and events, capture the required data, and hand it off to the Windows host component by a reliable bridge you propose and implement.
3(b) In Thunderbird, the automation must receive that handoff and perform the intended actions against open windows or mail items without stealing focus or changing the user's active desktop.
3(c) The full flow must run quietly in the background, create clear logs for diagnostics, and recover gracefully from common failure cases such as Chrome or Thunderbird not running, version updates, or temporary network errors.
3(d) The solution must honour my standing constraint that it never creates new virtual desktops, never switches the user's current desktop, and opens any new Thunderbird context only in the background on the next existing available virtual desktop in ascending order until all existing desktops are filled.
TARGET ENVIRONMENT.
4(a) Operating system: Windows 11, fully patched.
4(b) Browsers and mail client: latest stable Chrome and latest stable Thunderbird at the time of delivery.
4(c) No administrative rights should be required at run time. Administrative rights may be used once during installation if clearly justified.
Chrome workflow (Tampermonkey).
5(a) The userscript runs within Chrome and listens for defined URL patterns and DOM events.
5(b) On match, it extracts structured data and posts it to the Windows host component using a secure local channel such as native messaging, localhost HTTP on a random high port with CSRF protection, or a named pipe. You will recommend the most robust approach and implement it end to end.
5(c) The userscript must expose a small settings panel in the Tampermonkey menu for per-machine tweaks, stored in Tampermonkey storage and readable by the host component if needed.
THUNDERBIRD WORKFLOW.
6(a) The host component or Thunderbird add-on receives the data from Chrome and applies the action logic to Thunderbird.
6(b) Actions may include locating or opening the relevant message, updating state, and triggering defined routines while respecting the background-only and no-desktop-switch rules.
6(c) Where Thunderbird APIs are required, implement a minimal signed add-on or a script using supported automation interfaces. If an add-on is necessary, provide signed and unsigned builds plus clear build instructions.
INSTALLER REQUIREMENTS.
7(a) Deliver a single installer that runs on any Windows 11 laptop with Chrome and Thunderbird already installed.
7(b) The installer must detect Chrome and Thunderbird, install the host component, register any services or Scheduled Tasks needed, and import or prompt to install the Tampermonkey userscript.
7(c) The installer must offer a simple first-run configuration screen for file paths, logging level, and start-with-Windows options, and then write those settings to a human-readable config file.
7(d) Provide a clean uninstaller that removes all installed components and scheduled tasks without touching user data.
DELIVERABLES.
8(a) A signed Windows installer (.exe or .msi) that performs the complete setup.
8(b) Source code in a private repository with build scripts so I can reproduce the installer.
8(c) The updated Tampermonkey userscript, any Windows services or helper executables, and any Thunderbird add-on code.
8(d) A concise admin guide covering installation, configuration, operation, logging, and troubleshooting.
8(e) A user guide with a plain sequence showing how the Chrome-to-Thunderbird flow works in practice.
8(f) Release notes stating tested versions of Chrome and Thunderbird and any known limitations.
SECURITY, PRIVACY, AND RESILIENCE.
9(a) All local communications between Chrome and the host component must be authenticated and limited to the local machine.
9(b) No data should be sent off the machine unless explicitly configured.
9(c) Log files must avoid sensitive content or provide redact options.
9(d) The system must handle version updates of Chrome and Thunderbird without breaking, or fail closed with a helpful diagnostic.
ACCEPTANCE CRITERIA AND TESTS.
10(a) A fresh Windows 11 laptop with Chrome and Thunderbird installed can run the installer and get a working system without manual edits.
10(b) The Chrome trigger reliably hands off data to the host, and Thunderbird actions complete in the background with no focus theft and no desktop switching.
10(c) After a reboot, the system starts automatically and functions as above.
10(d) Uninstall leaves the machine clean and stable.
10(e) You will provide a short test plan I can follow to verify each step.
DOCUMENTATION AND SUPPORT.
11(a) Provide clear build instructions so I can regenerate the installer and packages.
11(b) Provide a 30-day defect warranty covering fixes for bugs found in normal use on the stated environment.
11(c) Propose an optional maintenance arrangement for future version bumps of Chrome and Thunderbird.
Skills required.
12(a) Strong Windows development experience including installers and Scheduled Tasks.
12(b) Browser extension or Tampermonkey userscript development.
12(c) Thunderbird automation or add-on development, or equivalent Windows automation experience.
12(d) Secure inter-process communication on Windows.
How to bid.
13(a) Briefly describe your proposed bridge between Chrome and Thunderbird and why you prefer it.
13(b) Confirm you can meet the background-only and no-desktop-switch constraints.
13(c) Share one or two relevant examples of Windows installers or browser-to-desktop integrations you have delivered.
13(d) Provide a fixed-price quote and an estimated delivery timeframe.
HANDOVER PACKAGE I WILL SUPPLY.
14(a) The zip of current scripts and configuration files with a readme describing present behaviour and any known pain points. (attached to this posting)
14(b) A short list of target URLs and trigger conditions for the Tampermonkey userscript.
14(c) Other Tampermonkey scripts.
OUTCOME.
A developer should be able to take the supplied zip and deliver a single, reliable installer that gets a Windows 11 machine from zero to a fully working Chrome-to-Thunderbird automation in one pass, with clean logs, resilience to updates, and straightforward support materials.
WORKING DIRECTORY
C:\Tools\ChatGPTClientLauncher\
FILES
Attached in a zip file with a README note explaining them. You can install the Thunderbird Scripts in Tools >> addons & Themes >> Gear Icon >> Install addon from file >> select the file in the attached zip file called Project Scripts.zip
HOW TO DEPLOY THE ATTACHED SCRIPTS
Unzip the package to C:\Tools\ChatGPTClientLauncher.
Open PowerShell as Administrator and run the installer script there (or create two scheduled tasks that run RunListener.ps1 and RunPump2.ps1 at logon), then reserve the URLs so the listener can use http://127.0.0.1:9805
In Thunderbird, open the "Open In CRM — HTTP" add-on settings and set the target to: http://127.0.0.1:9805/open?email={email}
Check it's alive by running: Invoke-RestMethod http://127.0.0.1:9805/health
(should return OK).
Click "Open in CRM" on an email; Chrome should open ChatGPT with that address.
Optional: place a window-mover tool at C:\Tools\ChatGPTClientLauncher\bin\MoveToNextDesktop.exe so the new window is sent to the next virtual desktop
REQUIRES:
Google Chrome
Mozilla Thunderbird.
VirtualDesktopAccessor.dll (in attached zip file or fresh from Github) https://github.com/Ciantic/VirtualDesktopAccessor
AutoHotKey v2. https://www.autohotkey.com/v2/
Tampermonkey extension for Chrome> https://www.tampermonkey.net/
ChatGPT account. (not necessarily a paid one).
Develop a robust Windows installer that sets up my existing automation so that it runs reliably on any Windows 11 laptop with Google Chrome and Mozilla Thunderbird installed. The automation currently comprises a Chrome Tampermonkey userscript and Thunderbird-side components. The installer must place the right files in the right locations, register any scheduled tasks or services needed, and ensure the system runs on startup without manual steps.
WHAT IS DOES
In Mozilla Thunderbird, a custom "Open in CRM" button is added to every inbox message (script attached). When clicked, it launches ChatGPT in Google Chrome and opens the conversation associated with the message's sender email on the next available Windows virtual desktop above the current one, without switching the user to that desktop. Inside that ChatGPT tab, a custom "Open" button (via a Tampermonkey script, available on request) loads the client's files and opens the relevant ChatGPT chat in Google Drive.
BIDDING
All bids are final.
WHAT YOU WILL CREATE
2(a) A zip archive of the current working materials.
2(b) Contents include the Tampermonkey userscript, helper scripts (PowerShell and batch where applicable), configuration files, and any Thunderbird add-on or script stubs now in use. (all attached here, they work)
WHAT THE SYSTEM MUST DO.
3(a) In Chrome, the Tampermonkey userscript must detect the relevant pages and events, capture the required data, and hand it off to the Windows host component by a reliable bridge you propose and implement.
3(b) In Thunderbird, the automation must receive that handoff and perform the intended actions against open windows or mail items without stealing focus or changing the user's active desktop.
3(c) The full flow must run quietly in the background, create clear logs for diagnostics, and recover gracefully from common failure cases such as Chrome or Thunderbird not running, version updates, or temporary network errors.
3(d) The solution must honour my standing constraint that it never creates new virtual desktops, never switches the user's current desktop, and opens any new Thunderbird context only in the background on the next existing available virtual desktop in ascending order until all existing desktops are filled.
TARGET ENVIRONMENT.
4(a) Operating system: Windows 11, fully patched.
4(b) Browsers and mail client: latest stable Chrome and latest stable Thunderbird at the time of delivery.
4(c) No administrative rights should be required at run time. Administrative rights may be used once during installation if clearly justified.
Chrome workflow (Tampermonkey).
5(a) The userscript runs within Chrome and listens for defined URL patterns and DOM events.
5(b) On match, it extracts structured data and posts it to the Windows host component using a secure local channel such as native messaging, localhost HTTP on a random high port with CSRF protection, or a named pipe. You will recommend the most robust approach and implement it end to end.
5(c) The userscript must expose a small settings panel in the Tampermonkey menu for per-machine tweaks, stored in Tampermonkey storage and readable by the host component if needed.
THUNDERBIRD WORKFLOW.
6(a) The host component or Thunderbird add-on receives the data from Chrome and applies the action logic to Thunderbird.
6(b) Actions may include locating or opening the relevant message, updating state, and triggering defined routines while respecting the background-only and no-desktop-switch rules.
6(c) Where Thunderbird APIs are required, implement a minimal signed add-on or a script using supported automation interfaces. If an add-on is necessary, provide signed and unsigned builds plus clear build instructions.
INSTALLER REQUIREMENTS.
7(a) Deliver a single installer that runs on any Windows 11 laptop with Chrome and Thunderbird already installed.
7(b) The installer must detect Chrome and Thunderbird, install the host component, register any services or Scheduled Tasks needed, and import or prompt to install the Tampermonkey userscript.
7(c) The installer must offer a simple first-run configuration screen for file paths, logging level, and start-with-Windows options, and then write those settings to a human-readable config file.
7(d) Provide a clean uninstaller that removes all installed components and scheduled tasks without touching user data.
DELIVERABLES.
8(a) A signed Windows installer (.exe or .msi) that performs the complete setup.
8(b) Source code in a private repository with build scripts so I can reproduce the installer.
8(c) The updated Tampermonkey userscript, any Windows services or helper executables, and any Thunderbird add-on code.
8(d) A concise admin guide covering installation, configuration, operation, logging, and troubleshooting.
8(e) A user guide with a plain sequence showing how the Chrome-to-Thunderbird flow works in practice.
8(f) Release notes stating tested versions of Chrome and Thunderbird and any known limitations.
SECURITY, PRIVACY, AND RESILIENCE.
9(a) All local communications between Chrome and the host component must be authenticated and limited to the local machine.
9(b) No data should be sent off the machine unless explicitly configured.
9(c) Log files must avoid sensitive content or provide redact options.
9(d) The system must handle version updates of Chrome and Thunderbird without breaking, or fail closed with a helpful diagnostic.
ACCEPTANCE CRITERIA AND TESTS.
10(a) A fresh Windows 11 laptop with Chrome and Thunderbird installed can run the installer and get a working system without manual edits.
10(b) The Chrome trigger reliably hands off data to the host, and Thunderbird actions complete in the background with no focus theft and no desktop switching.
10(c) After a reboot, the system starts automatically and functions as above.
10(d) Uninstall leaves the machine clean and stable.
10(e) You will provide a short test plan I can follow to verify each step.
DOCUMENTATION AND SUPPORT.
11(a) Provide clear build instructions so I can regenerate the installer and packages.
11(b) Provide a 30-day defect warranty covering fixes for bugs found in normal use on the stated environment.
11(c) Propose an optional maintenance arrangement for future version bumps of Chrome and Thunderbird.
Skills required.
12(a) Strong Windows development experience including installers and Scheduled Tasks.
12(b) Browser extension or Tampermonkey userscript development.
12(c) Thunderbird automation or add-on development, or equivalent Windows automation experience.
12(d) Secure inter-process communication on Windows.
How to bid.
13(a) Briefly describe your proposed bridge between Chrome and Thunderbird and why you prefer it.
13(b) Confirm you can meet the background-only and no-desktop-switch constraints.
13(c) Share one or two relevant examples of Windows installers or browser-to-desktop integrations you have delivered.
13(d) Provide a fixed-price quote and an estimated delivery timeframe.
HANDOVER PACKAGE I WILL SUPPLY.
14(a) The zip of current scripts and configuration files with a readme describing present behaviour and any known pain points. (attached to this posting)
14(b) A short list of target URLs and trigger conditions for the Tampermonkey userscript.
14(c) Other Tampermonkey scripts.
OUTCOME.
A developer should be able to take the supplied zip and deliver a single, reliable installer that gets a Windows 11 machine from zero to a fully working Chrome-to-Thunderbird automation in one pass, with clean logs, resilience to updates, and straightforward support materials.
WORKING DIRECTORY
C:\Tools\ChatGPTClientLauncher\
FILES
Attached in a zip file with a README note explaining them. You can install the Thunderbird Scripts in Tools >> addons & Themes >> Gear Icon >> Install addon from file >> select the file in the attached zip file called Project Scripts.zip
HOW TO DEPLOY THE ATTACHED SCRIPTS
Unzip the package to C:\Tools\ChatGPTClientLauncher.
Open PowerShell as Administrator and run the installer script there (or create two scheduled tasks that run RunListener.ps1 and RunPump2.ps1 at logon), then reserve the URLs so the listener can use http://127.0.0.1:9805
In Thunderbird, open the "Open In CRM — HTTP" add-on settings and set the target to: http://127.0.0.1:9805/open?email={email}
Check it's alive by running: Invoke-RestMethod http://127.0.0.1:9805/health
(should return OK).
Click "Open in CRM" on an email; Chrome should open ChatGPT with that address.
Optional: place a window-mover tool at C:\Tools\ChatGPTClientLauncher\bin\MoveToNextDesktop.exe so the new window is sent to the next virtual desktop
REQUIRES:
Google Chrome
Mozilla Thunderbird.
VirtualDesktopAccessor.dll (in attached zip file or fresh from Github) https://github.com/Ciantic/VirtualDesktopAccessor
AutoHotKey v2. https://www.autohotkey.com/v2/
Tampermonkey extension for Chrome> https://www.tampermonkey.net/
ChatGPT account. (not necessarily a paid one).