@vansangpfiev

1. Can we make this syntax a bit more inconsistent:

• not: cortex engines <engine_name> install
• correct: cortex models start <model_id>

2. Can we decide on syntax around required vs optional flags, e.g. when do we expect users to use a flag, vs not?

3. I see this getting conflated as well get vs pull vs install. Was the decision:

• pull: just for models, docker like
• get: available for most methods, similar to a local api /get request
• install: for when user is installing something from remote/internet?

1. Yes - I think we should follow the syntax that @dan-homebrew suggested

cortex <feature> <command> <subject>
cortex engines install <engine>

cc: @namchuai
2. All flags are optional for now (except cortex -v), I think

• --verbose for logging
• --version specify a version to download
• --message to append message to chat command

3. It is correct.

Maybe we can use a specific example:

Usage: cortex-nightly chat [OPTIONS] [model_id]

Positionals:
  model_id TEXT

Options:
  -h,--help                   Print this help message and exit
  -m,--message TEXT           Message to chat with model

Confusing

1. model id is required
2. message is not
3. Request fails if message is not provided

OAI indicates both params are required.

So should the proper syntax actually be:

• cortex chat <model_id> <message> [-options] OR
• cortex chat [-options] <model_id> <message>

cc @dan-homebrew

@vansangpfiev Quick check: does the CLI library we use auto-generate the "UI" (e.g. with helper flags, etc)?

@0xSage These are standard CLI library features, I wouldn't over-litigate this - there's best practices out there already

@dan-homebrew Yes - The "UI" is autogenerated by the CLI library
@0xSage The message is mandatory in the request body. But we are talking about the CLI, so if the message is not specified, can we just let user inputs it later? Something like:

.\cortex.exe models chat tinyllama
Inorder to exit, type `exit()`
> // input message here

The syntax should be:

• cortex chat <model_id> -m <message> OR
• cortex chat -m <message> <model_id>

Yes, this is straightforward and can be implemented in the final days as finishing touches
We can also put in the "Cortex" ASCII text

I am adding this in as a tail end task for Cortex v0.1