I've got the same error on my side. At first I thought it was some weirdness with Firefox, but opening on Chrome gives the same result.

I don't know what causes this bug specifically, but encountered similar behavior when I asked claude to create some frontend for me. It may not even be the same bug, but I find it an interesting coincidence.