Rendered at 15:09:54 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
jarodrh 20 hours ago [-]
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)?
midtake 3 days ago [-]
Name collision with Foreman, the provisioning/patching tool.
That was actually one of my naming inspirations, the george foreman grill is a s tier invention
TurdF3rguson 2 days ago [-]
Lol. It's an objectively bad grill.
GuestFAUniverse 3 days ago [-]
Slop(py) coders don't care.
I would vote for the alternative:
"Sloppy McSlopGate"
AndrewLiu96 3 days ago [-]
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 :)
dilushin 2 days ago [-]
I have something simmilar brewed in my multi-agent system, showing and saving cost data on every agent flow run.
AndrewLiu96 2 days ago [-]
That's awesome! I'd love to check it out and give it a try
dilushin 8 hours ago [-]
It is in my private repo, let see if I can OSS this part )
bigtechisajoke 3 days ago [-]
Foreman is too well known imo
AndrewLiu96 2 days ago [-]
Noted!
jsabess24 3 days ago [-]
Nice
AndrewLiu96 2 days ago [-]
Thanks for checking it out!
anirudhak47 2 days ago [-]
how does it compare to sakana?
AndrewLiu96 2 days ago [-]
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.
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)?
https://en.wikipedia.org/wiki/Foreman_(software)
I would vote for the alternative: "Sloppy McSlopGate"