Top
Best
New

Posted by staticvar 7 hours ago

Cook: A simple CLI for orchestrating Claude Code(rjcorwin.github.io)
182 points | 42 comments
vadepaysa 4 hours ago|
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.

[0]: https://news.ycombinator.com/item?id=47262711 [1]: https://getcook.dev

catlifeonmars 3 hours ago|
[dead]
maCDzP 1 hour ago||
I dunno. I just let Claude build a python script that calls Claude code though subprocess.run().

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.

jamiemallers 9 minutes ago|
[dead]
rc_kas 6 hours ago||
Can someone explain what this is to my n00b brain. I don't get what claude-cli is missing that this adds in?
beshrkayali 5 hours ago||
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.

My take on a solution for this is https://ossature.dev — .smd spec markdown files + ossature audit / build that gives you DAG orchestration, SHA-traced increments, and tiny focused contexts.

eloisius 4 hours ago|||
Isn’t a repeatable, multi-step workflow exactly what a script or Makefile does?
beshrkayali 2 hours ago||
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.

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.

Feel free to check the example projects on https://github.com/ossature/ossature-examples

wiseowise 1 hour ago||
> Yeah bash scripts start clean but the sprawl kicks in quick as the workflow and project becomes more complex.

Then just use Python.

beshrkayali 1 hour ago||
That’s what Ossature is :)
isodev 4 hours ago||||
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.
Yiin 2 hours ago||
can you elaborate on "easy to read and debug", because in my experience it is anything but
isodev 2 hours ago||
Compared to a random tool someone vibecoded?
je42 4 hours ago|||
Had a quick look. Stumbled upon the markdown format smd.

Was wondering if using front-matter instead of a "custom" encoding for parseble data was considered?

sghiassy 5 hours ago|||
As a prerequisite you’d want to understand the purpose of Ralph Wiggum Loops

But in general this is meta to the CLI agent.

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.

exolab 2 hours ago||
> 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.

Claude already does that if you ask nicely.

transitorykris 6 hours ago||
Maybe not adds in, but wraps around. You could accomplish much of this with fairly simply bash scripts.
esperent 5 hours ago||
You could accomplish all of it with claude -p (headless mode).
transitorykris 5 hours ago|||
Admittedly I might be missing a flag or two with claude, but how are multiple loops and comparisons of solutions done with just headless mode?
loveparade 1 hour ago|||
It's just a prompt.
esperent 4 hours ago|||
Via skills.
brcmthrowaway 5 hours ago|||
Indeed.

Where are people finding time for these sort of projects.

injidup 40 minutes ago||
They bootstrap a workflow with a prompt then build an orchestrator off that then prompt it to be converted to an opencode plugin and then prompt a website to be generated advertising it and then prompt a tool that reviews hacker news feedback and automatically incorporates feedback into next generation of the tool. At the end of the week they go to their manager and complain they are out of tokens for the actual job they are being paid for.
smarx007 37 minutes ago||
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.
sbinnee 5 hours ago||
There is a skill installation option. The skill markdown has 180 lines [1].

My take? I like it. It's concise enough for me to try it out. And I love the webpage.

[1] https://github.com/rjcorwin/cook/blob/main/no-code/SKILL.md

oefrha 3 hours ago|
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 https://github.com/anthropics/claude-code/issues/14321 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.
eknkc 2 hours ago||
At least in codex you can configure agents as you wish: https://developers.openai.com/codex/subagents

Might work out fine on codex.

genthree 52 minutes ago||
Semi-on-topic: Anyone know a way to get a good alternative UI on top of Cursor?

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 half 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)

jemmyw 3 hours ago||
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.
kasperstorgaard 2 hours ago||
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?
hasperdi 2 hours ago|
It's not 3x because of 3 runs; can be more token, can be less.

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.

More comments...