NHacker Next
login
▲Show HN: Druids – Build your own software factorygithub.com
37 points by etherio 1 days ago | 6 comments
Loading comments...
jessmartin 2 hours ago [-]
I love the idea of using a shared event log for coordination. Smart!

I have a Symphony-style[1] factory, which keeps all the context in a single session, but I want to start splitting into stations with separate sessions, and I hadn’t worked out how to do communication between sessions.

[1] https://github.com/openai/symphony

sensarts 3 hours ago [-]
When you have 5 workers + a judge all running in isolated VMs, what is a workflow for tracing a failure? Can I replay the event log locally, or inspect what each agent tried? And also, can agents share intermediate logs, results without going through the event system?
ethros 15 hours ago [-]
I'm going to check this out. I’ve been working on my end-to-end development method and these types of holistic pipelines I think are the future. (or the present!)

I've decided to start with concept capture, which then builds out strategy docs, which feed into specs, etc ... might be time for me to share, but I'm in the process of battle testing myself!

Looking at your post again, I guess I could script a concepting agent to help hone the idea?

einarvollset 37 minutes ago [-]
Very cool!
ipnon 3 hours ago [-]
Interesting. I like it. Now let's say I currently use the OS process as my primitive for agents, just spawning `claude "foo bar baz"`, and orchestrating this way, using perhaps Unix style of files for intermediate data and piping for transformations. What would you are some good use cases of Druid for someone like me?
etherio 2 hours ago [-]
What do you do with those agents? It's useful if you want to iterate on a flow and have more control over the orchestration/environment