Fucking tmux is AI slop. #openbsd #tmux #floss https://github.com/tmux/tmux/wiki/Contributing#use-of-ai

EDIT: There has been a fair amount of discussion about if this applies to upstream openBSD, and how the AI code policy is interpreted.

An example can be seen in this commit by the lead developer landing in openBSD attributed to "claude code" https://github.com/openbsd/src/commit/9c2b8e445a0bdfafdd6148b1760f00aa5429627b

Contributing

tmux source code. Contribute to tmux/tmux development by creating an account on GitHub.

GitHub
losing one tool after another

(T_T)

i really hope that slop doesn't make its way into #openbsd's base. lately it feels like i'd have to fork everything i care about...
@hi as I understand it, OpenBSD already said AI code was not acceptable (introducing notion of copyright). The tmux project that accepts AI is the portable one. I don’t expect code from there to go back to OpenBSD src. Unless it is something trivial and acceptable from their POV.
@joel @hi Here is a commit crediting claude code landing in the openbsd tree upstream. https://github.com/openbsd/src/commit/9c2b8e445a0bdfafdd6148b1760f00aa5429627b
Add support for applications to use synchronized output mode (DECSET Β· openbsd/src@9c2b8e4

2026) to prevent screen tearing during rapid updates. When an application sends SM ?2026, tmux buffers output until RM ?2026 is received or a 1-second timeout expires. From Chris Lloyd with the as...

GitHub

@trashheap πŸ€·β€β™‚οΈ maybe it was something identified as acceptable. I only have uneducated user opinion.

@hi