Repository navigation
Closed
Labels
P1Priority 1: current iteration goalPriority 1: current iteration goalcampaign:0.1.8-beta30.1.8 Beta3 generic advanced-tool workflows campaign0.1.8 Beta3 generic advanced-tool workflows campaignenhancementNew feature or requestNew feature or requestready-for-agentFully specified, ready for an AFK agentFully specified, ready for an AFK agenttier:heavyOrchestrator provider tier: heavyOrchestrator provider tier: heavywayfinder:taskWayfinder implementation taskWayfinder implementation task
Description
Parent
Outcome
Implement the generic protocol adapter for Codex client-executed tool_search.
The implementation is derived from the runtime declaration and selected upstream protocol. It must not depend on Provider or model names.
Required behavior
- Preserve
tool_searchnatively when the selected protocol can carry the Codex shape. - Otherwise encode it through one reversible request-scoped representation.
- Inverse-map search call, search output, discovered declarations, subsequent call/result, streaming events, and replay history.
- Preserve IDs, ordering, and declaration identity.
- Keep hosted search separate: it is available only when the already-selected Provider supports it and is never used as a substitute.
Acceptance criteria
- Deterministic protocol fixtures cover native and adapted declaration/call/output/history forms.
- Added/delta/done event ordering is assembled before final validation.
- Unknown aliases, collisions, malformed output, missing/duplicate IDs, and ambiguous inverse mapping fail safely.
- No model-name or maintained-Provider branch selects the Adapter.
- No request reaches a second Provider.
- Diagnostics contain no prompt, tool arguments/results, credentials, call IDs, or user content.
Blocked by
Metadata
Metadata
Assignees
Labels
P1Priority 1: current iteration goalPriority 1: current iteration goalcampaign:0.1.8-beta30.1.8 Beta3 generic advanced-tool workflows campaign0.1.8 Beta3 generic advanced-tool workflows campaignenhancementNew feature or requestNew feature or requestready-for-agentFully specified, ready for an AFK agentFully specified, ready for an AFK agenttier:heavyOrchestrator provider tier: heavyOrchestrator provider tier: heavywayfinder:taskWayfinder implementation taskWayfinder implementation task
Activity
[-]0.1.8 Beta2: Prove the GLM-5.2 explicit-hint tool_search lifecycle[/-][+]0.1.8 Beta3: Prove the GLM-5.2 explicit-hint tool_search lifecycle[/+][-]0.1.8 Beta3: Prove the GLM-5.2 explicit-hint tool_search lifecycle[/-][+]0.1.8 Beta4: Prove the GLM-5.2 explicit-hint tool_search lifecycle[/+][-]0.1.8 Beta4: Prove the GLM-5.2 explicit-hint tool_search lifecycle[/-][+]0.1.8 Beta3: Implement the generic client tool_search protocol adapter[/+]NOirBRight commentedon Aug 10, 2026
Completion receipt (Beta4 preflight audit, 2026-08-10): the accepted Beta3 implementation candidate is
7006542a773fc20c10e4bbcadd593393a259ceb2; it was promoted inv0.1.8-beta.3and remains in the cumulativev0.1.8-beta.3.3lineage (d1308ce5bd0546993a68579b23102bafde24513a). GitHub Actions remains disabled; local evidence is authoritative.The generic client-owned
tool_searchimplementation and native/adapted lifecycle evidence are recorded indocs/evidence/issue-63/anddocs/evidence/issue-278/. Fresh preflight validation passed withscripts/validate_issue_63_evidence.py --require-final-candidate, the bound #278 summary validator, andtests/test_beta3_protocol_cli_runner.py(12 passed). #63 and the Beta3 gate #281 are closed. Closing this stale child issue as delivered; no Beta4 code work is being added.