This is really cool! I’m doing something similar with Lemon Agent (https://github.com/felixbrock/lemon-agent). What I find most powerful about defining workflows in a json file is that you can add additional fields to let the LLM know about specific execution requirements, like asking the user for permission before executing a specific workflow step. This allows for infinite configuration options. Curious to hear if you already experimented with something like this or if you are planning to include something similar?
Sorry for the delay. I hadn’t thought about that specifically, but I think it’s a good idea. Basically, we can add all kinds of settings and options with the JSON. But I do want to avoid unnecessary bloat, and keep this as simple as possible.
Comments
This is really cool! I’m doing something similar with Lemon Agent (https://github.com/felixbrock/lemon-agent). What I find most powerful about defining workflows in a json file is that you can add additional fields to let the LLM know about specific execution requirements, like asking the user for permission before executing a specific workflow step. This allows for infinite configuration options. Curious to hear if you already experimented with something like this or if you are planning to include something similar?
Sorry for the delay. I hadn’t thought about that specifically, but I think it’s a good idea. Basically, we can add all kinds of settings and options with the JSON. But I do want to avoid unnecessary bloat, and keep this as simple as possible.