Closed sangee2004 closed 2 months ago
So far I have been able to figure out that this is a problem unique to the knowledge tool. Other tools are able to handle a workspace switch without a problem.
@g-linville This may be because https://github.com/gptscript-ai/knowledge/blob/1699d925b168fe4cd325d4e345c087115c661bbe/tool.gpt#L18C64-L18C87
Knowledge tool would work even with workspace context when setting just the workspace env variable when testing with "--ui" option.
This is what I see in the stacktraces - the workspace context tool itself returns something wrong :thinking:
But here's the weirdest thing is this:
As soon as I swap it out for a local reference to the knowledge tool, it works just fine :thinking:
I created a fork and added some logging to try to debug (github.com/g-linville/knowledge@grant-gateway
), but it just worked also. This is weird. Must be something particular to how the UI handles the knowledge repo maybe? I'll have to look into it more.
Tested the workflow mentioned in the issue and it works as expected with electron build from 523bf344b
But I dont see the new version of knowledge tool made available when adding knowledge tool using tool catalog . I still get "Knowledge@V0 4.7 Gateway" version.
Will retest scenario when the new knowledge tool is made available in tool catalog.
This workflow of having knowledge exposed in the "tool catalog" will be removed shortly. Closing this issue since it will be a supported workflow anymore.
Electron app from commit id
d2a9e6ecef
Steps to reproduce the problem:
knowledge
andworkspace
tool.What is my day 7 travel plan?
I get the following response
Stack Trace view shows that Knowledge tool is working from the default workspace -
/Users/sangeethahariharan/Library/Application Support/acorn/Acorn/workspace
Expected Behavior:
Knowledge tool should work from the current workspace that is set for the thread.