8 ms·
How does this work? I'm assuming you're using openai's function/tool calling. But how do you support the forking of the tools? The scheduling is cool.
by dardagreg 2y ago
How does this work? I'm assuming you're using openai's function/tool calling. But how do you support the forking of the tools? The scheduling is cool.
- kmgrassi 2y agoYep! I'm using OpenAI's assistants api. Regarding the tool forking - I have the canonical function hosted on the server. When someone forks an agent it grabs the agent context and all the tools and creates a new `assistant` with Open AI. When the tool is called during a thread it just points to the canonical function. I'm really excited about the next step - allowing folks to create their own tools and add them to the canonical function list. This will allow everyone to build on each other's work and use tools as building blocks for complex agents. Thanks for checking it out! Lmk if you have other questions!
- dardagreg 2y agoThat makes sense. Like it. One question - in the video you mentioned adding credentials that would be available to the function calling. I didn't see that tool when I forked the HN demo agent. Where can I find that? I really like the credentials idea. Having a way to use them for tool/function calling but not available to the AI is smart. With credentials you could envision giving the AI access to all sorts of services. Really opens up the possibilities. Let me know where I can find the credentials tool. Thanks
- kmgrassi 2y agoSo you can add credentials by clicking on the agent name and getting to the agent config. The agent in the video that had the credentials was a different private agent I have. Credentials were just added as a feature and I haven't built the functionality yet to fork them (need to fork only the keys not the value). But you can add credentials to any agent. If you can't find them, ping me at my HN handle at gmail and I can give you a quick walk through. Thanks again for checking Fabrk out!