[BUG] `config set` success message is incorrect when key contains spaces

[oxbullyellow]

Project

cortex

Description

When a config key contains spaces (quoted in shell), config set appears to save it, but the success message prints the key/value ambiguously and incorrectly. Example: setting key "abc def" with value abc prints [OK] Set abc def = abc, which looks like multiple tokens and is misleading.

Error Message

Debug Logs

System Information

Linux 6.14

Screenshots

Steps to Reproduce

1. Run cortex config set "abc def" abc.
2. Observe success message formatting.

Expected Behavior

Success output should preserve quoting/escaping for keys with spaces (for example: [OK] Set "abc def" = "abc"), so key and value boundaries are unambiguous.

Actual Behavior

Success message prints unquoted key/value text, which is ambiguous and misleading when keys contain spaces.

Additional Context

No response

[echobt]

The issue reports that when setting a configuration key containing spaces, the success message prints the key and value without quotes, making it ambiguous (e.g., [OK] Set abc def = abc).

The screenshot provided is authentic, shows the CLI interface, and clearly demonstrates the reported bug.

I verified the codebase by searching for the success message format. In src/cortex-cli/src/cli/handlers.rs around line 861, the code is:

print_success(&format!("Set {} = {}", args.key, args.value));

This confirms that the key and value are printed directly without any surrounding quotes or escaping, which matches the reported behavior.

No exact duplicates were found (the similar issues are related to config set/get but describe different specific bugs like invalid TOML generation or inconsistent wording).

Therefore, the bug is valid and verified.