Skip to content

Replace Brave Search with Grok for the LLM-shaped route - #36

Merged
bradflaugher merged 1 commit into
mainfrom
feat/restore-grok-search
Jun 11, 2026
Merged

bradflaugher merged 1 commit into
mainfrom
feat/restore-grok-search

Conversation

@bradflaugher

Copy link
Copy Markdown
Owner

Summary

  • Swap the LLM-shaped routing destination from Brave Search's Ask endpoint back to Grok (https://grok.com/?q={q}), reversing 3e341f7 on top of the current (post-overhaul) corpus — Grok is the better fit for longer agentic questions
  • Rename the engine key bravegrok in scripts/search_phrases.json (engine def, bangs !g !gr !p !px, 5 keyword rules, 176-phrase route) and in the 87 benchmark labels; natural-language uses of "brave" in corpus phrases are untouched
  • Regenerate search-config.json + search-embeddings.json (823 vectors) and bump EMBEDDINGS_VERSION to 16
  • Update Playwright host assertions to grok.com and the README engine table

Validation

  • python3 scripts/eval_routing.py: semantic 98.9% (349/353), keyword/lite 97.5% (344/353) — identical to baseline, same 4 known residual misroutes
  • npm run lint clean (eslint, ruff, config validator)
  • npm test: 173 passed, 11 skipped, including the live keyword-mode navigation test now landing on grok.com

🤖 Generated with Claude Code

Swap the brave engine back to Grok (https://grok.com/?q={q}) across the
corpus, benchmark labels, generated config/embeddings, tests, and README.
Brad uses Grok for longer agentic questions; Brave had replaced it in
3e341f7. Bump EMBEDDINGS_VERSION to 16.

Routing eval unchanged: semantic 98.9%, keyword 97.5% (353-query benchmark).
All 173 Playwright tests pass.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@bradflaugher
bradflaugher merged commit 3b73289 into main Jun 11, 2026
7 checks passed
@bradflaugher
bradflaugher deleted the feat/restore-grok-search branch June 11, 2026 10:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant