API keys visible in settings

[fvangils]

Awesome product! Love it so far!

Bug Description (required)

When storing the API key, it remains visible in the settings. Also after saving and returning.

Screenshot (recommended)

System Information

• Dyad Version: 0.43.0
• Platform: darwin
• Architecture: arm64
• Node Version: v22.22.2
• PNPM Version: 10.33.0
• Node Path: /Users/fransanton/.nvm/versions/node/v22.22.2/bin/node
• Pro User ID: n/a
• Telemetry ID: 255a699f-55d4-43ea-a29b-911691e973e8
• Model: auto:auto | customId: undefined

Settings

• Selected Model: auto:auto
• Chat Mode: build
• Auto Approve Changes: n/a
• Dyad Pro Enabled: n/a
• Thinking Budget: n/a
• Runtime Mode: n/a
• Release Channel: stable
• Auto Fix Problems: false
• Native Git: true

Logs

  providerCount: 6
}
  source: 'remote',
  version: '2026-04-12T04:47:58.835Z',
  expiresAt: '2026-04-12T05:47:58.835Z'
}
  source: 'remote',
  version: '2026-04-12T04:47:58.835Z',
  providerCount: 6
}
  source: 'remote',
  version: '2026-04-12T04:47:58.835Z',
  expiresAt: '2026-04-12T05:47:58.835Z'
}
  providerId: 'openai',
  source: 'remote',
  version: '2026-04-12T04:47:58.835Z',
  hasProviderModels: true
}

[rsharma2be23-cloud]

Hi, I’d like to work on this issue. Could you assign it to me?

[wwwillchen]

hi @fvangils - we encrypt the api keys locally but then display it for the users in the UI for convenience. Is there a reason why you don't want them visible in the settings?

[fvangils]

Hi @wwwillchen,

Thanks for the context on local encryption — that's a good foundation. The concern is specifically about displaying the decrypted key in the UI by default. Even with encryption at rest, plain-text display creates real exposure vectors: screen sharing, browser extensions, shoulder surfing, and screenshots. The industry-standard pattern is to mask the key (e.g. sk-••••••••••••1234) with an explicit reveal/copy action. It provides the same convenience without the exposure risk. Also wanted to say — really appreciate the work you're putting into DYAD. Great software, and I'm happy to keep sharing feedback as I explore it further. Keep it up! 🙌

[wwwillchen]

hi @fvangils - OK, agree, that makes sense.

@nourzakhama2003 - this might be another good feature for you to work on if you're interested.

[nourzakhama2003]

hi @fvangils - OK, agree, that makes sense.

@nourzakhama2003 - this might be another good feature for you to work on if you're interested.

Hi @wwwillchen , I'm interested That sounds like a good feature to look at . I'll start looking into it . Thanks for the suggestion!