Bing’s AI chat can be extremely useful, but it requires that you use Microsoft Edge. Some of us just don’t want to use Edge, even though it probably is better, we’ve had our time with Microsoft and want to limit our exposure to one monopoly.
So how do you use Bing AI chat on Chrome?
At least as of this writing I’ve got it working with changing the shortcut target on my desktop by adding the following:
--user-agent="Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/220.127.116.11 Safari/537.36 Edg/117.0.2045.43"
I personally made a copy of the shortcut and call it Google Chrome as Bing, but you do whatever floats your boat.
After you’ve made the change either reboot your computer or open up a command prompt and type:
taskkill /im chrome.exe
This will kill any of the Chrome processes that are running that will spoil your changes. Launch Chrome via the Chrome as Bing shortcut you just made, and at least for me, at least today Bing’s not refusing my Chrome.
The target on your shortcut should look something like
"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --user-agent="Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/18.104.22.168 Safari/537.36 Edg/117.0.2045.43"
I would advise updating the Chrome and Edge versions as your Chrome version updates in the event you ever run into a website that needs to deliver content that is browser version specific… but for now, today, this works for me.
If it doesn’t work for you, and you rebooted/task killed, let me know. I did it without the taskkill on a Windows 11 box, and then had to taskkill on a Server 2019 I was using to verify it worked and not just for my account.
At this point, Edge is probably slightly better than Chrome, but I’m still way too Microsoft’d out and a bit more than annoyed that MS uses Chrome (I know they contribute to it,) and then releases products that actively don’t work with the product they’re using to create their branded version.
My lawn, get off it Microsoft!
Obviously MS can just request something specific from the browser later on to work around this workaround, but as of Sep 29 2023 it’s working.