UX: Save individual too calls to preferences.yaml

[ccmitchellusa]

FEATURE

During tool call confirmations
Provide tool confirmation option (in addition to the current [y/n] options):

• [d]on't ask next time this tool is called

Add additional sub-commands to manage the tool call confirmation preferences (as applied to the current config):

• /confirm tool_calls - Toggle tool call confirmations globally (on by default). Previous individual tool call preferences will be cleared.
• /confirm tool_calls verbose - Toggle tool call details are shown for tools marked as NEVER confirm
• /confirm tool_calls list - List current tool call confirmation preferences (ALWAYS|NEVER)
• /confirm tool_calls toggle TOOL_NAME - Toggles whether a tool will always or never be confirmed before execution

Add ability to store user preferences in a preferences.yaml file.

[ccmitchellusa]

@chrishayuk I see that there is code in ModelManager to read ~/.mcp-cli/preferences.yaml (containing model, provider) settings.

Is this file where additional ui preferences like tool call confirmations, display options, etc. can be persisted?
Do you have thoughts on how you want to manage preferences (load/save/set) in general (maybe with a /prefs command?

I'd like to add the auto-confirm-tool call (per-tool call settings) like:

./mcp-cli/preferences.yaml

provider: open-ai
model: gpt-4o-mini
auto-accept-tools:
    - stdio.ibmcloud_target
    - stdio.ibmcloud_resource_groups