Breaking Workspace Change in v14.0.0

[olimorris]

Following on from: #705

Hi All,

Such little time has passed between breaking changes in v13.0.0 and v14.0.0. I'm not expecting this to be a hugely impactful breaking change and the fix is rather quick.

So, in v14.0.0 the workspace file format has been streamlined and optimized to make it easier for an LLM to create on your behalf. Please see CodeCompanion's own workspace file here.

Workspace groups now reference data objects which sit in their own, in the file. This makes it much easier to reference the same file in multiple groups. I've also created a JSON Schema for workspace files, here.

Most useful of all is the Workspace File prompt that now ships in the action palette. When selected, it will open up a chat buffer, and add the workspace JSON schema as part of a prompt. It will also determine if you have a workspace file in your current working directory, and if you do, the prompts will be altered to ask the LLM to help you in adding a group, rather than generating a whole workspace file. Whilst this approach is helpful, you'll still need to manually share a lot of context for the LLM to be able to understand the intricacies of your codebase. A more optimal way is to leverage VectorCode. The prompt will determine if you have this installed and add it to the chat as a tool.

Regarding the latter, I am very much open to PRs to make that prompt more useful. Please, please, please share how you fine-tune this.