Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Public variables #41

Closed
michaelsharpe opened this issue Jan 9, 2023 · 4 comments · Fixed by #202
Closed

Public variables #41

michaelsharpe opened this issue Jan 9, 2023 · 4 comments · Fixed by #202
Assignees
Labels
enhancement New feature or request help wanted Extra attention is needed
Milestone

Comments

@michaelsharpe
Copy link
Contributor

Public variable nodes. Should have different types. Could possibly just make our current variables exposable as public. A public variable can be inject into the spell. So either as data from outside or as sockets into a spell. Used to create sets of data for different entities to share the same brain/spell.

Need to consider whether public variables can be populated from the top level spell all the way down to subspells or not.

@michaelsharpe michaelsharpe added help wanted Extra attention is needed enhancement New feature or request labels Jan 9, 2023
@lalalune
Copy link
Contributor

@FabriceIRANKUNDA next step on this

  • all public variables for the "root spell" chosen are exposed in the agent's dropdown
  • we pass this data into the spell runner when we run the spell (or when we load it?)
  • goal is a bot that says "hi my name is <name" with the name coming from a public variable that is set on the agent

@lalalune lalalune added this to the v0.2.0 milestone Feb 12, 2023
@lalalune
Copy link
Contributor

Screen.Recording.2023-02-19.at.1.18.41.AM.mp4

@lalalune
Copy link
Contributor

Group 1

@lalalune lalalune modified the milestones: v0.2.0, MVP Feb 19, 2023
@michaelsharpe
Copy link
Contributor Author

One thing I would like to see is a set component for each variable type. Prompt input is a text area. Array input would be some kind of tag list perhaps (though arrays are more complicated if they involve complex objects). Boolean would be a switch. A number could be a range slider or just a number text area. String is just an input field. Etc.

These will be programmatically composed from a set of react components. This will make it easier to style these as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants