Repository navigation
0.1.8 Beta2: Approve the custom-endpoint tool compatibility contract #249
Copy link
Copy link
Closed
Labels
P1Priority 1: current iteration goalPriority 1: current iteration goalcampaign:0.1.8-beta20.1.8 Beta2 generic tool compatibility campaign0.1.8 Beta2 generic tool compatibility campaignenhancementNew feature or requestNew feature or requestready-for-humanRequires human implementationRequires human implementationwayfinder:grillingWayfinder decision or reconciliation gateWayfinder decision or reconciliation gate
Description
Parent
Decision scope
Approve the Beta2 custom-endpoint tool compatibility contract before production implementation begins. This is an architecture and release-scope decision, not a per-model GO/PARTIAL/NO-GO gate.
Inputs
- ADR-0002: 0.1.8 Beta2: Record the runtime-derived tool compatibility architecture (ADR-0002) #350
- Exact CLI 0.146 structural inventory: 0.1.8 Beta2: Inventory Codex CLI 0.146 tool types and representative Responses lifecycles #62
- V1/V2 schema boundary: 0.1.8 Beta2: Define the Codex CLI 0.146 Collaboration V1/V2 schema boundary #64
- Tool-type compatibility table: 0.1.8 Beta2: Define tool-type compatibility rules for custom Responses endpoints #65
Decisions to record
- The user-selected Provider/model remains immutable; no compatibility result can choose another model.
- Runtime tools are classified only as
native,adapt,omit, orrequired-but-unavailable. - Adapters apply only to incompatible reversible shapes; already compatible tools remain native.
- Unsupported hosted tools are not exposed and are never proxied through OpenAI or another Provider.
- Tool execution follows declaration type; CodexHub adapts but does not execute tools or schedule agents.
- Unknown custom endpoints use the generic conservative path.
- Maintained Provider regressions move to Beta5 and do not become a runtime allowlist.
- Beta2 excludes alternate-codec retry and model-output format repair.
Acceptance criteria
- The maintainer accepts 0.1.8 Beta2: Record the runtime-derived tool compatibility architecture (ADR-0002) #350 and 0.1.8 Beta2: Define tool-type compatibility rules for custom Responses endpoints #65 or records exact required changes.
- Beta2's advertised product scope is custom-endpoint compatibility behavior, not support claims for named models.
- The no-model-fallback and no-cross-Provider-proxy boundaries are explicit.
- No unresolved product decision remains before 0.1.8 Beta2: Implement runtime-derived tool compatibility for custom Responses endpoints #58 starts.
- The decision is recorded in this issue and in ADR-0002.
Blocked by
- 0.1.8 Beta2: Record the runtime-derived tool compatibility architecture (ADR-0002) #350
- 0.1.8 Beta2: Inventory Codex CLI 0.146 tool types and representative Responses lifecycles #62
- 0.1.8 Beta2: Define the Codex CLI 0.146 Collaboration V1/V2 schema boundary #64
- 0.1.8 Beta2: Define tool-type compatibility rules for custom Responses endpoints #65
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
P1Priority 1: current iteration goalPriority 1: current iteration goalcampaign:0.1.8-beta20.1.8 Beta2 generic tool compatibility campaign0.1.8 Beta2 generic tool compatibility campaignenhancementNew feature or requestNew feature or requestready-for-humanRequires human implementationRequires human implementationwayfinder:grillingWayfinder decision or reconciliation gateWayfinder decision or reconciliation gate
Activity
[-]0.1.8 Beta1: Reconcile the two-model Responses production capability gate[/-][+]0.1.8 Beta1: Approve the two-model core Responses capability gate[/+][-]0.1.8 Beta1: Approve the two-model core Responses capability gate[/-][+]0.1.8 Beta2: Approve the two-model core Responses capability gate[/+][-]0.1.8 Beta2: Approve the two-model core Responses capability gate[/-][+]0.1.8 Beta2: Approve the custom-endpoint tool compatibility contract[/+]NOirBRight commentedon Aug 4, 2026
Orchestrator decision gate (2026-08-04)
Campaign:
campaign:0.1.8-beta2.This is a maintainer/coordinator decision, not a worker implementation ticket. It will review #62/#64/#65/#198 and explicitly approve or reject the generic
native/adapt/omit/required-but-unavailablecontract. No downstream #58 implementation or #318 publication work starts until this decision is recorded.NOirBRight commentedon Aug 5, 2026
Maintainer decision: GO for Beta2 implementation
Accepted inputs:
Approved contract:
ative, �dapt, omit, or
equired-but-unavailable.
Decision: GO to start #58. No unresolved product decision remains for its stated scope. This approval does not authorize a Beta2 tag or release; #318 remains the publication gate.