From c04742f90efe8d205736ad4b697cc351adf54566 Mon Sep 17 00:00:00 2001 From: Taras Yemets Date: Fri, 4 Oct 2024 11:37:52 +0300 Subject: [PATCH] Update model config docs --- docs/cody/clients/model-configuration.mdx | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/docs/cody/clients/model-configuration.mdx b/docs/cody/clients/model-configuration.mdx index 751ff0f2f..1f7d61717 100644 --- a/docs/cody/clients/model-configuration.mdx +++ b/docs/cody/clients/model-configuration.mdx @@ -42,7 +42,10 @@ This requires site-admin privileges. To do so, ```json { // [...] - "cody.enabled": true + "cody.enabled": true, + "completions": { + "provider": "sourcegraph" + } } ``` @@ -319,6 +322,7 @@ The simplest way to configure your Sourcegraph Enterprise would be to add the fo ```json ... + "cody.enabled": true, "modelConfiguration": { "sourcegraph": {} }, @@ -360,6 +364,7 @@ The `"allow"` and `"deny"` fields, are arrays of [model references](#model-confi The following examples illustrate how to use all these settings in conjunction: ```json +"cody.enabled": true, "modelConfiguration": { "sourcegraph": { "modelFilters": { @@ -390,6 +395,7 @@ The `"modelConfiguration"` setting also contains a `"defaultModels"` field that ```json ... + "cody.enabled": true, "modelConfiguration": { "defaultModels": { "chat": "anthropic::2023-06-01::claude-3.5-sonnet", @@ -421,6 +427,7 @@ By defining a provider override in your Sourcegraph site configuration, you are The following configuration shippet defines a single provider override with the ID `"anthropic"`. ```json +"cody.enabled": true, "modelConfiguration": { // Do not use any Sourcegraph-supplied models. "sourcegraph": null, @@ -487,6 +494,7 @@ With a provider defined, we can now specify custom models using that provider by The following configuration snippet defines a custom model, using the `"anthropic"` provider from the previous example. ```json +"cody.enabled": true, "modelConfiguration": { ... "modelOverrides": [