staticvar

6 ms·

1.
What's on the Box vs. What's in the Box(rjcorwin.github.io)
1 points by staticvar 4d ago|0 comments
2.
by staticvar 2mo ago
I'm not sure that AI helps us with that last 1%. Just the 99% which is why, instead of having a backlog of 0% projects, we have a backlog of 99% projects. My hope is that we're more effective prioritizing a backlog of 99% projects
3.
by staticvar 3mo ago
Maybe revenge, but it's a common play to fire a shot across the bow to create leverage in other areas.
4.
by staticvar 4mo ago
Totally fair argument to make right now. But so funny how this is the opposite movement of "Let me Google that for you".
5.
by staticvar 6mo ago
> We told Claude Code to block npx using its own denylist. The agent found another way to run it and copied the binary to a new path using /proc/self/root to bypass the deny pattern. When Anthropic's sandbox caught th
6.
by staticvar 6mo ago
Too many cooks? >.<
7.
by staticvar 6mo ago
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
8.
by staticvar 6mo ago
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
9.
by staticvar 6mo ago
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
10.
by staticvar 6mo ago
Done! @let-it-cook/cli@5.1.0 is out. This works when running loops, but even when you just run `cook "do something"` which itself is not a loop, just a call to your agent.
11.
by staticvar 6mo ago
Exactly! That's my vibe. https://rjcorwin.github.io
12.
by staticvar 6mo ago
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 mo
13.
by staticvar 6mo ago
I would be interested in which stories you are thinking of. Stories of Claude breaking out of the restrictions set in its sandbox or stories of people not configuring Claude's sandbox correctly?
14.
by staticvar 6mo ago
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).
15.
by staticvar 6mo ago
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.
16.
by staticvar 6mo ago
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 a
17.
by staticvar 6mo ago
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.
18.
by staticvar 6mo ago
To a certain extent, yes it does! For my cases, I'm often running 3 parallel implementations that get 10 to 20 iterations deep, and then Claude has to sort out the pros and cons of the options and also take the best bits of each. Easy
19.
by staticvar 6mo ago
By default it's locked down to the permissions you have granted in your Claude config. If you use the docker sandbox mode, then you can really let it fly as it can issue more commands in a safer environment.
20.
by staticvar 6mo ago
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 us
21.
by staticvar 6mo ago
Ah sorry about that. I have weird tastes in design. The README.md is less detailed but covers the basics: https://github.com/rjcorwin/cook/
22.
by staticvar 6mo ago
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 co
23.
by staticvar 6mo ago
This is a fantastic idea and I'll add it!
24.
by staticvar 6mo ago
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 whethe
25.
by staticvar 6mo ago
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 tha
26.
by staticvar 6mo ago
Oh haha, small world! Maybe I should add cook (agent) support for cook (orchestration) and then we'll have cook manage subagents via cook!
27.
Cook: A simple CLI for orchestrating Claude Code(rjcorwin.github.io)
307 points by staticvar 6mo ago|97 comments
28.
Show HN: Automate Claude in a work->review loop with cook(github.com)
2 points by staticvar 6mo ago|0 comments
29.
Watch two AI robots roast me while I play video games(twitch.tv)
2 points by staticvar 1y ago|2 comments
30.
by staticvar 1y ago
Adventures on the Sea of Thieves with Vibe coding: I created a Mystery Science Theater 3000 like experience where I share my game window and two AI robots roast me.

More ›