Search feature requests semantically
Changed onDedupe-style search across the project's FEATURE_REQUEST tickets. Uses OpenSearch fuzzy match + Voyage AI rerank — returns the most semantically similar matches to the query argument, not literal keyword hits. Use this before filing a new feature request to avoid duplicates.
Returns { matches: [...] } with at most 5 reranked matches, best first, each with its rerank score. Archived feature requests are excluded, and so are hidden lanes unless includeHiddenLanes=true: those matches come back with public: false and no status label or share link (new requests land in the hidden intake lane, so an agent deduping before it files one needs them). When the reranker is unavailable the matches are unranked (score: null) and ranked is false.
Request
- Base URLhttps://api.gleap.io/v3
- URLhttps://api.gleap.io/v3/tickets/search-feature-requests
- AuthHTTP bearer
Query parameters
- Required free-text description of the requested feature.
- Size of the candidate set retrieved before reranking (default: 10). The reranked response is still capped at 5 matches unless minScore=0 is passed.
- Minimum rerank relevance score, 0-1 (default: 0.35). 0 disables reranking and returns up to limit candidates.
- Also return feature requests in hidden lanes, flagged public: false (default: false).
Headers
Response
Ok
Changes
- info
added the new optional
queryrequest parameterincludeHiddenLanes
- info