I've noticed that if you ask claude code to add a GPL or AGPL license to a project it just totally stops, like some kind of weird kill switch as soon as it reads the contents of the file.
Works fine if you ask it to cp the license from one place to another or to add the name of the license to a readme or .gempsec file, but the full content of the license just stops it in it's tracks.
@andrewnez why would anyone want to use an LLM to add a license file to a project? Why throw huge amounts of computing resources on a problem that takes maybe a few seconds when doing it by hand and only has to be done once for a project? Why would anyone ever want an #LLM to read or maybe even generate the license text in order to add it to a project, a text that has already been "generated" by humans who put a lot of time and effort into creating a license that protects users' freedoms? Even if one doesn't care about the negative impact of these huge LLMs this is just a stupid way to use them.
@eruwero @andrewnez i think the point is that these tools have clearly been censored to avoid generating certain forms of output that has the potential to introduce litigation
@hipsterelectron @andrewnez yeah the FSF knows about copyright
@andrewnez Interesting. But I hope you did this just to play around and never productively use LLMs to create your license text files. It may well occur that the result contains variations that you did not intend, or that may even break the license (e.g., by adding additional restrictions).
It may not be the most fulfilling work but please invest the time to copy the original, official license. Ideally from the license steward, or from https://spdx.org/licenses/
@mxmehl even just getting it to read the file (to copy from one repo to another) causes this bug.
