feat: default search to Kagi - #69
Merged
Merged
Conversation
Kagi (https://kagi.com/search?q=) becomes the default search engine everywhere TronBrowser picks one: - Omnibox: the launcher's once-per-profile default_search_provider_data now seeds Kagi. The sentinel filename carries the engine name (.tron-search-kagi), so profiles created under the old NeoSearch default get the new default applied once, and a user's own chrome://settings/search choice is still respected afterwards. - New tab (ai-sidebar): Kagi is added to SEARCH_ENGINES, is the initial value of searchEngine, and is the fallback for an unknown stored id. - Settings (extension options + web): Kagi is the first option and is labelled the default; the stored-value fallback now resolves to kagi. - Mobile: the in-app browser's address-bar search falls back to Kagi. NeoSearch, Xprivo, DuckDuckGo, Altpower, and Oxiverse remain available as alternatives, and the Tor engine list is untouched. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
vu1nz Security Review0 finding(s) in PR #? No security issues found. |
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
1 participant
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.
Makes Kagi (
https://kagi.com/search?q=) the default search engine everywhere TronBrowser picks one.Changes
apps/desktop/launcher/tronbrowser) — the once-per-profiledefault_search_provider_dataseed now points at Kagi (suggestions_url→https://kagi.com/api/autosuggest?q={searchTerms}). The sentinel filename carries the engine name (.tron-search-kagi), so profiles created under the old NeoSearch default pick the new default up once; a user's ownchrome://settings/searchchoice is still respected afterwards.ai-sidebar/newtab.js) —kagiadded toSEARCH_ENGINES, is the initialsearchEngine, and is the fallback when a stored id is unknown. Placeholder and quick links updated.options.html+ websettings.html, and bothsettings-sections.js) — Kagi is the first option and labelled the default; the stored-value fallback resolves tokagi.apps/mobile/src/lib/navigation.ts) — the in-app browser's address-bar search falls back to Kagi. Tests updated.NeoSearch, Xprivo, DuckDuckGo, Altpower, and Oxiverse remain available as alternatives; the Tor engine list is untouched.
Verification
pnpm buildthenpnpm test— full workspace green (mobile 6/6, desktop 113, api 62, browser-core 12, plus the rest).pnpm lint— exit 0 (36 pre-existingno-explicit-anywarnings inservices/api, untouched).bash -n apps/desktop/launcher/tronbrowser— clean.Note
Kagi requires a signed-in account; signed-out users hit Kagi's landing page rather than results. Flagging in case the alternatives should be reordered for signed-out users.
🤖 Generated with Claude Code