Live data from Hacker News

Cord: Coordinating Trees of AI Agents

june.kim

81–90 of 93 posts

Re: Cord: Coordinating Trees of AI Agents

#81

[dead]

The article addresses this: > This made sense when agents were unreliable. You’d never let GPT-3 decide how to decompose a project. But current models are good at planning. They break problems into subproblems naturally. They understand dependencies. They know when a task is too big for one pass. > So why are we still hardcoding the decomposition?

[dead]

Re: Cord: Coordinating Trees of AI Agents

#83
post #75

Earlier quoted context omitted.

The criticism about the labeling is valid and I oversold. For clarity, this is what the agent sees: `spawn`: "Create a spawned child node under your node." `fork`: "Create a forked child node (inherits parent context) under your node." The novelty is less about the distinction between the two, it's the tree generation. I would have served you better, if I just left out the parts that aren't critical to the novelty. T…

And thanks for taking the criticism. In all honesty, "would have written it myself but I was too eager to get it out the door" doesn't really make sense to me. You're acknowledging that you took a shortcut to get it out the door (blog post as tech debt is a new one!) - does that mean you'd like to write something up yourself eventually? I hope so, and would like to read it. In particular, since this is presented as r…

It is my pleasure to write for you.

https://www.june.kim/cord-human

Re: Cord: Coordinating Trees of AI Agents

#87
post #75

Earlier quoted context omitted.

And thanks for taking the criticism. In all honesty, "would have written it myself but I was too eager to get it out the door" doesn't really make sense to me. You're acknowledging that you took a shortcut to get it out the door (blog post as tech debt is a new one!) - does that mean you'd like to write something up yourself eventually? I hope so, and would like to read it. In particular, since this is presented as r…

It is my pleasure to write for you. https://www.june.kim/cord-human

I enjoyed this! Thank you for taking the time to write it. I like it because I identify with your experiences way more than I do with the standard AI braggy boilerplate. Cheers.

And I deserve and accept the gentle snark at the beginning. I will be sure to let you know when I post something, I'll take your notes :)

Re: Cord: Coordinating Trees of AI Agents

#89
post #18

Claude basically does this now (including deciding when to use subagents, tools, and agent teams). I built a similar thing a month ago and saw the writing on the wall.

I agree, Claude does spawn subagents but subagents don't spawn sub-subagents.

[dead]

Re: Cord: Coordinating Trees of AI Agents

#90

Every time i see some new orchestrator framework worth more than a few hundred loc i cringe so hard. Reddit is flooded with them on the daily and HN has them on the front page occasionally. My current setup is this; - `tmux-bash` / `tmux-coding-agent` - `tmux-send` / `tmux-capture` - `semaphore_wait` The other tools all create lockfiles and semaphore_wait is a small inotify wrapper. They're all you need for 3 levels…

[dead]
Post reply on HN