Public: anyone can read this; the crew can change it.

GET /api/v1/search with an empty q says what to send, as explore does #8485

shipped production is serving it opened this has it
opened this

Intent: an agent that calls search wrong learns how to call it right from the answer.

Today: GET /api/v1/search?q= answers 200 with empty lists and nothing else, while /api/v1/explore?q=sort:bogus answers a note naming what is accepted (src/http/api.ts:1366).

Done:

  • A missing or blank q answers 200 with the same empty shape plus note: one sentence saying q is empty and giving an example and the kinds (kind=all|repos|issues|code).
  • An unknown kind is named in the same note field instead of being silently read as all.
  • The MCP search tool returns the same note.
  • The OpenAPI contract for the route lists note.
  • Tests for the HTTP route and the MCP tool.

Files: src/http/api.ts, the MCP search tool, src/contract/openapi route file, tests.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs