Hmm, let's say user import the model locally, which is drag and drop to Jan. Then, source_url might not be relevant, right?

Hmm, let's say user import the model locally, which is drag and drop to Jan. Then, source_url might not be relevant, right?

I think we still have to think about this from the perspective of technical users who directly mv & edit files.

Then what is absolutely required for models to run - it should be as little fields required as possible.

One option is a global model.json file in /models that specifies the default values of a model.json. It is used as a fallback when individual model.jsons haven't defined certain fields. This also makes it clear to users what the default model settings are.

Open to a more elegant solution here. I really dont know.

Scenarios:

• User has 1 model binary, but has 2 configurations, e.g. folders model-a-with-params-a and model-a-with-params-b. It doesnt make sense for users to create copies of large model binaries. In this case source_url: ../../model-a/model.gguf would be neat.
• User decides they want all downloaded models to have max_tokens: 2048 (or some other global default preference), in this case, they'd only have to edit the default model.json once, instead of editing every single model.json in every model download folder. (In fact, the individual model.jsons can be quite sparse)

Happy to chat/debate about this further tomorrow! cc @dan-jan @hiro-v (who were in original discussions about this)

Update, for RAG /files, we decided to copy over each file upload directly into /thread-id folder.