Config Values Being Double-Quoted 🐛

The user also reported this warning in logs:

WARN goose::providers::codex: Invalid CODEX_REASONING_EFFORT '"medium"', using 'high'

Note the double quotes around medium - the value is being stored/read as "medium" instead of medium.

The user confirmed:

• goose config shows CODEX_REASONING_EFFORT: medium (correct)
• But the provider receives "medium" (with quotes)

This is likely the root cause of the exit code 1 error - if CODEX_COMMAND is also being double-quoted, the path would be invalid.

Additional Issue: Can't Edit Config After First Save

User also noted:

"I can't seem to edit the reasoning effort beyond the first time"

This suggests a UI/config persistence bug where updates aren't being saved properly.

Questions for @fgs

1. Can you check what CODEX_COMMAND shows in your config? Is it also double-quoted?
2. Can you try setting the config via CLI instead of the UI?

   goose configure

3. What does your ~/.config/goose/config.yaml show for any CODEX_* keys?

Root Cause Hypothesis

The config upsert flow from the Desktop UI may be double-serializing string values:

1. Frontend sends JSON: {"value": "medium"}
2. Server receives serde_json::Value::String("medium")
3. When serializing to YAML, it may be writing "medium" (quoted) instead of medium
4. When reading back, the quotes become part of the string value

This would affect all string config values set via the Desktop UI, not just Codex.