By the way, if you go to https://github.com/claude and "block this user", every Github repo you visit containing code written by Claude will actually have a warning sigil
-
@mcc oh no
-
@mcc oh no
-
-
@emjonaitis The .claude directory is, *as far as I know* (again, this is partially assumptions) configuration for claude to help it work with the codebase. Anyone who adds such a directory is essentially *inviting* claude commits. However technically they might not be using it to create code, they technically could be using it to answer questions about the codebase. Technically. One assumes this results in as much global warming as using it to write code however.
@mcc @emjonaitis unless they are using it to poison the agents in question. I'm not poisoning a .claude directiory but I am poisoning a .github/copilot-instructions.md (we actually started getting some copilot-agent spam)
I do think I'd be a lot more hesitant to put an anti-agents node in the root directory since it would be more likely to be seen but not read, but also my software isn't a piece of infrastructure where people are looking at using it in that way. -
By the way, if you go to https://github.com/claude and "block this user", every Github repo you visit containing code written by Claude will actually have a warning sigil
CF
@mcc what is Claude, some bullshit generator? if so, then it's a not bad idea to block them all, of all kinds. but that works only if you logged in to Github, and this is a spyware of a kind. -
@mcc @emjonaitis unless they are using it to poison the agents in question. I'm not poisoning a .claude directiory but I am poisoning a .github/copilot-instructions.md (we actually started getting some copilot-agent spam)
I do think I'd be a lot more hesitant to put an anti-agents node in the root directory since it would be more likely to be seen but not read, but also my software isn't a piece of infrastructure where people are looking at using it in that way.@kevingranade @emjonaitis yes, that's a frustrating problem, that the directory is slightly more likely to ward off anti-ai folks than it is "code assistants". one thing someone suggested is that if the commit message for the agents file says "block agents" or something the humans might notice this, but that assumes they're using something like github (which i think hides dotfiles anyway) and not just noticing a directory on their computer
-
@kevingranade @emjonaitis yes, that's a frustrating problem, that the directory is slightly more likely to ward off anti-ai folks than it is "code assistants". one thing someone suggested is that if the commit message for the agents file says "block agents" or something the humans might notice this, but that assumes they're using something like github (which i think hides dotfiles anyway) and not just noticing a directory on their computer
@mcc @emjonaitis maybe touch files that will lexicographically sort next to it with names like .claude_DIRECTORY_IS_A_POISON_PILL
-
@mcc @emjonaitis maybe touch files that will lexicographically sort next to it with names like .claude_DIRECTORY_IS_A_POISON_PILL
@kevingranade @emjonaitis Part of the problem is I do not know for a fact whether any one mitigation will be accepted by a "code assistant" without installing and activating a "code assistant", a thing I will not do. So like if it turns out it checks in .claude but not in .claude_poison, then maybe creating the .claude_poison directory creates the inconvenience of directory junk without having the effect I want.
-
@kevingranade @emjonaitis Part of the problem is I do not know for a fact whether any one mitigation will be accepted by a "code assistant" without installing and activating a "code assistant", a thing I will not do. So like if it turns out it checks in .claude but not in .claude_poison, then maybe creating the .claude_poison directory creates the inconvenience of directory junk without having the effect I want.
@mcc @emjonaitis yea, in this specific case it's built into github so you can't *not* have it "installed", but that is a problem.
When we were adding it some people were proposing we add a bunch of different agent files, but when asked weren't actually testing them so what's the point.
Best answer I can come up with is someone takes it on as a infosec-style project and publishes a repo of agent poison pills you can simply incorporate.
-
@lanodan @nick @mcc gdb will most likely also adopting the same wording as binutils due to the overlap usage of bfd.
As far as mesa and other gui runtimes stuff, that needs to be redone. Gcc or something more. Right now from what I remember Mesa depends on older versions of llvm due to api instability too.
With respect to clang-format, there is some work going on dealing with gcc a68 which might be reused with c/c++ frontends too
-
@lanodan @nick @mcc gdb will most likely also adopting the same wording as binutils due to the overlap usage of bfd.
As far as mesa and other gui runtimes stuff, that needs to be redone. Gcc or something more. Right now from what I remember Mesa depends on older versions of llvm due to api instability too.
With respect to clang-format, there is some work going on dealing with gcc a68 which might be reused with c/c++ frontends too
-
-
@porglezomp @lanodan @nick a nice thing about the block warning is assuming microsoft did not code it in an absurd way, the block warning surely applies only to commits in the past of the current branch.
this would be improved if github had not exempted the copilot bot from blocks. they did exempt it from blocks, and if you look in the github feedback forum there's a feature request from me for the day they did it asking them to not-exempt it. oh well…
-
@mcc oh no
-
@porglezomp @lanodan @nick a nice thing about the block warning is assuming microsoft did not code it in an absurd way, the block warning surely applies only to commits in the past of the current branch.
this would be improved if github had not exempted the copilot bot from blocks. they did exempt it from blocks, and if you look in the github feedback forum there's a feature request from me for the day they did it asking them to not-exempt it. oh well…
@mcc @porglezomp @nick Sadly it doesn't shows up in https://github.com/llvm/llvm-project/commits?author=claude
Might be due to Co-Authored-By kind of stuff. -
@mcc oh no
@nick @mcc thankfully the swift project's fork of LLVM is clean for now:
(or at least, it hasn't been touched by claude yet)
https://github.com/swiftlang/llvm-project -
@nick @mcc thankfully the swift project's fork of LLVM is clean for now:
(or at least, it hasn't been touched by claude yet)
https://github.com/swiftlang/llvm-project@JamesWidman @nick apple's absurd litigousness pays off possibly for possibly the first time I can think of
-
By the way, if you go to https://github.com/claude and "block this user", every Github repo you visit containing code written by Claude will actually have a warning sigil
CF
@mcc As the old meme goes.. oh no.
-
@JamesWidman @nick apple's absurd litigousness pays off possibly for possibly the first time I can think of
-
@lanodan @nick @mcc that's not true.. they can and historically have used GCC, just preferred to migrate when they could.
freebsd changed from gcc to clang as default for main architectures in 2012 but didn't stop shopping gcc until 2020.
openbsd moved to clang in 2018-2020
nerbsd still uses gcc as default
