waleedlatif1

6 ms·

1. 31.▲
   by waleedlatif1 1y ago

   i like to think of us as the version of these automation platforms that doesn't make you hardcode in all the non-determinism & edge cases, because now we can just use llms :)
2. 32.▲
   by waleedlatif1 1y ago

   we bet that its just because they pre-dated LLMs and don't really allow for granular control. the goal is to make it easier to develop automations/workflows, not harder. we think the future of development is 90% transformations&#x
3. 33.▲
   by waleedlatif1 1y ago

   thanks for the feedback, we are launching a ton of templates on the platform this week that you can add to your workspace with a single click. also, we'll add some examples to the home page
4. 34.▲
   by waleedlatif1 1y ago

   i think it significantly lowers the bar for entry to building agentic workflows, but also has the potential to augment the development process for engineers since its such a tight feedback loop. for instance, we were working on a sales &amp
5. 35.▲
   by waleedlatif1 1y ago

   thanks for the feedback, will add the demo directly to the website!
6. 36.▲
   by waleedlatif1 1y ago

   thank you! We believe Sim Studio is different because we built it from the ground up to be ai-native - not an automation tool that bolted on ai features as an afterthought A few points on this: - Super intuitive & highly configurable vi
7. 37.▲
   Launch HN: Sim Studio (YC X25) – Figma-like canvas for agent workflows

   55 points by waleedlatif1 1y ago|32 comments
8. 38.▲
   by waleedlatif1 1y ago

   tried another fix! let me know if that resolves it for you, otherwise you can join the discord and I can help you debug to the best of my ability. sorry for the hassle
9. 39.▲
   by waleedlatif1 1y ago

   If you want to add a custom tool for your agent to use, you can use the “add custom tool” in the agent block and just define the JSON schema and the code for the tool call. If you want a custom integration, you can either request it, or if
10. 40.▲
    by waleedlatif1 1y ago

    just pushed a hotfix that should resolve this for you! let me know if you are still having issues. we recently updated the csp and needed to explicitly add the ollama endpoint to the connect-src directive
11. 41.▲
    by waleedlatif1 1y ago

    i think it could be one of a few things: - first, even though your ollama is running on the host, you still need to use the local profile flag to enable ollama models in the UI. you can do this by running the docker compose command with `lo
12. 42.▲
    by waleedlatif1 1y ago

    of course! we will be sure to keep the most up-to-date & accurate documentation and document all of the intricacies like this one, and create a roadmap as well. excited for you to try it out and let us know what you think
13. 43.▲
    by waleedlatif1 1y ago

    thank you! for ollama running on your host machine, you'll need to modify the docker configuration since by default it's looking at http://localhost:11434 which points to localhost inside the container, not your host.
14. 44.▲
    by waleedlatif1 1y ago

    thanks!
15. 45.▲
    by waleedlatif1 1y ago

    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
16. 46.▲
    by waleedlatif1 1y ago

    thanks!
17. 47.▲
    by waleedlatif1 1y ago

    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.
18. 48.▲
    by waleedlatif1 1y ago

    thank you and exactly! that's why we built it. trigger it many different ways, swap out tools, models, etc. Just focus on the things that matter for agent performance and ignore everything else
19. 49.▲
    by waleedlatif1 1y ago

    thanks! that would be awesome to have, always welcome contributors :)
20. 50.▲
    by waleedlatif1 1y ago

    although I haven't experimented with gemma 3 locally, with ollama we have instructions in the README, and all you need to do is initialize the model, and pull it when running sim studio. let me know how it goes!
21. 51.▲
    by waleedlatif1 1y ago

    for ease of use, we are exploring a way to add in short-term and medium-term memory out of the box in a way that doesn't require us to inject anything into the agent's context unless the user explicitly wants to. for longer-term m
22. 52.▲
    by waleedlatif1 1y ago

    yeah! for stagehand, I actually stitched together a way for you to login and authenticate on platforms without the LLM's ever seeing your login credentials. in the prompt, you can specify the username as %username% and provide the cred
23. 53.▲
    by waleedlatif1 1y ago

    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
24. 54.▲
    by waleedlatif1 1y ago

    we have support for browser agents (browser-use and stagehand), but running this locally with computer use agents would change the game. will explore :)
25. 55.▲
    by waleedlatif1 1y ago

    this is something we've been looking into. curious, would you rather export the code into an existing agentic framework like crewai/langgraph, or have it exported as raw code? also, would you prefer if the code was exported block-
26. 56.▲
    by waleedlatif1 1y ago

    thanks for the feedback! adding some screenshots to the docs showcasing more complex workflows we've created so far
27. 57.▲
    Show HN: Sim Studio – Open-Source Agent Workflow GUI(github.com)

    196 points by waleedlatif1 1y ago|58 comments