ekarabeg

I've been working on an open-source platform to build agentic workflows. I really wanted a Figma-like experience for building agents.

Apache-2.0 license: https://github.com/simstudioai/sim

This seems really interesting. I tried running a swarm on my landing page but didn't get a completed email. I'll try it again, though!

Try out https://hn.simstudio.ai for a live example, but we're also releasing templates this week to see community workflows.

That's awesome! I like the visual rendering on the canvas.

We believe a visual solution is the best way for developers — and LLMs — to build applications in the future.

Thanks for the suggestion! We're adding in a prompt to workflow this week.

The big names out there are n8n and flowwise. I'd encourage you to try them out and let us know what you think compared to Sim Studio! We have a logs page that shows execution duration, tool call duration, tokens used, the cost based on the model you selected, etc.

Exactly

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!

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!

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!

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?

Congrats on the launch! Awesome product!