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

Function groups #17

Open
dev-msp opened this issue Nov 10, 2023 · 2 comments
Open

Function groups #17

dev-msp opened this issue Nov 10, 2023 · 2 comments

Comments

@dev-msp
Copy link

dev-msp commented Nov 10, 2023

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.

@blindmansion
Copy link
Member

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.

@blindmansion
Copy link
Member

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants