Describe the bug
When configuring ElevenLabs for Voice Dictation in Goose Desktop, the API key appears to save successfully (UI shows "configured" in green text) but does not actually persist. Upon returning to Chat mode, the microphone icon displays an error: "ElevenLabs API Key is not configured. Set it up in Settings > Chat > Voice Dictation."

📦 To help us debug faster, attach your diagnostics zip if possible.

diagnostics_20251211_3.zip

To Reproduce
Steps to Reproduce

1. Open Goose Desktop
2. Navigate to Settings > Chat > Voice Dictation
3. Select ElevenLabs as the voice dictation provider
4. Enter a valid ElevenLabs API key in the provided field
5. Click outside the API key field
6. Observe "configured" appears in green text (suggesting successful save)
7. Return to Chat mode
8. Click the microphone icon

Expected behavior
The ElevenLabs API key should persist after being entered, and voice dictation should function when clicking the microphone icon in Chat mode.

Actual Behavior

• The UI incorrectly indicates the key is "configured"
• The key is not saved to any persistent storage
• Returning to Chat mode shows error: "ElevenLabs API Key is not configured. Set it up in Settings > Chat > Voice Dictation."
• The issue persists across app restarts

Screenshots
No screenshots.

System & app information

• OS & Arch: [macOS 14.7.6, Intel]
• Interface: [GUI]
• Version: [Version 1.16.1 (1.16.1)]
• Extensions enabled: [Auto Visualiser, Chatrecall, Computer Controller, Developer, Extension Manager, Memory, Skills, Todo, Tutorial]
• Provider & Model: [anthropic/claude-opus-4.5]
• ElevenLabs Account Type: [Free]

Additional context
Investigation Notes
Checked the following storage locations - none contain the ElevenLabs API key after configuration:

~/.config/goose/config.yaml - No ElevenLabs entries
macOS Keychain - No ElevenLabs-related entries found
~/Library/Application Support/Goose/ local storage - No ElevenLabs data
Manually adding ELEVENLABS_API_KEY to config.yaml did not resolve the issue.

Additional Context
The UI state ("configured" indicator) appears to be disconnected from the actual persistence mechanism. The key may be stored in component state but never written to disk or keychain.