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?
Show HN: Sim Studio – Open-Source Agent Workflow GUI
11–20 of 63 posts
Re: Show HN: Sim Studio – Open-Source Agent Workflow GUI
#12Hi y'all. Love the idea and congratulations on your launch. I've used [n8n](https://github.com/n8n-io/n8n) for similar use cases in the past. Any differences in Sim Studio that you'd like to call out?
Re: Show HN: Sim Studio – Open-Source Agent Workflow GUI
#13Congrats 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 visibility, so everything that's exposed on the workflow canvas is exactly what's being executed in the background. Also, we think it's faster and more intuitive to get your workflow up and running in Sim Studio. I'd love your feedback, though! What do you think?
Re: Show HN: Sim Studio – Open-Source Agent Workflow GUI
#14> Building reliable, multi-step agent systems with current frameworks often gets complicated fast.
In my experience so far it's not just complicated, but effectively impossible. I struggle to get a single agent to reliably & consistently use tools, and adding n+1 agents is a error multiplier.
Re: Show HN: Sim Studio – Open-Source Agent Workflow GUI
#15[flagged]
Re: Show HN: Sim Studio – Open-Source Agent Workflow GUI
#16> Building reliable, multi-step agent systems with current frameworks often gets complicated fast. In my experience so far it's not just complicated, but effectively impossible. I struggle to get a single agent to reliably & consistently use tools, and adding n+1 agents is a error multiplier.
on our platform (for the providers that allow granular tool use control), you can actually 'force' certain tool calls and have the agent dynamically select others. this was a painpoint that we faced ourselves and were confused why any frameworks didn't allow granular tool use control if the provider allows it. try it out and let us know what you think
Re: Show HN: Sim Studio – Open-Source Agent Workflow GUI
#17Hi y'all. Love the idea and congratulations on your launch. I've used [n8n]( https://github.com/n8n-io/n8n ) for similar use cases in the past. Any differences in Sim Studio that you'd like to call out?
Thank you! n8n has done really well over the last few years to simplify the workflow building process. I responded to this in a previous comment, but we believe the agent building process should be more open, meaning fewer abstractions between the interface and the model provider. We want our platform to be as lightweight as possible.
How this translates in the application is through features like allowing for custom tool calling with code execution, JSON schema input for response format, etc. I'd love to hear your thoughts using Sim Studio - let us know how we compare to the other workflow builders!
Re: Show HN: Sim Studio – Open-Source Agent Workflow GUI
#18I'm sure that the complex logic and state management were not trivial to implement, but the link said GUI so I wanted to see some screenshots, but all I saw were two very dim simple forms. This space is REALLY struggling to graduate from Gradio-like design sensibilities. That being said, I'm looking forward to playing with this, congrats on the launch!
The video linked in the post description shows everything pretty clearly, here: https://www.youtube.com/watch?v=JlCktXTY8sE
Re: Show HN: Sim Studio – Open-Source Agent Workflow GUI
#19This could play very well with building a managed agentic system around computer-use for RPA. Great stuff!
we have support for browser agents (browser-use and stagehand), but running this locally with computer use agents would change the game. will explore :)
Can the browser agents use my already running browser? It would be nice to automate some light workflows in platforms that require login, especially the ones that make it hard to use headless browsers
Right now my solution is to build extensions that I can manually start on my browser. But using extensions to gather and export data + maintaining them is a bit of a pain
Re: Show HN: Sim Studio – Open-Source Agent Workflow GUI
#20Congrats on the launch the tool looks phenomenal.
I’m conflicted because n8n does feel like the right level of abstraction but the UI and dated JS runtime environment are horrible. I don’t really want to write my own memory functionality for my AI agents but wondering if it’s worth it just to have a nicer UI and more modern JS env.