Live data from Hacker News

Show HN: Sim Studio – Open-Source Agent Workflow GUI

github.com

31–40 of 63 posts

Re: Show HN: Sim Studio – Open-Source Agent Workflow GUI

#31

Youtube demo looks intriguing, I'm self-hosting n8n for exact this purpose with a home run LLM machine in a local k8s cluster (lol) but out of the box I can tell your tool surpasses AI integrations and workflow in n8n. Quick glance at GitHub suggests that GitHub package for the Docker image is missing, let me know if you need help with that — happy to contribute!

It's funny, but I solved a similar problem myself, but instead of n8n I came to write my own solution. I even noticed this post thanks to automation and llm. Likewise, I'll be glad to help!

Re: Show HN: Sim Studio – Open-Source Agent Workflow GUI

#32
post #29

Congratulations, Emir and Waleed! This is exactly the kind of OSS tooling I’ve been waiting for. I’ve spent countless hours wrestling with multi-step agent workflows hidden inside monolithic prompts, and every iteration felt like shooting in the dark. Having a drag-and-drop, executable graph with built-in branching, loops, and observability is a game-changer.

thank you! check out the mem0 integration and let us know if you like the form factor. excited for you to check out the platform and let us know if it helps you wrangle those multi-step agent workflows.

Re: Show HN: Sim Studio – Open-Source Agent Workflow GUI

#36

Congrats on the launch! Looking forward to playing with it. Do you mind elaborating on what differentiates Sim Studio from n8n, Flowise, RAGFlow and other open source flow based AI automation platforms?

Thanks! The main difference between Sim Studio and other open-source AI agent workflow builders is the level of abstraction used when creating agents. For instance, n8n has a "memory" parameter, which is not an inherent parameter of LLMs. You can inject your agent's memories into the agent message history (or system prompt) - which is the most common scenario - but we give you control over that. We want to provide vi…

This sounds like execution/variable resolution scopes in programming languages. I wonder if there are ideas from programming languages you could pick up and use?

Re: Show HN: Sim Studio – Open-Source Agent Workflow GUI

#37
post #36

Earlier quoted context omitted.

Thanks! The main difference between Sim Studio and other open-source AI agent workflow builders is the level of abstraction used when creating agents. For instance, n8n has a "memory" parameter, which is not an inherent parameter of LLMs. You can inject your agent's memories into the agent message history (or system prompt) - which is the most common scenario - but we give you control over that. We want to provide vi…

This sounds like execution/variable resolution scopes in programming languages. I wonder if there are ideas from programming languages you could pick up and use?

Yes exactly! A lot of our platform was inspired by programming languages - for loops, for each loops, custom variables, and environment variables in settings. If you have any more concepts, we'd love to hear them!

Re: Show HN: Sim Studio – Open-Source Agent Workflow GUI

#38

It looks very nice. What happens when a flow that takes 1 minute to complete is triggered by three different Slack messages from different users one second apart. Are flow executions queued or executed in parallel? Is it configurable?

thanks! this would actually trigger three separate workflow executions, and the messages would be processed in parallel by each execution. by default, within the workflow all the blocks execute once their dependencies are resolved, and for the workflow itself they are also executed in parallel. if three messages are sent by the same user, it is also executed as separate workflow executions. curious to hear about your usecase though, are you looking to process the messages in batches?

Re: Show HN: Sim Studio – Open-Source Agent Workflow GUI

#39
post #35

I checked it out and it’s quite polished for a workflow builder. But I struggled for it to handle lists of content well. But I saw that’s already an ongoing feature request.

Thank you! Yes - we are adding variable resolution to the for each input. Let us know if there's anything else you'd like to see!
Post reply on HN