Local Ai Search

What to consider before installing: - Incoherent metadata: the registry says no env vars/credentials are required, but the skill and its config files expect and use API keys (OPENAI_API_KEY, ANTHROPIC_API_KEY, KHOJ_API_KEY) and a KHOJ_URL. Treat that as a red flag: the skill will ask you to provide secrets even though metadata does not advertise that need. - Data flow and exfiltration risk: by default the scripts upload converted file contents to a Khoj API (http://localhost:42110). That is fine if Khoj runs locally. But if you set KHOJ_URL or LLM provider base URL to a remote server (or misconfigure the base_url), the skill will send your converted documents and query context to that remote service and to cloud LLM providers. Only provide API keys or point KHOJ_URL to hosts you trust. - Persistence: the skill can install cron jobs (schedule_sync.sh) and writes state/logs under ~/.khoj. If enabled, syncs will run periodically and continue uploading new/changed files. Review the schedule script before enabling and verify the cron entry before trusting it. - Review and sandbox: because the package contains executable scripts that read arbitrary directories and make HTTP requests, inspect the code yourself (or run it in an isolated VM/container) before pointing it at sensitive files. Confirm KHOJ_URL remains localhost and do not export API keys to the environment unless you intend cloud processing. - Least privilege: if you do use this skill, create a dedicated, minimal directory for indexing first (not your entire home), test conversion and indexing there, and verify network traffic (e.g., via netstat/tcpdump) to ensure uploads go only where you expect. - What would change this assessment: if the registry metadata were updated to explicitly declare all required env vars and their purposes (and require user consent before enabling scheduled sync), or if the package came from a verifiable homepage/repo with a release signature, I would consider the incoherence resolved and raise confidence toward benign. Conversely, evidence that the default KHOJ_URL points to a remote, unknown host would increase severity. Recommended immediate actions: 1) Inspect config.yaml and make sure llm.provider and base_url are what you expect (prefer local/localhost). 2) Do not export API keys globally; use them only for trusted providers and ephemeral test runs. 3) Run the scripts in a sandbox and monitor network activity before pointing the tool at sensitive directories. 4) If you do not understand or cannot audit the code, avoid granting it access to your entire home directory or enabling cron syncing.