From fdc1455ad9346e5558daabdd2097d5cd7ad3fd44 Mon Sep 17 00:00:00 2001 From: Pavel Tisnovsky Date: Sun, 7 Dec 2025 13:34:24 +0100 Subject: [PATCH] LCORE-533: updated config doc --- docs/config.html | 2111 +++++++++++++++++++++++----------------------- 1 file changed, 1070 insertions(+), 1041 deletions(-) diff --git a/docs/config.html b/docs/config.html index 215ebc3d4..25b89f93a 100644 --- a/docs/config.html +++ b/docs/config.html @@ -1,11 +1,12 @@ + - - - - - - - - -
-

-
-

Lightspeed Core Stack

-
-

📋 Configuration schema

-

AccessRule

-

Rule defining what actions a role can perform.

- - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
rolestringName of the role
actionsarrayAllowed actions for this role
-

Action

-

Available actions in the system.

-

Note: this is not a real model, just an enumeration of all action + + +

+

+
+

Lightspeed Core Stack

+
+

📋 Configuration schema

+

AccessRule

+

Rule defining what actions a role can perform.

+ + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
rolestringName of the role
actionsarrayAllowed actions for this role
+

Action

+

Available actions in the system.

+

Note: this is not a real model, just an enumeration of all action names.

-

AuthenticationConfiguration

-

Authentication configuration.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
modulestring
skip_tls_verificationboolean
k8s_cluster_apistring
k8s_ca_cert_pathstring
jwk_config
rh_identity_config
-

AuthorizationConfiguration

-

Authorization configuration.

- - - - - - - - - - - - - - - -
FieldTypeDescription
access_rulesarrayRules for role-based access control
-

ByokRag

-

BYOK (Bring Your Own Knowledge) RAG configuration.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
rag_idstringUnique RAG ID
rag_typestringType of RAG database.
embedding_modelstringEmbedding model identification
embedding_dimensionintegerDimensionality of embedding vectors.
vector_db_idstringVector DB identification.
db_pathstringPath to RAG database.
-

CORSConfiguration

-

CORS configuration.

-

CORS or ‘Cross-Origin Resource Sharing’ refers to the situations when +

AuthenticationConfiguration

+

Authentication configuration.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
modulestring +
skip_tls_verificationboolean +
k8s_cluster_apistring +
k8s_ca_cert_pathstring +
jwk_config + +
rh_identity_config + +
+

AuthorizationConfiguration

+

Authorization configuration.

+ + + + + + + + + + + + + + + +
FieldTypeDescription
access_rulesarrayRules for role-based access control
+

ByokRag

+

BYOK (Bring Your Own Knowledge) RAG configuration.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
rag_idstringUnique RAG ID
rag_typestringType of RAG database.
embedding_modelstringEmbedding model identification
embedding_dimensionintegerDimensionality of embedding vectors.
vector_db_idstringVector DB identification.
db_pathstringPath to RAG database.
+

CORSConfiguration

+

CORS configuration.

+

CORS or ‘Cross-Origin Resource Sharing’ refers to the situations when a frontend running in a browser has JavaScript code that communicates -with a backend, and the backend is in a different ‘origin’ than the +with a backend, and the backend is in a different ‘origin’ than the frontend.

-

Useful resources:

- - ----- - - - - - - - - - - - - + +
FieldTypeDescription
allow_originsarrayA list of origins allowed for cross-origin requests. An origin is +

Useful resources:

+ + + + + + + + + + + + + + + + + + + - - - - - + + + + - - - - - - - - - - + + + + + + + + + - - -
FieldTypeDescription
allow_originsarrayA list of origins allowed for cross-origin requests. An origin is the combination of protocol (http, https), domain (myapp.com, localhost, -localhost.tiangolo.com), and port (80, 443, 8080). Use [’*’] to allow +localhost.tiangolo.com), and port (80, 443, 8080). Use [’*’] to allow all origins.
allow_credentialsbooleanIndicate that cookies should be supported for cross-origin +
allow_credentialsbooleanIndicate that cookies should be supported for cross-origin requests
allow_methodsarrayA list of HTTP methods that should be allowed for cross-origin -requests. You can use [’*’] to allow all standard methods.
allow_headersarrayA list of HTTP request headers that should be supported for -cross-origin requests. You can use [’*’] to allow all headers. The +
allow_methodsarrayA list of HTTP methods that should be allowed for cross-origin +requests. You can use [’*’] to allow all standard methods.
allow_headersarrayA list of HTTP request headers that should be supported for +cross-origin requests. You can use [’*’] to allow all headers. The Accept, Accept-Language, Content-Language and Content-Type headers are always allowed for simple CORS requests.
-

Configuration

-

Global service configuration.

- ----- - - - - - - - - - - - - + +
FieldTypeDescription
namestringName of the service. That value will be used in REST API +
+

Configuration

+

Global service configuration.

+ + + + + + + + + + + + + + + + + + - - - - - + + + - - - - - + + + - - - - - + + + - - - - - + + + - - - - - + + + + - - - - - - - - - - + + + + + + + - - - - - + + + - - - - - + + + - - - - - - - - - - + + + + + + + - - - - - - - -
FieldTypeDescription
namestringName of the service. That value will be used in REST API endpoints.
serviceThis section contains Lightspeed Core Stack service +
service + This section contains Lightspeed Core Stack service configuration.
llama_stackThis section contains Llama Stack configuration. Lightspeed Core +
llama_stack + This section contains Llama Stack configuration. Lightspeed Core Stack service can call Llama Stack in library mode or in server mode.
user_data_collectionThis section contains configuration for subsystem that collects user +
user_data_collection + This section contains configuration for subsystem that collects user data(transcription history and feedbacks).
databaseConfiguration for database to store conversation IDs and other +
database + Configuration for database to store conversation IDs and other runtime data
mcp_serversarrayMCP (Model Context Protocol) servers provide tools and capabilities +
mcp_serversarrayMCP (Model Context Protocol) servers provide tools and capabilities to the AI agents. These are configured in this section. Only MCP servers defined in the lightspeed-stack.yaml configuration are available to the agents. Tools configured in the llama-stack run.yaml are not accessible to lightspeed-core agents.
authenticationAuthentication configuration
authorizationLightspeed Core Stack implements a modular authentication and +
authentication + Authentication configuration
authorization + Lightspeed Core Stack implements a modular authentication and authorization system with multiple authentication methods. Authorization is configurable through role-based access control. Authentication is handled through selectable modules configured via the module field in the authentication configuration.
customizationIt is possible to customize Lightspeed Core Stack via this section. +
customization + It is possible to customize Lightspeed Core Stack via this section. System prompt can be customized and also different parts of the service can be replaced by custom Python modules.
inferenceOne LLM provider and one its model might be selected as default +
inference + One LLM provider and one its model might be selected as default ones. When no provider+model pair is specified in REST API calls (query endpoints), the default provider and model are used.
conversation_cache
byok_ragarrayBYOK RAG configuration. This configuration can be used to +
conversation_cache + +
byok_ragarrayBYOK RAG configuration. This configuration can be used to reconfigure Llama Stack through its run.yaml configuration file
quota_handlersQuota handlers configuration
-

ConversationHistoryConfiguration

-

Conversation history configuration.

- ----- - - - - - - - - - - - - + + + + + +
FieldTypeDescription
typestringType of database where the conversation history is to be +
quota_handlers + Quota handlers configuration
+

ConversationHistoryConfiguration

+

Conversation history configuration.

+ + + + + + + + + + + + + + + + + + - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typestringType of database where the conversation history is to be stored.
memoryIn-memory cache configuration
sqliteSQLite database configuration
postgresPostgreSQL database configuration
-

CustomProfile

-

Custom profile customization for prompts and validation.

- - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
pathstringPath to Python modules containing custom profile.
promptsobjectDictionary containing map of system prompts
-

Customization

-

Service customization.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
profile_pathstring
disable_query_system_promptboolean
system_prompt_pathstring
system_promptstring
custom_profile
-

DatabaseConfiguration

-

Database configuration.

- - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
sqliteSQLite database configuration
postgresPostgreSQL database configuration
-

InMemoryCacheConfig

-

In-memory cache configuration.

- ----- - - - - - - - - - - - - - - -
FieldTypeDescription
max_entriesintegerMaximum number of entries stored in the in-memory cache
-

InferenceConfiguration

-

Inference configuration.

- ----- - - - - - - - - - - - - + + + + + + + + + + + + + +
FieldTypeDescription
default_modelstringIdentification of default model used when no other model is +
memory + In-memory cache configuration
sqlite + SQLite database configuration
postgres + PostgreSQL database configuration
+

CustomProfile

+

Custom profile customization for prompts and validation.

+ + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
pathstringPath to Python modules containing custom profile.
promptsobjectDictionary containing map of system prompts
+

Customization

+

Service customization.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
profile_pathstring +
disable_query_system_promptboolean +
system_prompt_pathstring +
system_promptstring +
custom_profile + +
+

DatabaseConfiguration

+

Database configuration.

+ + + + + + + + + + + + + + + + + + +
FieldTypeDescription
sqlite + SQLite database configuration
postgres + PostgreSQL database configuration
+

InMemoryCacheConfig

+

In-memory cache configuration.

+ + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
max_entriesintegerMaximum number of entries stored in the in-memory cache
+

InferenceConfiguration

+

Inference configuration.

+ + + + + + + + + + + + + + + + + + - - - - - + + + + - - -
FieldTypeDescription
default_modelstringIdentification of default model used when no other model is specified.
default_providerstringIdentification of default provider used when no other model is +
default_providerstringIdentification of default provider used when no other model is specified.
-

JsonPathOperator

-

Supported operators for JSONPath evaluation.

-

Note: this is not a real model, just an enumeration of all supported +

+

JsonPathOperator

+

Supported operators for JSONPath evaluation.

+

Note: this is not a real model, just an enumeration of all supported JSONPath operators.

-

JwkConfiguration

-

JWK (JSON Web Key) configuration.

-

A JSON Web Key (JWK) is a JavaScript Object Notation (JSON) data +

JwkConfiguration

+

JWK (JSON Web Key) configuration.

+

A JSON Web Key (JWK) is a JavaScript Object Notation (JSON) data structure that represents a cryptographic key.

-

Useful resources:

- - ----- - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
urlstringHTTPS URL of the JWK (JSON Web Key) set used to validate JWTs.
jwt_configurationJWT (JSON Web Token) configuration
-

JwtConfiguration

-

JWT (JSON Web Token) configuration.

-

JSON Web Token (JWT) is a compact, URL-safe means of representing +

Useful resources:

+ + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
urlstringHTTPS URL of the JWK (JSON Web Key) set used to validate JWTs.
jwt_configuration + JWT (JSON Web Token) configuration
+

JwtConfiguration

+

JWT (JSON Web Token) configuration.

+

JSON Web Token (JWT) is a compact, URL-safe means of representing claims to be transferred between two parties. The claims in a JWT are encoded as a JSON object that is used as the payload of a JSON Web Signature (JWS) structure or as the plaintext of a JSON Web Encryption (JWE) structure, enabling the claims to be digitally signed or integrity protected with a Message Authentication Code (MAC) and/or encrypted.

-

Useful resources:

- - ----- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
user_id_claimstringJWT claim name that uniquely identifies the user (subject ID).
username_claimstringJWT claim name that provides the human-readable username.
role_rulesarrayRules for extracting roles from JWT claims
-

JwtRoleRule

-

Rule for extracting roles from JWT claims.

- ----- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
jsonpathstringJSONPath expression to evaluate against the JWT payload
operatorJSON path comparison operator
negatebooleanIf set to true, the meaning of the rule is negated
valueValue to compare against
rolesarrayRoles to be assigned if the rule matches
-

LlamaStackConfiguration

-

Llama stack configuration.

-

Llama Stack is a comprehensive system that provides a uniform set of +

Useful resources:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
user_id_claimstringJWT claim name that uniquely identifies the user (subject ID).
username_claimstringJWT claim name that provides the human-readable username.
role_rulesarrayRules for extracting roles from JWT claims
+

JwtRoleRule

+

Rule for extracting roles from JWT claims.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
jsonpathstringJSONPath expression to evaluate against the JWT payload
operator + JSON path comparison operator
negatebooleanIf set to true, the meaning of the rule is negated
value + Value to compare against
rolesarrayRoles to be assigned if the rule matches
+

LlamaStackConfiguration

+

Llama stack configuration.

+

Llama Stack is a comprehensive system that provides a uniform set of tools for building, scaling, and deploying generative AI applications, enabling developers to create, integrate, and orchestrate multiple AI services and capabilities into an adaptable setup.

-

Useful resources:

- - ----- - - - - - - - - - - - - - - - - - - - - - - + +
FieldTypeDescription
urlstringURL to Llama Stack service; used when library mode is disabled
api_keystringAPI key to access Llama Stack service
use_as_library_clientbooleanWhen set to true Llama Stack will be used in library mode, not in +

Useful resources:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + - - - - - + + + + - - -
FieldTypeDescription
urlstringURL to Llama Stack service; used when library mode is disabled
api_keystringAPI key to access Llama Stack service
use_as_library_clientbooleanWhen set to true Llama Stack will be used in library mode, not in server mode (default)
library_client_config_pathstringPath to configuration file used when Llama Stack is run in library +
library_client_config_pathstringPath to configuration file used when Llama Stack is run in library mode
-

ModelContextProtocolServer

-

Model context protocol server configuration.

-

MCP (Model Context Protocol) servers provide tools and capabilities +

+

ModelContextProtocolServer

+

Model context protocol server configuration.

+

MCP (Model Context Protocol) servers provide tools and capabilities to the AI agents. These are configured by this structure. Only MCP servers defined in the lightspeed-stack.yaml configuration are available to the agents. Tools configured in the llama-stack run.yaml are not accessible to lightspeed-core agents.

-

Useful resources:

- - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
namestringMCP server name that must be unique
provider_idstringMCP provider identification
urlstringURL of the MCP server
-

PostgreSQLDatabaseConfiguration

-

PostgreSQL database configuration.

-

PostgreSQL database is used by Lightspeed Core Stack service for +

Useful resources:

+ + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
namestringMCP server name that must be unique
provider_idstringMCP provider identification
urlstringURL of the MCP server
+

PostgreSQLDatabaseConfiguration

+

PostgreSQL database configuration.

+

PostgreSQL database is used by Lightspeed Core Stack service for storing information about conversation IDs. It can also be leveraged to store conversation history and information about quota usage.

-

Useful resources:

- - ----- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + +
FieldTypeDescription
hoststringDatabase server host or socket directory
portintegerDatabase server port
dbstringDatabase name to connect to
userstringDatabase user name used to authenticate
passwordstringPassword used to authenticate
namespacestringDatabase namespace
ssl_modestringSSL mode
gss_encmodestringThis option determines whether or with what priority a secure GSS +

Useful resources:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - - - - - - - -
FieldTypeDescription
hoststringDatabase server host or socket directory
portintegerDatabase server port
dbstringDatabase name to connect to
userstringDatabase user name used to authenticate
passwordstringPassword used to authenticate
namespacestringDatabase namespace
ssl_modestringSSL mode
gss_encmodestringThis option determines whether or with what priority a secure GSS TCP/IP connection will be negotiated with the server.
ca_cert_pathstringPath to CA certificate
-

QuotaHandlersConfiguration

-

Quota limiter configuration.

-

It is possible to limit quota usage per user or per service or +

ca_cert_pathstringPath to CA certificate
+

QuotaHandlersConfiguration

+

Quota limiter configuration.

+

It is possible to limit quota usage per user or per service or services (that typically run in one cluster). Each limit is configured as a separate quota limiter. It can be of type user_limiter or cluster_limiter (which is name that makes sense in OpenShift deployment).

- ----- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
sqliteSQLite database configuration
postgresPostgreSQL database configuration
limitersarrayQuota limiters configuration
schedulerQuota scheduler configuration
enable_token_historybooleanEnables storing information about token usage history
-

QuotaLimiterConfiguration

-

Configuration for one quota limiter.

-

There are three configuration options for each limiter:

-
    -
  1. period is specified in a human-readable form, see + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    FieldTypeDescription
    sqlite + SQLite database configuration
    postgres + PostgreSQL database configuration
    limitersarrayQuota limiters configuration
    scheduler + Quota scheduler configuration
    enable_token_historybooleanEnables storing information about token usage history
    +

    QuotaLimiterConfiguration

    +

    Configuration for one quota limiter.

    +

    There are three configuration options for each limiter:

    +
      +
    1. period is specified in a human-readable form, see https://www.postgresql.org/docs/current/datatype-datetime.html#DATATYPE-INTERVAL-INPUT for all possible options. When the end of the period is reached, the quota is reset or increased.
      2. -
    2. initial_quota is the value set at the beginning of the +
    3. initial_quota is the value set at the beginning of the period.
      4. -
    4. quota_increase is the value (if specified) used to +
    5. quota_increase is the value (if specified) used to increase the quota when the period is reached.
      6. -
    -

    There are two basic use cases:

    -
      -
    1. When the quota needs to be reset to a specific value periodically +
    +

    There are two basic use cases:

    +
      +
    1. When the quota needs to be reset to a specific value periodically (for example on a weekly or monthly basis), set initial_quota to the required value.
      2. -
    2. When the quota needs to be increased by a specific value +
    3. When the quota needs to be increased by a specific value periodically (for example on a daily basis), set quota_increase.
      4. -
    - ----- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    FieldTypeDescription
    typestringQuota limiter type, either user_limiter or cluster_limiter
    namestringHuman readable quota limiter name
    initial_quotaintegerQuota set at beginning of the period
    quota_increaseintegerDelta value used to increase quota when period is reached
    periodstringPeriod specified in human readable form
    -

    QuotaSchedulerConfiguration

    -

    Quota scheduler configuration.

    - - - - - - - - - - - - - - - -
    FieldTypeDescription
    periodintegerQuota scheduler period specified in seconds
    -

    RHIdentityConfiguration

    -

    Red Hat Identity authentication configuration.

    - - - - - - - - - - - - - - - -
    FieldTypeDescription
    required_entitlementsarrayList of all required entitlements.
    -

    SQLiteDatabaseConfiguration

    -

    SQLite database configuration.

    - - - - - - - - - - - - - - - -
    FieldTypeDescription
    db_pathstringPath to file where SQLite database is stored
    -

    ServiceConfiguration

    -

    Service configuration.

    -

    Lightspeed Core Stack is a REST API service that accepts requests on +

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FieldTypeDescription
typestringQuota limiter type, either user_limiter or cluster_limiter
namestringHuman readable quota limiter name
initial_quotaintegerQuota set at beginning of the period
quota_increaseintegerDelta value used to increase quota when period is reached
periodstringPeriod specified in human readable form
+

QuotaSchedulerConfiguration

+

Quota scheduler configuration.

+ + + + + + + + + + + + + + + +
FieldTypeDescription
periodintegerQuota scheduler period specified in seconds
+

RHIdentityConfiguration

+

Red Hat Identity authentication configuration.

+ + + + + + + + + + + + + + + +
FieldTypeDescription
required_entitlementsarrayList of all required entitlements.
+

SQLiteDatabaseConfiguration

+

SQLite database configuration.

+ + + + + + + + + + + + + + + +
FieldTypeDescription
db_pathstringPath to file where SQLite database is stored
+

ServiceConfiguration

+

Service configuration.

+

Lightspeed Core Stack is a REST API service that accepts requests on a specified hostname and port. It is also possible to enable authentication and specify the number of Uvicorn workers. When more workers are specified, the service can handle requests concurrently.

- ----- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + +
FieldTypeDescription
hoststringService hostname
portintegerService port
auth_enabledbooleanEnables the authentication subsystem
workersintegerNumber of Uvicorn worker processes to start
color_logbooleanEnables colorized logging
access_logbooleanEnables logging of all access information
tls_configTransport Layer Security configuration for HTTPS support
corsCross-Origin Resource Sharing configuration for cross-domain + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - - -
FieldTypeDescription
hoststringService hostname
portintegerService port
auth_enabledbooleanEnables the authentication subsystem
workersintegerNumber of Uvicorn worker processes to start
color_logbooleanEnables colorized logging
access_logbooleanEnables logging of all access information
tls_config + Transport Layer Security configuration for HTTPS support
cors + Cross-Origin Resource Sharing configuration for cross-domain requests
-

TLSConfiguration

-

TLS configuration.

-

Transport Layer Security (TLS) is a cryptographic protocol designed +

+

TLSConfiguration

+

TLS configuration.

+

Transport Layer Security (TLS) is a cryptographic protocol designed to provide communications security over a computer network, such as the Internet. The protocol is widely used in applications such as email, instant messaging, and voice over IP, but its use in securing HTTPS remains the most publicly visible.

-

Useful resources:

- - ----- - - - - - - - - - - - - - - - - - - - - - - + +
FieldTypeDescription
tls_certificate_pathstringSSL/TLS certificate file path for HTTPS support.
tls_key_pathstringSSL/TLS private key file path for HTTPS support.
tls_key_passwordstringPath to file containing the password to decrypt the SSL/TLS private +

Useful resources:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + - - -
FieldTypeDescription
tls_certificate_pathstringSSL/TLS certificate file path for HTTPS support.
tls_key_pathstringSSL/TLS private key file path for HTTPS support.
tls_key_passwordstringPath to file containing the password to decrypt the SSL/TLS private key.
-

UserDataCollection

-

User data collection configuration.

- ----- - - - - - - - - - - - - + +
FieldTypeDescription
feedback_enabledbooleanWhen set to true the user feedback is stored and later sent for +
+

UserDataCollection

+

User data collection configuration.

+ + + + + + + + + + + + + + + + + + - - - - - + + + + - - - - - + + + + - - - - - + + + + - - -
FieldTypeDescription
feedback_enabledbooleanWhen set to true the user feedback is stored and later sent for analysis.
feedback_storagestringPath to directory where feedback will be saved for further +
feedback_storagestringPath to directory where feedback will be saved for further processing.
transcripts_enabledbooleanWhen set to true the conversation history is stored and later sent +
transcripts_enabledbooleanWhen set to true the conversation history is stored and later sent for analysis.
transcripts_storagestringPath to directory where conversation history will be saved for +
transcripts_storagestringPath to directory where conversation history will be saved for further processing.
- +
+