UI - Changing workspace from UI does not take effect

[sangee2004]

gptscript version - v0.0.0-dev-51fd2b32-dirty

Steps to reproduce the problem

1. Get k8s docs made available in local directory using git clone https://github.com/kubernetes/website.git
2. Run the following script to launch knowledge chat agent without workspace option - gptscript --ui --disable-cache knowledge_remote.gpt

tools: github.com/gptscript-ai/knowledge
context: github.com/gptscript-ai/context/workspace
chat: true

You are a helpful assistant that can retrieve information and answer questions using your tools. When you strat just introduce yourself and wait for the user to prompt you. 
You must use the knowledge tool to look up answers to your questions. Do NOT use the read tool. You may only answer questions with information you retrieve from the knowledge tool.
When you give answers, always give a proper citation to the best of your abilities.

3. Used UI to set workspace parameter (edit existing value seen for workspace) and set it to k8s doc directory from step1 . This resulted in UI prompting to restart the script and allow for this operartion.
4. Once script is loaded , tool calls made still continue to use the default workspace that was presented to me initially and I dont get any results for queries relating to k8s.

[thedadams]

PR: #575

[thedadams]

@sangee2004 The changes to fix this issue have been merged.

As state in Slack, you should be able to reproduce this issue (and then verify the fix) by doing something like

GPTSCRIPT_WORKSPACE_DIR=/some/other/path gptscript --workspace /my/workspace my-script.gpt

If the my-script.gpt uses the workspace context, then it will use /some/other/path instead of the /my/workspace, which is not correct.

[sangee2004]

Tested with gptscript version - v0.0.0-dev-91751200-dirty

Changing workspace from within UI works as expected.

User is not allowed to override the workspace by setting GPTSCRIPT_WORKSPACE_DIR anymore.