Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

github.com

Post reply on HN
Print view View original

41–50 of 63 posts

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

#43

Post by handfuloflight »

waleedlatif1 wrote: post #9
ddon wrote: post #7

Would be amazing to be able to design the workflow using your builder, and then export to code (and choose the language) and then copy paste the code into the project... just an idea.

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-by-block or the entire workflow altogether?

Raw code, block by block.

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

#44

Post by ekarabeg »

handfuloflight wrote: post #43
waleedlatif1 wrote: post #9

Earlier quoted context omitted.

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-by-block or the entire workflow altogether?

Raw code, block by block.

Exactly

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

#46

Post by dr_kiszonka »

waleedlatif1 wrote: post #38
dr_kiszonka wrote: post #34

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…

Thanks for replying so quickly and in detail. I wanted to understand issues around scalability and integration into a larger system.

I have been looking for a good solution in this increasingly crowded space and if I could offer a word of unsolicited advice it would be to ensure documentation is top notch, truthful (some competitors mention non-existent features in their docs), and includes a relatively detailed roadmap.

Good luck with Sim Studio. I may try it out in a few weeks!

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

#47

Post by waleedlatif1 »

rahimnathwani wrote: post #45

The UI looks lovely. If I run Sim Studio with docker compose, how do I point it to the existing `ollama serve` instance running on the host? I looked in settings (in the workspace UI) but don't see anywhere to configure the ollama endpoint.

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. you can either add `extra_hosts` as `host.docker.internal:host-gateway` to your docker compose and set the OLLAMA_HOST envvar to `OLLAMA_HOST=http://host.docker.internal:11434`, or just run `docker compose up --profile local-cpu -d --build --network=host` when running the compose command.

will add this to the readme and add in some UI locally so its easily configurable! let me know if you have any issues

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

#48

Post by waleedlatif1 »

dr_kiszonka wrote: post #46
waleedlatif1 wrote: post #38

Earlier quoted context omitted.

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…

Thanks for replying so quickly and in detail. I wanted to understand issues around scalability and integration into a larger system. I have been looking for a good solution in this increasingly crowded space and if I could offer a word of unsolicited advice it would be to ensure documentation is top notch, truthful (some competitors mention non-existent features in their docs), and includes a relatively detailed road…

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

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

#49

Post by rahimnathwani »

waleedlatif1 wrote: post #47
rahimnathwani wrote: post #45

The UI looks lovely. If I run Sim Studio with docker compose, how do I point it to the existing `ollama serve` instance running on the host? I looked in settings (in the workspace UI) but don't see anywhere to configure the ollama endpoint.

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. you can either add `extra_hosts` as `host.docker.internal:host-gateway` to your docker compose and set the OLLAMA_HOST envvar to `OLLAMA_HOST= http://host.docker.internal:11434 `, or just run `docker co…

I modified the docker-compose.yml thus:

  ...
  services:
    simstudio:
      build:
        context: .
        dockerfile: Dockerfile
      ports:
        - "3000:3000"
      volumes:
        - ./sim:/app
        - /app/node_modules
        - /app/.next
      extra_hosts:
        - "host.docker.internal:host-gateway"
      environment:
        - OLLAMA_HOST=http://host.docker.internal:11434
        - NODE_ENV=development
        - DATABASE_URL=postgresql://postgres:postgres@db:5432/simstudio
      ...
Then I ran `docker compose up -d --build`

Then I went to localhost:3000/w/

Then I added an Agent block. I expected ollama (or my ollama models) to show up in the drop-down, but I only see the hosted models.

I even tried editing `sim/providers/ollama/index.ts`:

  const OLLAMA_HOST = 'http://host.docker.internal:11434'
Any ideas?

(BTW I did NOT run `--profile local-cpu` because I didn't want to run ollama in a docker container, as it's already running on the host.)

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

#50

Post by waleedlatif1 »

rahimnathwani wrote: post #49
waleedlatif1 wrote: post #47

Earlier quoted context omitted.

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. you can either add `extra_hosts` as `host.docker.internal:host-gateway` to your docker compose and set the OLLAMA_HOST envvar to `OLLAMA_HOST= http://host.docker.internal:11434 `, or just run `docker co…

I modified the docker-compose.yml thus: ... services: simstudio: build: context: . dockerfile: Dockerfile ports: - "3000:3000" volumes: - ./sim:/app - /app/node_modules - /app/.next extra_hosts: - "host.docker.internal:host-gateway" environment: - OLLAMA_HOST=http://host.docker.internal:11434 - NODE_ENV=development - DATABASE_URL=postgresql://postgres:postgres@db:5432/simstudio ... Then I ran `docker compose up -d --…

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 `local-cpu` - also, make sure your host ollama is actually running and responding (curl http://localhost:11434/api/tags should show your models) - if neither of the above work, you may need to restart the app container after changing the OLLAMA_HOST value
Post reply on HN