Ask HN: Releasing code under AGPLv3, but want to block LLM reconstruction?

I am preparing to release a software project under the AGPLv3. The goal is traditional copyleft reciprocity - if you use it or host it, share your changes.

However, I am realistic about the current legal landscape. Big tech corps are treating public code as free raw material for LLM training under the banner of "Fair Use". I am concerned that a company will ingest my codebase and use an LLM to effectively launder the logic, allowing their users to prompt a clean, closed-source recreation of my software without triggering the AGPL.

Do we have a licence specifically to prevent this but still keep OSS healthy and alive? Do we have a llm.txt / robots.txt that LLM scrapers respect? I feel that the whole OSS model is under threat here, even more than before (e.g. big corps earn billions from Linux instances without having to pay any software licensing cost, but they're more than happy to charge others for their own OS).