docs(search): document SearXNG setup#2435
Conversation
📝 WalkthroughWalkthroughDocumentation adds an optional self-hosted SearXNG path for native Web Search, expands the web-search feature doc with registration, endpoint, configuration and error behavior details, and updates the native-tools index and privacy/security pages to clarify managed proxy default vs optional SearXNG routing. ChangesSelf-hosted SearXNG Web Search Documentation
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@gitbooks/features/native-tools/README.md`:
- Line 28: Update the statement that all network tools route through the
OpenHuman proxy to qualify it as the default behavior (e.g., add "by default" or
"unless self-hosted/opted-out") so it no longer contradicts the optional
self-hosted SearXNG mention; adjust the sentence near the network-tools
description that currently implies unconditional proxying (referenced alongside
the "Web Search" table row) to explicitly say the proxy is used by default and
note the self-host/opt-out option.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 7da08c44-1763-435d-b441-645ad6b55fd5
📒 Files selected for processing (3)
gitbooks/features/native-tools/README.mdgitbooks/features/native-tools/web-search.mdgitbooks/features/privacy-and-security.md
Summary
searxng_searchtool on the user-facing Web Search page.config.tomland environment examples for enabling self-hosted SearXNG search.Problem
Issue #1842 asks for SearXNG as a native tool. The implementation is already present on
main, but the feature docs still describe only the managed web-search proxy. Users running a private SearXNG instance would not know how to enable or call the existing tool from the feature docs.Solution
gitbooks/features/native-tools/web-search.md.searxng_searchis listed for MCP clients.Submission Checklist
Closes #NNN: N/A, this documents existing Feature Request : SearXNG as a native MCP tool integration for private, self-hosted web search #1842 implementation but does not itself add the runtime feature.Impact
No runtime behavior changes. Users and MCP clients get a discoverable setup path for the existing self-hosted SearXNG search tool.
Related
AI Authored PR Metadata (required for Codex/Linear PRs)
Linear Issue
Commit & Branch
codex/1842-searxng-docs7eadfb6ddf0584b90b825874a3e85e0e679ea8fdValidation Run
git diff --checkrg -n "SearXNG|searxng_search|OPENHUMAN_SEARXNG|MCP Server" gitbooks/features/native-tools/web-search.md gitbooks/features/native-tools/README.md gitbooks/features/privacy-and-security.mdpnpm --filter openhuman-app format:check: N/A, docs-only change; not run in this isolated worktree.pnpm typecheck: N/A, docs-only change.Validation Blocked
command:N/Aerror:N/Aimpact:N/ABehavior Changes
Parity Contract
Duplicate / Superseded PR Handling
Summary by CodeRabbit