Configuration

Configuration is optional, default values will be used if no configuration profile isprovided.

Viewing the current configuration

From the command line

Run the program with theconfig argument:

lweconfig

You can also view just a portion of the config by providing a filter argument.

To view just the file/directory config:

lweconfigfiles

From a running instance

/config

This will show all the current configuration settings, the most important ones for installation are:

  • Config dir: Where configuration files are stored

  • Current profile: (shown in theProfileconfiguration section)

  • Config file: The configuration file current being used

  • Data dir: The data storage directory

From a running instance, you can also view just a portion of the configuration by providing afilter argument:

/config model

…will show just themodel portion of the configuration

A very handy filter is/configdatabase, which will show just the currently configureddatabase connection string.

Sample configuration

The default configuation settings can be seen inconfig.sample.yaml– the file is well-commented with descriptions of the settings.

DON’T just copy this file as your configuration!

Instead, use it as a reference to tweak the configuration to your liking.

NOTE: Not all settings are available on all backends. See the example config for more information.

Command line arguments overrride custom configuration settings, which override defaultconfiguration settings.

Editing the configuration for the current profile

  1. Start the program:lwe

  2. Open the profile’s configuration file in an editor:/configedit

  3. Edit file to taste and save

Most configuration options will be reloaded dynamically after the configuration file is saved,otherwise a restart of the program is required.

Configuring model properties

To change the properties of a particular LLM model, use the/model command:

/model model_name gpt-3.5-turbo/model temperature 1.0

The/model command works within the models of the currently loadedprovider.

NOTE: The attributes that a particular model accepts are beyond the scope of thisdocument. While some attributes can be displayed via command completion in theshell, you are advised to consult the API documentation for the specific providerfor a full list of available attributes and their values.