Repository navigation
fix(search): stop collecting task context in CLI search - #315
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 4 files
Confidence score: 5/5
- Automated review surfaced no issues in the provided summaries.
- No files require special attention.
Shadow auto-approve: would auto-approve. Stops forwarding the CLI search --objective flag to the API while still accepting it for legacy scripts, and removes it from SearchOptions. Bounded compatibility-preserving fix with tests verifying objective is omitted and clientModel is preserved.
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 4 files (changes from recent commits).
Confidence score: 5/5
- Automated review surfaced no issues in the provided summaries.
- No files require special attention.
Shadow auto-approve: would require human review. Stops CLI search from forwarding --objective and --client-model, hides both flags while still accepting them, and removes the fields from SearchOptions. This extends the prior approval by also dropping clientModel; live hosted-backend validation is still pending.
View guided diff | Turn on auto-fix | Re-trigger cubic
1 participant
Hide Search's
--objectiveand--client-modelflags and stop forwarding their values to the API. Continue accepting both legacy flags so existing scripts keep working. Remove both fields from the Search options type; feedback objectives and non-search model fields are unchanged.Validation: build, typecheck, formatting, and 123 targeted search/feedback checks passed. A built-CLI process check against a local HTTP fixture confirmed calls with neither, either, and both legacy flags succeed, search help and outbound bodies omit both fields, and feedback help retains its objective. Live hosted-backend validation remains pending.