No consumer complaints found — Keenable's bad press is six engineering traces, five of them the same missing-text defect

Question asked: find all mentions of someone using Keenable and having a bad experience. Broad web, forum, review, social, and GitHub searches (hundreds of unique hits reviewed, as of 30 Aug 2026) surfaced no first-person consumer review — only bug reports, integration docs, corrective commits, and one configuration error.

Evidence base: 6 distinct negative mentions across 4 affected projects, each verified against a public page.

direct bug report known-defect documentation corrective commit configuration error outlined = the repeated missing-text defect

The single recurring defect — results arrive as titles and links with no page text, from reading description instead of snippet — appears in 5 of the 6 mentions across three separate codebases. github.com

Ketch shipped the defect but documents a workaround: pass --scrape until PR #43 lands; Omnigent documents no workaround while PR #5020 is open. docs.keenable.ai

CrewAI already fixed both of its issues in the merged PR #6279 — reading text from the snippet field and rejecting a negative n_results. github.com

The only non-project mention is an error reference: a ValueError when KEENABLE_API_URL is not a usable HTTPS URL — user configuration, not product failure. errors.standardbeagle.com

Project	Type	Verified quote	Resolution	Source

Method: broad web, forum, review, social, and GitHub searches for negative Keenable mentions, reviewed as of 2026-08-30; hundreds of unique hits screened down to 6 defensible items across 3 result sets. Each row is one distinct mention; the two CrewAI rows are separate corrective commits inside one pull request, and duplicate descriptions of the Omnigent missing-text defect were collapsed to one issue plus one documentation entry. Dates shown where the page carries one. Coverage is limited to publicly indexed pages; no claim of exhaustiveness.