(Reposting a blog post by nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpq3gvpdda8dwt6r90x3ast0hyxqe5mpvgjf9fazyv0xkw5k3y3gehsgcrm88 (nprofile…rm88) copy-pasted in full from: this webpage)Can you Lisp without being strapped in to the Torment Nexus Machine?As of 2026-05-18 … sort of.
Every Lisp, Scheme, and Lisp-adjacent project listed is a non-toy implementation that is at least somewhat active. When I first wrote this article (2026-03-12), most Lisps did not have a policy or even public stance on LLM contributions. In such cases I posted to their bug trackers or discussion lists to ask. Most maintainers kindly responded.
Every link is either a document or issue stating the project’s LLM policy, or a link to an open issue. Roughly categorized according to how strongly for or against LLM contributions.
If I’m missing a project that should be listed, lemme know.Strictly Against
Fennel
STklos Scheme
Clojure
ECLStrongly Against
Loko SchemeWeakly Against
Janet exception given for tests and bug reproductions
GNU CLISP against on a specific reading of copyright law
Emacs Lisp temporarily against LLMs, waiting for official policy
Hy maintainer recommends against LLM contributions, no actual policyHesitantly Accepting
Chicken Scheme
Chibi Scheme
Cyclone Scheme
Gambit
Gauche
Gerbil Scheme LLM generated code potentially in source tree
Clasp
CCLAccepting
Bigloo
Coalton
Kawa Scheme
Sagittarius Scheme
Jank doesn’t accept external LLM contributions but permits usage by core developers
Racket LLM generated code in source tree
SBCL LLM generated code in source tree
Carp LLM generated code in source treeUnknown
Scheme 48 open issue
Chez Scheme at least one maintainer is against, another skeptical, open issue
Guile Scheme likely against but nothing officially stated, open issue
MIT Scheme open issue
ABCL open issue
LFE open issue
#tech #software #Lisp #LispLang #SchemeLang #SchemeLang #GuileScheme #AI #LLM #LLMs #VibeCoding #AntiAI
Ramin Honary
npub105…puwdv
2026-05-24 12:15:29 UTC
Author Public Key
npub1053m9ka5kf6r3rlcr3kmstaswqk2ewqduv2dvtjtud3p38r0dxvqepuwdvSeen on
wss://relay.ditto.pubPublished at
2026-05-24 12:15:29 UTCEvent JSON
{
"id": "15bee7ed0436a41646ec371bc4870362a9b8f8e4ea9d9de3368ac3d29a9dcd33",
"pubkey": "7d23b2dbb4b274388ff81c6db82fb0702cacb80de314d62e4be362189c6f6998",
"created_at": 1779624929,
"kind": 1,
"tags": [
[
"p",
"8a1816b7a76b97a195e68f60b7dc860669b0b1124953d1118f359d4b4491466f",
"wss://relay.ditto.pub"
],
[
"p",
"b0f2301c8d19d276e62f3917756744066f51844b2da9bd993a622f7a2826265d",
"wss://relay.ditto.pub"
],
[
"t",
"ai"
],
[
"t",
"antiai"
],
[
"t",
"guilescheme"
],
[
"t",
"llm"
],
[
"t",
"llms"
],
[
"t",
"lisp"
],
[
"t",
"lisplang"
],
[
"t",
"schemelang"
],
[
"t",
"vibecoding"
],
[
"t",
"software"
],
[
"t",
"tech"
],
[
"proxy",
"https://fe.disroot.org/objects/7042eafa-62c8-4742-b73a-f6c17956a985",
"activitypub"
],
[
"client",
"Mostr",
"31990:6be38f8c63df7dbf84db7ec4a6e6fbbd8d19dca3b980efad18585c46f04b26f9:mostr",
"wss://relay.ditto.pub"
]
],
"content": "(Reposting a blog post by nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpq3gvpdda8dwt6r90x3ast0hyxqe5mpvgjf9fazyv0xkw5k3y3gehsgcrm88 copy-pasted in full from: this webpage)Can you Lisp without being strapped in to the Torment Nexus Machine?As of 2026-05-18 … sort of.\n\nEvery Lisp, Scheme, and Lisp-adjacent project listed is a non-toy implementation that is at least somewhat active. When I first wrote this article (2026-03-12), most Lisps did not have a policy or even public stance on LLM contributions. In such cases I posted to their bug trackers or discussion lists to ask. Most maintainers kindly responded.\n\nEvery link is either a document or issue stating the project’s LLM policy, or a link to an open issue. Roughly categorized according to how strongly for or against LLM contributions.\n\nIf I’m missing a project that should be listed, lemme know.Strictly Against\nFennel\nSTklos Scheme\nClojure\nECLStrongly Against\nLoko SchemeWeakly Against\nJanet exception given for tests and bug reproductions\nGNU CLISP against on a specific reading of copyright law\nEmacs Lisp temporarily against LLMs, waiting for official policy\nHy maintainer recommends against LLM contributions, no actual policyHesitantly Accepting\nChicken Scheme\nChibi Scheme\nCyclone Scheme\nGambit\nGauche\nGerbil Scheme LLM generated code potentially in source tree\nClasp\nCCLAccepting\nBigloo\nCoalton\nKawa Scheme\nSagittarius Scheme\nJank doesn’t accept external LLM contributions but permits usage by core developers\nRacket LLM generated code in source tree\nSBCL LLM generated code in source tree\nCarp LLM generated code in source treeUnknown\nScheme 48 open issue\nChez Scheme at least one maintainer is against, another skeptical, open issue\nGuile Scheme likely against but nothing officially stated, open issue\nMIT Scheme open issue\nABCL open issue\nLFE open issue\n\n#tech #software #Lisp #LispLang #SchemeLang #SchemeLang #GuileScheme #AI #LLM #LLMs #VibeCoding #AntiAI",
"sig": "1744df0ad2616d893df0bfad06ac6625cef3972b4e26f66ed8a7f6b3ec49cf1c15f435f3b7f1833f0ab9829d0fb1011305544a6b73a218d3d22809b61dac9b5c"
}