I did a Show HN[0] a few days back with my CLI agent called cook[1] and for a moment I was ecstatic my tool made it to the front page. haha.<p>[0]: <a href="https://news.ycombinator.com/item?id=47262711">https://news.ycombinator.com/item?id=47262711</a>
[1]: <a href="https://getcook.dev" rel="nofollow">https://getcook.dev</a>
I dunno. I just let Claude build a python script that calls Claude code though subprocess.run().<p>I recently made a sort of Autoresearch with that approach. The script calls Claude Code to create a hyphotesis, then code based on that, evaluate- rinse and repeat. I am still trying to figure out if I am actually on to something or just burning tokens. Jury is still out.
I think you're onto something, but I would add that it's sort of like a live REPL that has an integrated agent but with extra steps.<p>I haven't used python much but I wouldn't be surprised if you can set up a sufficiently powerful REPL with it. I know Julia can do it very well and it's a very similar language. Obviously there are powerful Lisps that do this very well as well.
That's totally a valid approach! Especially for a very specific workflow you are looking for. For the cases I cover in cook, I had done those patterns enough times that I figured it was time to build a tool/skill for Claude so that I didn't have to explain it as much and also not have to wait for claude to code it up, and possibly interpret me wrong. Now ask claude to "/cook race 3 of foo plan with review, pick the best" and it knows what to do.
[dead]
Can someone explain what this is to my n00b brain. I don't get what claude-cli is missing that this adds in?
IMO the raw Claude CLI is great for one-off interactive sessions, but as soon as you want repeatable multi-step workflows you’re either copy-pasting prompts forever or hacking your own solution manually. That’s exactly the gap these tools fill.<p>My take on a solution for this is <a href="https://ossature.dev" rel="nofollow">https://ossature.dev</a> — .smd spec markdown files + ossature audit / build that gives you DAG orchestration, SHA-traced increments, and tiny focused contexts.
Isn’t a repeatable, multi-step workflow exactly what a script or Makefile does?
Yeah bash scripts start clean but the sprawl kicks in quick as the workflow and project becomes more complex. Prompts get copied, deps turn manual, and maintenance of your workflow itself becomes the chore.<p>Ossature swaps that for structured SMDs and optional AMDs. Multiple specs build a clean DAG that drops into an editable plan.toml so everything stays traceable without the mess.<p>Feel free to check the example projects on <a href="https://github.com/ossature/ossature-examples" rel="nofollow">https://github.com/ossature/ossature-examples</a>
I use bash scripts. Both Claude and Vibe support all kinds of arguments if you need a prompt to “become a task”. Bash is also deterministic and easy to read and debug.
Had a quick look. Stumbled upon the markdown format smd.<p>Was wondering if using front-matter instead of a "custom" encoding for parseble data was considered?
As a prerequisite you’d want to understand the purpose of Ralph Wiggum Loops<p>But in general this is meta to the CLI agent.<p>So if you were to use the CLI to perform a review of some code. This tool would allow you to loop the output of the code review 5 times onto itself.
Maybe not adds in, but wraps around. You could accomplish much of this with fairly simply bash scripts.
There is a skill installation option. The skill markdown has 180 lines [1].<p>My take? I like it. It's concise enough for me to try it out. And I love the webpage.<p>[1] <a href="https://github.com/rjcorwin/cook/blob/main/no-code/SKILL.md" rel="nofollow">https://github.com/rjcorwin/cook/blob/main/no-code/SKILL.md</a>
Nice! You found the no-code option that just has the outer agent perform the duties of the workflows that cook describes. It's a bit experimental (the whole thing is really), but it would be nice to get some folks impressions of whether this works well as a pure skill or if y'all find the deterministic nature of the cook script improves reliability.
Given that subagents have different thinking/effort behavior from the main agent and very limited control on that front (I’m not completely sure about this but see <a href="https://github.com/anthropics/claude-code/issues/14321" rel="nofollow">https://github.com/anthropics/claude-code/issues/14321</a> and I’ve also noticed very different behavior when the same prompt is used in the main agent or passed to a subagent), I’m not sure this skill will be the same.
A noob question: is there a tool that automatically instructs Claude Code to "continue" when the token quota is reset after 5h? I am interested in that more than some rather fancy loops.
Looks pretty nice. I think a lot of devs have been making similar tools, I've written my own thing that does a work review loop. I like the interface you've made. I'll probably give it a go, but I'm also reluctant to relinquish the control I have when it's my own code doing orchestration.
Oh ya, lots of tools out there orchestrating these days, and just writing a script is a valid option. On the control bit, note that if you `cook init` in your project, it generates a COOK.md that lets you template the meta prompt. Claude could probably take a look at how you've been doing it and port it over to COOK.md so it's similar to the prompts you've been using.
How heavy on tokens is this? I don't use these style workflows and am fairly new to claude code, so I assume it's better than 3x tokens when doing 3 passes?
It's not 3x because of 3 runs; can be more token, can be less.<p>The way of thinking it is, telling Claude to tackle the problem 3 times, each time it may or may not use different approach, fix or improve on things it did previously.
Semi-on-topic: Anyone know a way to get a good alternative UI on top of Cursor?<p>My company’s tracking how much we use the damn thing (its autocomplete is literally less-useful than standard VSCode, only time it’s consistently good is when it sees me do one thing to a line, sees repeated similar lines after that, and suggests I do it on the next one too, one at a time, and that’s only useful to me because I’ve never actually bothered to learn how to properly use a text editor) so I can’t avoid it, but even on codebases in the hundreds of lines it’s OOM killing things on my 16GB laptop (it, plus goddamn Teams, were eating <i>half</i> the memory by themselves the other day… with Cursor sitting at almost 6GB alone. JFC. On the plus side if this is what software from a company that should be full of experts at using these things looks like, guess our jobs are safe from them… though not from recession and ZIRP unwinding)
Dull colors and a display font used for copy makes this website incredibly unpleasant to read.
How does this handle when Claude needs user input? To choose an option, grant tool permission, clarify questions…
On asking for user input during implementation, it's best to use this when you have a plan sufficiently written up that you can point it to. To prep that plan, you can also use cook to iterate on the plan for you. Having Claude Code use `/cook` directly is nice because it watches what the subagents are up to and can speak for them, although Claude can't speak to the subagents running through cook.<p>On permissions, by default, when it runs instances of Claude they will inherit your Claude's permissions. So if there is no permission to `rm -rf /`, Claude will just get denied and move on. Using the docker sandbox option (see bottom of page), then it runs inside that `--dangerously-skip-permissions` and get more stuff done (my preferred option). The hard part about that is it means you need to set up the Docker sandbox with any dependencies your project needs. Run `cook init` and edit the `.cook/Dockerfile` to set those up.
If you impl this as a backend and connect to Telegram bots, agents can just do `$ ask "Should I do this?"` for agent→human and `$ alert "this thing blocked me"` for coder→planner. That's what I'm actually doing — I have 1 manager + 3 designers + 1 researcher + 2 debugger + 1 communicator + any number of temporal coders/reviewers in my setup, all connected to taskwarrior for task-driven-dev
It seems to be in the spirit of automated vibecoding. I assume it skips all permission checks.
can we integrate it with Devin too? seems like it doable
claude> "We want to add a title section that shows what page we are currently on, use cook to manage the development process"<p>* coolers whirring, gpus on fire, tokens flying, investors happy, developer goes for 6th break of the day
[dead]
[dead]
[dead]
[dead]
[dead]
[dead]
[dead]
[dead]
[dead]
[flagged]
If this was human written sarcasm, bravo.
just use 200usd plan, I forgot what limits are.
Do you hit the limit pretty quickly on the Pro plan these days?
Im thinking about subscribing for video editing, but Im still not sure.
You'll remember it soon
[flagged]