cool, so there's a whole new github dork people can do: claude chatlogs.

[viss@mastodon.social]

cool, so there's a whole new github dork people can do: claude chatlogs.

they live in .claude/logs/ and are full text records of peoples entire conversations with claude

and they're ending up in public on github because i guess people arent adding them to .gitignore

happy monday! ai is going great!

[schrotthaufen@mastodon.social]

@Viss At some point, `git init` needs to be patched to pre-populate the .gitignore with
```
.*
!.𝚐𝚒𝚝𝚒𝚐𝚗𝚘𝚛𝚎
```
just so people don’t shoot themselves in the balls…

[nf3xn@mastodon.social]

@Viss omg the yummy secrets

[depereo@mastodon.social]

@schrotthaufen a really good suggestion, I will set that up for myself at least.

[schrotthaufen@mastodon.social]

@crazyeddie @Viss Lol no. Kinda insulting to suggest I’d even use AI. And no, it would not break stuff. It does however force you to maintain your .gitignore. Also, I just tried it with submodules, and git does indeed just stage .gitmodules, despite the `.*`. Additionally, you can always use `git add -f` to stage files, regardless of of .gitignore. Next time, maybe try it out before posting something condescending. Kthxbai.

[viss@mastodon.social]

oops, found creds.

[hrbrmstr@mastodon.social]

@Viss pretty sure that's a legacy claude code thing (don't get me wrong, still bad/dumb).

I've not seen Claude CLI (it's not really just "code" anymore) put anything except settings (on its own) in the project-local .claude. They keep all session stuff in ~/.claude

I suspect it's configurable tho, and some CLAUDE.md generators might cause logs to be shunted to the project level

[viss@mastodon.social]

@hrbrmstr ive had to manually make those files to use a claude api key, depending on where you launch it from itll want it in various places, i totally have .claude dirs outside of ~

[hrbrmstr@mastodon.social]

@Viss oh def. but all the logs from any sessions i have are central to ~/.claude and i didn't config it that way.

it's cool that we have these super smart "AI”s that seem to think the OWASP security risks corpus they were trained on were TODOs rather than "don’t”s.

[viss@mastodon.social]

@hrbrmstr they werent trained to care about security :D