[ENG-4083, ENG-4077] fix(ApiKeyAuth): add persistent label to API key field#1618
Merged
Conversation
Customer feedback noted it was unclear that the API key input is for an
API key, since the field only had a placeholder that disappears on focus
or typing.
Render the API key field with the same DocsHelperTextHeader UI used by the
metadata inputs in the same form: a persistent "{Provider} API Key" header
with the docs link folded into a "Help" expander. Covers both the initial
setup and update-connection flows via the shared ApiKeyAuthForm.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The docs link previously rendered as a bare "Learn more →" inside the
Help expander, which was vague. Pass a prompt to DocsHelperTextHeader so
the expanded Help reads "Where to find your {Provider} API key: Learn
more →". Gated on docsURL so providers without docs show no expander.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
- API key field placeholder now reads "Paste your API key here" instead of the terse "API Key". - Lowercase the "learn more →" docs link in DocsHelperTextHeader so it reads naturally inline (applies to API key and metadata field help). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
dionlow
changed the title
anushat05
approved these changes
Jun 23, 2026
dionlow
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context
Customer feedback: in the API key connection flow, it's unclear that the input field is for an API key. The field previously had only a placeholder (
placeholder="API Key") and no persistent label — so the only indication disappeared as soon as the user typed, focused the field, or a password manager pre-filled it.Change
Render the API key field with the same UI as the metadata inputs in the same form — wrapping a
DocsHelperTextHeaderabove thePasswordInput, mirroringMetadataInput:docsURLis folded into the header's "Help" expander (omitted automatically when there's no docs URL), replacing the old always-visible "Learn more about where to find your {provider} API key." text.The edit is in the shared
ApiKeyAuthForm, so it covers both API key flows:ApiKeyAuthContent)UpdateApiKeyConnect)Verification
docsURLexists and is omitted otherwise; the header persists on focus/typing; and the same header appears in the update-connection flow.