Cook: A simple CLI for orchestrating Claude Code
32 points
1 hour ago
| 2 comments
| rjcorwin.github.io
| HN
rc_kas
40 minutes ago
[-]
Can someone explain what this is to my n00b brain. I don't get what claude-cli is missing that this adds in?
reply
beshrkayali
8 minutes 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.

reply
transitorykris
26 minutes ago
[-]
Maybe not adds in, but wraps around. You could accomplish much of this with fairly simply bash scripts.
reply
esperent
13 minutes ago
[-]
You could accomplish all of it with claude -p (headless mode).
reply
rafaamaral
42 minutes ago
[-]
Nice approach to the orchestration problem. The recipe-based pattern is clean — define the workflow declaratively, let the CLI handle the execution.

One thing I've been thinking about with tools like this: as you chain more Claude Code calls, the cost compounds fast. A single "cook" run with 5-6 steps could easily burn through $10-15 in API credits if you're not careful about which model handles which step.

Has anyone experimented with routing different recipe steps to different model tiers? E.g., using Haiku for boilerplate generation and Opus only for the steps that actually need deep reasoning? That's where the real savings are in multi-agent orchestration.

reply
Yiin
31 minutes ago
[-]
just use 200usd plan, I forgot what limits are.
reply
croes
21 minutes ago
[-]
You'll remember it soon
reply
weird-eye-issue
6 minutes ago
[-]
Do you often hit the limits recently on the $200 plan? I don't even come close
reply