You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As I've continued to use griptape, the paradigm of using PromptTasks inside of broader request contexts is becoming repetitive and not as clean as using Agents. I'm slowly articulating prompts in the form of responsibilities for specific agents and rather than re-setting this up in a pipeline, I'd rather be able to chain prompts between agents in the form of a pipeline. Rulesets allow me to assign responsibilities in a nice programmatic format and I'd like to keep that.
This programming model enables users to treat agents similarly to actors with Pipelines essentially enabling message passing between the respective agents. For example, I have one agent that summarizes a prompt based on a ruleset and another agent that acts on the summarized prompt with its own ruleset.
It'd be nice to define agents and simply chain their I/O in the following form:
Hey @jimatregrello thanks for trying out Griptape, and for the great feedback! This is something we've been playing with internally, I think need a StructureRunnerTask and StructureRunnerTool. That would enable something like:
To provide more context, we have instances where we may want to fine tune models for individual agents before chaining and that's where this will be a huge help.
As I've continued to use griptape, the paradigm of using PromptTasks inside of broader request contexts is becoming repetitive and not as clean as using Agents. I'm slowly articulating prompts in the form of responsibilities for specific agents and rather than re-setting this up in a pipeline, I'd rather be able to chain prompts between agents in the form of a pipeline. Rulesets allow me to assign responsibilities in a nice programmatic format and I'd like to keep that.
This programming model enables users to treat agents similarly to actors with Pipelines essentially enabling message passing between the respective agents. For example, I have one agent that summarizes a prompt based on a ruleset and another agent that acts on the summarized prompt with its own ruleset.
It'd be nice to define agents and simply chain their I/O in the following form:
This enables me to build agents in isolation and test their input and output and then chain them together.
The text was updated successfully, but these errors were encountered: