Summary
gbrain search is now failing hard on Eva's local install because the AI gateway rejects the google recipe embedding touchpoint missing max_batch_tokens.
This appears related to #88, but the observed behavior is worse than the original "noisy warning" scope: search returns no results and exits non-zero.
Environment
- Machine: Eva origin local Mac
- Repo/context: Paperclip fork work, trying to index/search the new epic doc
- Installed CLI:
gbrain 0.33.0
gbrain doctor --fast --json: status warnings, health score 95
- Legacy
brain CLI is also stale/broken separately; this issue is about gbrain.
Repro
cd /Users/lume/repos/mission-control-paperclip
gbrain search "Eva field of view Paperclip"
Actual
[ai.gateway] recipe "google" declares an embedding touchpoint without max_batch_tokens; recursion is the only safety net for batch caps.
Error: command failed
The command exits non-zero and returns no search results.
Expected
gbrain search should complete successfully. If the active provider is not Google, a Google recipe warning should not break search. If Google is active, the recipe should declare a supported batch cap or an explicit dynamic/no-cap policy.
Notes
gbrain doctor --fast --json output from the same session:
{"schema_version":2,"status":"warnings","health_score":95,"checks":[{"name":"resolver_health","status":"ok","message":"42 skills, all reachable"},{"name":"skill_conformance","status":"ok","message":"42/42 skills pass"},{"name":"sync_failures","status":"ok","message":"2 historical sync failure(s), all acknowledged [UNKNOWN=2]."},{"name":"connection","status":"warn","message":"Skipping DB checks (--fast mode, URL present from config-file-path)"}]}
Acceptance Criteria
gbrain search "Eva field of view Paperclip" exits 0 on Eva origin.
- Google recipe batch-cap warning is either removed from non-Google paths or no longer causes command failure.
- Add/update a regression test covering search startup/config validation when inactive recipes have embedding touchpoints.
Summary
gbrain searchis now failing hard on Eva's local install because the AI gateway rejects thegooglerecipe embedding touchpoint missingmax_batch_tokens.This appears related to #88, but the observed behavior is worse than the original "noisy warning" scope: search returns no results and exits non-zero.
Environment
gbrain 0.33.0gbrain doctor --fast --json: statuswarnings, health score95brainCLI is also stale/broken separately; this issue is aboutgbrain.Repro
Actual
The command exits non-zero and returns no search results.
Expected
gbrain searchshould complete successfully. If the active provider is not Google, a Google recipe warning should not break search. If Google is active, the recipe should declare a supported batch cap or an explicit dynamic/no-cap policy.Notes
gbrain doctor --fast --jsonoutput from the same session:{"schema_version":2,"status":"warnings","health_score":95,"checks":[{"name":"resolver_health","status":"ok","message":"42 skills, all reachable"},{"name":"skill_conformance","status":"ok","message":"42/42 skills pass"},{"name":"sync_failures","status":"ok","message":"2 historical sync failure(s), all acknowledged [UNKNOWN=2]."},{"name":"connection","status":"warn","message":"Skipping DB checks (--fast mode, URL present from config-file-path)"}]}Acceptance Criteria
gbrain search "Eva field of view Paperclip"exits 0 on Eva origin.