Repository navigation
fix(search): remove task context from MCP search inputs - #531
Conversation
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
No issues found across 13 files
Confidence score: 5/5
- Automated review surfaced no issues in the provided summaries.
- No files require special attention.
Requires human review: Removes objective from the advertised MCP firecrawl_search schema and outbound /v2/search bodies while tolerating legacy input. This is a public contract change and live backend end-to-end validation is still pending, so human sign-off is needed.
View guided diff | Turn on auto-fix | Re-trigger cubic
capy-ai
Bot
changed the title
There was a problem hiding this comment.
0 issues found across 13 files (changes from recent commits).
Confidence score: 5/5
- Automated review surfaced no issues in the provided summaries.
- No files require special attention.
Requires human review: Removes objective and clientModel from the public MCP search schema and outbound /v2/search requests, while discarding legacy inputs for compatibility. This is a public contract and backend-behavior change, and live hosted-backend validation remains pending.
View guided diff | Turn on auto-fix | Re-trigger cubic
Remove
objectiveandclientModelfrom all advertised MCP Search schemas and outbound search requests. Discard legacy values before strict search-surface validation so cached clients continue to work. Feedback objectives, non-search model metadata, and extension hooks are unchanged.Validation: build, lint, typecheck, and targeted search, contract, feedback-hint, and extension-hook checks passed locally. MCP transport checks use a stubbed API backend; live hosted-backend validation remains pending.