@elegant-branch-54423 you might also want to add these to the list (if not reported yet):
1. The CLI cannot be configured using only the keyboard. You are forced to use the mouse, because TAB doesn't work in the LLM settings page so you can't move between the 'controls' when setting the CLI up the first time. Not really expected for a CLI tool to require a mouse to set up.
2. In the LLM settings, there's no difference between enabled/disabled fields, you get those optional fields that look exactly like the others, but you can't type in them, because they only unlock once you scroll to the bottom of the settings and enter the API key. Not really intuitive, unless you know that kind of inherited quirky behavior from the GUI.
3. The API key is still required in the CLI, while it no longer is in the GUI. It makes everything more confusing for local LLMs users, which often do not need an API key for their local LLM server.