Earlier quoted context omitted.
I beg people to learn what symlinks are. The fact that "put @AGENTS.md in there" is a "common workaround" shows why programmers (good ones at least) are not going anywhere soon.
Good programmers know symlinks are not portable
Codex logging bug may write TBs to local SSDs
231–240 of 296 posts
Re: Codex logging bug may write TBs to local SSDs
#232Earlier quoted context omitted.
> same "profit reducing red tape" that civil engineers or similar face. I don't think we should ever head toward licensing/a credential body for software development, but I do think now is a good time to have discussions around liability for defective products. A good start would be to stop allowing companies to disclaim all warranties of fitness for a particular purpose in their EULAs. The joke of Microsoft Copilot…
> I don't think we should ever head toward licensing/a credential body for software development, but I do think now is a good time to have discussions around liability for defective products. Liability is how a credential body would organically grow. It already exists in the security, compliance, and enterprise parts of the software world.
The EU Cyber Resilience Act puts heavy liability on vendors for software vulnerabilities that get exploited, including in open-source components they incorporate. OSS devs are shielded - liability is on the companies who incorporate OSS into commercial stuff.
Re: Codex logging bug may write TBs to local SSDs
#233Earlier quoted context omitted.
> yet that's a human thing. is this joke? Here we are talking about trillon dollar AI companies who claim AI can fix decade old bugs and create new compilers, OSs and what not. Are parallel agents working autonomously to fix issues as well as create new features not allowed at these companies?
Humans still decide what LLMs do in a code base, full stop.
Re: Codex logging bug may write TBs to local SSDs
#234Earlier quoted context omitted.
> yet that's a human thing. is this joke? Here we are talking about trillon dollar AI companies who claim AI can fix decade old bugs and create new compilers, OSs and what not. Are parallel agents working autonomously to fix issues as well as create new features not allowed at these companies?
Humans still decide what LLMs do in a code base, full stop.
Re: Codex logging bug may write TBs to local SSDs
#235Earlier quoted context omitted.
Two trends I see at work: 1) No more human written code in projects, all code must be AI generated. 2) Developers are responsible for all code AI generated. Combine that with fear of losing job and you have no one calling out management bullshit on their face.
I don't see how these things conflict. Nor did I get the point you were making in the sarcastic upstream comment. It is obviously the case that you can both delegate code implementation to AI and also be responsible for it. You are signing off on the code you submit to a project no matter where you got it from nor how it was generated nor who you delegated the task to ("actually my friend wrote it so if it sucks don'…
Re: Codex logging bug may write TBs to local SSDs
#236Codex is one of the most infamous examples of slopware. Just having the window unhidden on my mac will cause it to use 100% of the GPU displaying the spinner message. THE SPINNER MESSAGE CAUSES 100% GPU USAGE ON AN MBP M5!! So any time you're waiting on the model (which is 90% of the time), your fans will be blasting (careful, don't use it on battery). The issue is on github and close to 6 months old. Probably since…
if we are at 10x with AI and near AGI or ASI, then how is it possible that these products (Codex, Claude Code CLI) are still such garbage? shouldn't this "agentic AI revolution" have long solved this already? no way they're over there saying "we are on it plz wait" or that "it's too much effort"?
Re: Codex logging bug may write TBs to local SSDs
#237Earlier quoted context omitted.
Claude is also weird for being the only coding assistant that for some reason doesn't support AGENTS.md. Codex, Amp, Cursor all of them support it and read from it, but not claude which forces it's users to use CLAUDE.md instead. The issue is the higest voted issue on their gitlab repo: https://github.com/anthropics/claude-code/issues/6235
So there's this amazing thing called a symlink
[1]: https://github.com/dutifuldev/claude-md-symlinker#claude-md-...
(I’m not the author obviously)
Re: Codex logging bug may write TBs to local SSDs
#238Earlier quoted context omitted.
Claude is also weird for being the only coding assistant that for some reason doesn't support AGENTS.md. Codex, Amp, Cursor all of them support it and read from it, but not claude which forces it's users to use CLAUDE.md instead. The issue is the higest voted issue on their gitlab repo: https://github.com/anthropics/claude-code/issues/6235
I created a Claude Code plugin to load AGENTS.md. Uses symlinks but it’s better than no support. https://github.com/hexsprite/claude-agents-md
Re: Codex logging bug may write TBs to local SSDs
#239Re: Codex logging bug may write TBs to local SSDs
#240These guys really need to stop polluting the root folder of repo with Claude dot MD and copilot dot MD. Get in a room together and decide on a well known folder structure like docs/llm/*