Log level

Set the log level for the MTA binary. The default log level is debug. The log level increases or decreases the verbosity of logs.

RPC Server Path

Displays the path to the solution server binary. If you do not modify the path, Developer Lightspeed for MTA uses the bundled binary.

Analyzer path

Specify a MTA custom binary path. If you do not provide a path, Developer Lightspeed for MTA uses the default path to the binary.

Solution Server:URL

Configure the URL of the Solution Server end point. This field has the default URL.

Solution Server:enabled

Enable the Solution Server client (MTA extension) to connect to the Solution Server to perform analysis.

Solution Server:Auth

Enable authentication for the Solution Server.

Solution Server:Auth Realm

Enter the name of the Keycloak realm for Solution Server.

If you enabled authentication for the Solution Server, you must configure a Keycloak realm to allow clients to connect to the Solution Server. An administrator can configure SSL for the realm.

Solution Server: Auth Insecure

This option is enabled by default to skip SSL certificate verification when clients connect to the Solution Server. Disable the setting to allow secure connections to the Solution Server.

Analyze on save

Enable this setting for Developer Lightspeed for MTA to run an analysis on a file that is saved after code modification. This setting is enabled automatically when you enable Agentic AI mode.

Diff editor type

Select from diff or merge view to review the suggested solutions after running an analysis. The diff view shows the old code and a copy of the code with changes side-by-side. The merge view overlays the changes in the code in a single view.

Gen AI:Enabled

This option is enabled by default. It enables you to get code fixes by using Developer Lightspeed for MTA with a large language model.

Diff:Auto Accept On Save

This option is enabled by default. When you accept the changes suggested by the LLM, the updated code is saved automatically in a new file. Disable this option if you want to manually save the new file after accepting the suggested code changes.

Agent mode

Enable the experimental Agentic AI flow for analysis. Developer Lightspeed for MTA runs an automated analysis of a file to identify issues and suggest resolutions. After you accept the solutions, Developer Lightspeed for MTA makes the changes in the code and re-analyzes the file.

Excluded diagnostic sources

Add diagnostic sources in the settings.json file. The issues generated by such diagnostic sources are excluded from the automated Agentic AI analysis.

Cache directory

Specify the path to a directory in your filesystem to store cached responses from the LLM.

Demo mode

Enable to run Developer Lightspeed for MTA in demo mode that uses the LLM responses saved in the cache directory for analysis.

Trace enabled

Enable to trace MTA communication with the LLM model. Traces are stored in the /.vscode/konveyor-logs/traces path in your IDE project.

Debug:Webview

Enable debug level logging for Webview message handling in VS Code.

Analyze dependencies

Enable Developer Lightspeed for MTA to analyze dependency-related errors detected by the LLM in your project.

Analyze known libraries

Enable Developer Lightspeed for MTA to analyze well-known open-source libraries in your code.

Code snip limit

Set the maximum number of lines of code that are included in incident reports.

Context lines

Configure the number of context lines included in incident reports. The greater the number, the more the LLM accuracy.

Incident limit

Specifies the maximum number of incidents to be reported. If you enter a higher value, it increases the coverage of incidents in your report.

Select profile

Create a profile that you can reuse for multiple analyses. The profile name is part of the context provided to the LLM for analysis.

Configure label selector

A label selector filters rules for analysis based on the source or target technology.

Specify one or more target or source technologies (for example, cloud-readiness). Developer Lightspeed for MTA uses this configuration to determine the rules that are applied to a project during analysis.

If you mentioned a new target or a source technology in your custom rule, you can type that name to create and add the new item to the list.

Set rules

Enable default rules and select your custom rule that you want MTA to use for an analysis. You can use the custom rules in addition to the default rules.

Configure generative AI

This option opens the provider-settings.yaml file that contains API keys and other parameters for all supported LLMs. By default, Developer Lightspeed for MTA is configured to use OpenAI LLM. To change the model, update the anchor &active to the desired block. Modify this file with the required arguments, such as the model and API key, to complete the setup.