We must make the kai/rpc-server binary that we will run configurable (by default if this is unset we will use the one packaged in assets/bin). Additionally, we need a flag so that when we go to start our client we choose the correct binary to spawn.
Our package.json needs to be updated to contribute new configuration (see here). User's should be able to configure:
1) The path to the kai/rpc-server to be used
2) Should we use kai/rpc-server over the analyzer binary (because we are only going to manage the lifecycle of one or the other).
Start kai/rpc-server
Assuming the user's environment has been configured to enableGenerativeAI (or some other name to represent that the user wants genAI capabilities, when given the "Start Analyzer" command, we need to start the kai/rpc-server.
Definition of Done:
package.json updated for new configuration items + any command for configuring this + binary configuration walkthrough item updated
Configuration
We must make the kai/rpc-server binary that we will run configurable (by default if this is unset we will use the one packaged in assets/bin). Additionally, we need a flag so that when we go to start our client we choose the correct binary to spawn.
Our package.json needs to be updated to contribute new configuration (see here). User's should be able to configure:
1) The path to the kai/rpc-server to be used 2) Should we use kai/rpc-server over the analyzer binary (because we are only going to manage the lifecycle of one or the other).
Start kai/rpc-server
Assuming the user's environment has been configured to
enableGenerativeAI(or some other name to represent that the user wants genAI capabilities, when given the "Start Analyzer" command, we need to start the kai/rpc-server.Definition of Done: