Maybe revenge, but it's a common play to fire a shot across the bow to create leverage in other areas.

Totally fair argument to make right now. But so funny how this is the opposite movement of "Let me Google that for you".

Opposite in which sense?

I guess this is all about rudeness from being too lazy.

My understanding is 'lmgtfy' is a response to a lazy request for help. Someone's asking for help, but it seems like they could have helped themselves if they just searched Google. -- The corrective action is: it would have been better if the person asking the question had demonstrated thought/effort about their response.

Whereas "don't paste AI slop", merely copy-pasting an LLM's output is lazy. (The asker could have asked an LLM). -- The corrective action is: the response should show more thought/effort.

Yes, plz don't trust it, always review! The idea is that one prompt in Claude Code got you 80% of the way there, but with some automated review/iterate, it gets you 95% of the way there. It's not worth your time to review the 80% done version when you could be reviewing the 95% done version.

Also on that point about keeping humans in the loop on decisions, I've found following the Research-Plan-Implement process where we humans review at each of those stages, to be really helpful. This doc describes the skill I use with my agents so they keep me looped in: https://gist.github.com/rjcorwin/296885590dc8a4ebc64e70879dc...

Then I use cook to iterate and explore during the AI led parts.

Dagu.sh, using yaml files to describe the flow, looks like a nice step up in sophistication from the cook approach that's just trying to make it easy to issue directly from the command line.

My 2 cents on the dagu.sh website, it should lead with the demo section (https://docs.dagu.sh/overview/#demo). That helped me connect what it was and how I might use it.

Exactly! That's my vibe. https://rjcorwin.github.io

Good to hear that you're having luck with small models. Note that cook exposes a --model param, also workflow specific model params (--model-work, --model-review, etc) so you can have a smaller model implementing a plan and a larger model reviewing the implementation.

That's right. However if you use the v3 operator, you get three parallel versions being built, and then combined depending on which resolver you use (pick, merge, and compare).

Hey scrappyejoe, way looks pretty cool. The goal of cook is to be unopinionated, exposing primitives for the shape of workflows as opposed to defining what happens in those workflows. Cook is something that way could use under the hood.

Cool, I'm already digging into your stuff, thanks for posting it.

Your getcook.dev tool has a nice form factor for a coding agent, keeping users out of a TUI, instead staying on the command line. An option I'd be interested in exploring is one that wraps `claude -p`, reads the jsonl of that session and prints it out nicely like you are doing with getcook.dev.

Haha, not far off. Only difference is I'm not spending my tokens at work. I use this on a side project video game that I'm developing.