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
I think there's significant potential in the idea of using cannoli's node API for modeling "functions" for the API to call - what do you think?
I see it as being very similar to how you use *.cno files as "callable" operations with inputs and outputs, with the key difference being how you expose the callable, and to whom. Rather than exposing it to the user as an Obsidian command they, a .cnof file (or whatever) would be exposed to OpenAI as a callable function.
Naturally you'd want to be careful about token usage. Maybe don't allow nested function calls, or at least prompt the user when that happens. Since you've already got cost-calculating logic, maybe that wouldn't be too much of a lift.
The text was updated successfully, but these errors were encountered:
I like the sound of this, but I'm not quite grasping it. Are you talking about making cannoli's trigerrable by other cannolis? This is indeed something I've been thinking about, but I'm not sure that's exactly what you're suggesting.
@dev-msp hoping to implement this as "sub-cannolis" soon! A workaround for this is also now possible by using our new Val Town integration to push a cannoli up as an API and then call it using an http action node.
I think there's significant potential in the idea of using cannoli's node API for modeling "functions" for the API to call - what do you think?
I see it as being very similar to how you use
*.cno
files as "callable" operations with inputs and outputs, with the key difference being how you expose the callable, and to whom. Rather than exposing it to the user as an Obsidian command they, a.cnof
file (or whatever) would be exposed to OpenAI as a callable function.Naturally you'd want to be careful about token usage. Maybe don't allow nested function calls, or at least prompt the user when that happens. Since you've already got cost-calculating logic, maybe that wouldn't be too much of a lift.
The text was updated successfully, but these errors were encountered: