KnockOutEZ/wigolo

First off — thanks for wigolo. We ran it seriously for a local-first, keyless research/search setup and it's been a genuinely great fit. Filing this because the failure mode below is silent and worth surfacing. Environment Host: Apple Silicon macOS, container runtime OrbStack Container: linux/arm64, image ghcr.io/knockoutez/wigolo Version: v0.2.1 Deploy path: packaging/compose.serve.yml Steps to reproduce On an arm64 host (Apple Silicon Mac), run the serve container via packaging/compose.serve.yml. Run a search query through the running daemon/REST API. Check the daemon logs — you'll see the embedding model fail to load a native binding. Compare against running wigolo natively on macOS arm64 (Darwin binding present) — vector-similarity ranking is active there. Expected Embedding/vector-similarity ranking works inside the container on an arm64 host, matching native macOS arm64 behavior. Actual @anush008/tokenizers-linux-arm64-gnu is missing from the ARM64 Docker image. The emb

What happened? An opt-in env var (WIGOLO_CHROME_PROFILE_PATH, meant for authenticated fetches) copies your entire actual Chrome profile - cookies, saved logins, history - to a temp folder, and that copy is never used by the code that's supposed to consume it (dead code path) and never cleaned up. privacy leak, but only if you deliberately set that specific variable since default install never touches it. WIGOLO_CDP_URL with self launched chrome works. I didn't experience this bug, claude code found it while I had it check it before installing, just FYI. Command / tool call No response wigolo version 0.1.43-beta.0 OS + Node version win11 Output of npx wigolo doctor (if relevant) Logs / error output

wigolo has a plugin system (wigolo plugin add <git-url>) for custom extractors and search engines, but there's no in-repo example showing the minimal shape of one. A tiny examples/plugin-search-engine/ that people can copy is the easiest possible on-ramp for contributors. Where to look Plugin loader/validation: src/plugins/ (loader, registry, validation define the expected plugin shape) Acceptance examples/plugin-search-engine/ with a minimal working plugin (any simple public JSON API is fine) + a short README explaining install via wigolo plugin add Loads cleanly through wigolo plugin add / plugin list A line in the main README's Contributing section pointing at it

wigolo's code search vertical fans queries across engine adapters — adding one is a well-contained ~100-line PR, and the npm registry has a clean public JSON API (https://registry.npmjs.org/-/v1/search?text=...), so there's no scraping involved. Where to look Reference adapter: src/search/engines/mojeek.ts (implements the SearchEngine interface — name + search() returning RawSearchResult[]) src/search/engines/hn-algolia.ts is another good API-based example Register it in the code vertical: src/search/core/verticals/code.ts Acceptance New src/search/engines/npm-registry.ts adapter, registered in the code vertical Respects timeoutMs / maxResults options like the other adapters Unit test alongside the existing engine tests npm test and npm run lint green Questions welcome in the thread — happy to point at anything.