18 comments

[ 3.9 ms ] story [ 44.2 ms ] thread
Name collision with Foreman, the provisioning/patching tool.

https://en.wikipedia.org/wiki/Foreman_(software)

Slop(py) coders don't care.

I would vote for the alternative: "Sloppy McSlopGate"

Could you point out where you see the slop in the codebase? I'm more than happy to address it and make the tool better and more useful :)
Not to mention the George Foreman grill
That was actually one of my naming inspirations, the george foreman grill is a s tier invention
I have something simmilar brewed in my multi-agent system, showing and saving cost data on every agent flow run.
That's awesome! I'd love to check it out and give it a try
It is in my private repo, let see if I can OSS this part )
how does it compare to sakana?
I assume you're referencing Sakana Fugu? Similar in the sense that there's multiple models involved, but from what I understand Fugu is kind of a black box in terms of what model is used for what. This project is more deterministic, you can pick and choose which model to assign/use for certain tasks, plus this project is open source which Fugu isn't.
Interesting project. Most of what I read appears to deal well with a linear agent session.

How does it handle concurrent agent/subagent spawning?

Do they fall under the same sessionId (where they're potentially fighting over the warm route breaking it with every task-type change) or get their own individual sessionIds (where you must rewrite the shared prefix for each agent)?