Ever need to reverse engineer how a browser extension is doing what it’s doing? Well, with a little help from Cursor I was able to do just that. The use case here was determining how the extension was parsing pages (i.e. what it was looking for and how it got what to look for), and then how it was invoking the thing it does (in this case making a HTTP call with info it found on a page).

Fortunately the prompt was stupid simple:

download the extension for [urlToChromeExtension] into [folder]

Cursor downloaded the .crx file, unpacked it into a .zip, then extracted the zip to a folder. Amazing!

From there it was simply a matter asking questions about the unpacked code.