Loeffelmann

I also love how with the right system prompt they can pull in tooling for what they currently need via a nix shell

How do you prevent prompt injections?

This is strawmaning the article

Why?

I think I was sold the full agentic coding hype all over the internet. You give it a try and it does write a feature really fast. Impressed you test the boundaries more and more and before you know it this has become your new workflow. Breaking free of this again is harder than you'd think even when you do realize what a mess is generated in the process.

> locally coherent but structurally incoherent

Perfectly summarizes what I hate about AI code. The diff looks fine but if you take a step back its an absolute mess. I mean have you looked at the Claude Code or Openclaw codebases? that is the result of full on vibecoded. A bloated unattainable mess that no one understands.

If you ever work with LLMs you know that they quite frequently give up.

Sometimes it's a

    // TODO: implement logic

or a

"this feature would require extensive logic and changes to the existing codebase".

Sometimes they just declare their work done. Ignoring failing tests and builds.

You can nudge them to keep going but I often feel like, when they behave like this, they are at their limit of what they can achieve.

An AI version of ls and fzf bringing your file system to the AI age

> you can always do C-x C-e in bash/zsh (M-v in Fish).

Thanks I didn't know!

Lol a formatting error in a change log breaking the entire thing

You can use subscriptions.

I like it but I am not too deep into the whole agentic coding business.

Why do all these AI generated readmes have a directory structure sections it's so redundant because you know I could just run tree

It's mainly about showing how low the odds actually are. I think everyone understands they are low but it's ridiculous how low exactly.