feat: add Extension settings category with auth token copying and browser integration support#341
Merged
SuperCoolPencil merged 3 commits intomainfrom Apr 10, 2026
Merged
Conversation
…wser integration support
Binary Size Analysis
|
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
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.
Greptile Summary
This PR adds a new Extension settings tab to the TUI, moving
ExtensionPromptfrom General into a dedicatedExtensionSettingsstruct, and adding auth-token display/copy-to-clipboard and browser-extension installation links. TheAuthTokenfield is deliberately excluded from JSON serialization viajson:"-"and is read from the state file viaInitAuthToken()at startup.The three commits address the previous round's feedback (removed dead
ExtensionTokenCopyTimer, fixed JSON exclusion of the auth token, and corrected theExtensionPromptfield location). Overall the feature is well-structured and handles the main user flows correctly.Confidence Score: 5/5
Safe to merge; all remaining findings are P2 style/quality suggestions that do not block correct runtime behaviour.
The three previous round findings have all been addressed: AuthToken is now json:"-", ExtensionTokenCopyTimer has been removed, and ExtensionPrompt has been relocated correctly. The two remaining issues (the "-" key produced by json:"-" in metadata, and missing unit tests for new TUI actions) are non-breaking quality improvements.
internal/config/settings.go (json:"-" key extraction) and internal/tui/view_settings.go (same pattern in getSettingsValues at line 593)
Important Files Changed
Flowchart
%%{init: {'theme': 'neutral'}}%% flowchart TD A([User presses Enter on Extension tab]) --> B{getCurrentSettingType} B -->|auth_token| C[GetAuthToken from cache] C --> D{token empty?} D -->|yes| E[return nil, no-op] D -->|no| F[clipboard.Write token] F --> G[ExtensionTokenCopied = true] G --> H[tea.Tick 2s → extensionTokenFlashFadeMsg] H --> I[ExtensionTokenCopied = false\nUI returns to truncated token display] B -->|link| J[getSettingsValues for category] J --> K[utils.OpenBrowser url] B -->|bool| L[toggle value via setSettingValue] B -->|string/int/etc| M[enter edit mode\nSettingsIsEditing = true]Prompt To Fix All With AI
Reviews (2): Last reviewed commit: "style: increase settings modal width and..." | Re-trigger Greptile