Console Go -> Meta: sanitize recursive $ref tool schemas (Codex Desktop codex_app tools hit it too)

[mykhailoyermolenko]

What

Muse Spark 1.3 Contributor via OpenCode Go (endpoint https://opencode.ai/zen/go/v1/responses) fails on the FIRST request, before any tool executes, when the client sends a recursive tool schema:

Error from provider (Console Go): Upstream request failed: [invalid_request_error] Recursive JSON schemas are not currently supported

Meta returns HTTP 400 for recursive schemas (https://ai.developer.meta.com/docs/features/structured-output).

Relation to #45800

Same error class as #45800 (postgres MCP $defs/__schema0 self-ref broke Muse 1.2). This report shows it's not MCP-specific: Codex Desktop's built-in app tools (codex_app MCP: automation_update, create_thread, send_message_to_thread, fork_thread, handoff_thread) trigger it too. Proven by elimination: same codex binary (0.153.4), same config/model/provider succeeds via codex exec (no Desktop-only tools) and fails in Desktop (with them). OpenAI-side report: openai/codex#44144.

Ask

Apply recursive-$ref sanitization Meta-bound in the provider transform layer (the approach from unmerged #29295 - inline local $refs, replace cycles with permissive {} - or the merged #16910 fallback {type:object, additionalProperties:true}), so one strict upstream doesn't break every tool-heavy client. transform.ts currently has sanitizers for OpenAI/Moonshot/Gemini but nothing Meta/Muse-shaped.

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• Recursive $ref in postgres tool schemas breaks Meta Muse Spark ("Recursive JSON schemas are not currently supported") #45800: Same error ("Recursive JSON schemas are not currently supported") with Meta Muse Spark via Console Go, same root cause in transform.ts lacking Meta-specific $ref sanitization
• Bug Report — houseCARL + Muse Spark 1.2 Contributor (Console Go) — Recursive JSON Schema #45823: Same recursive JSON schema error with Muse Spark 1.2 Contributor (Console Go), also traced to the same transform.ts gap

Your report adds useful context (Codex Desktop built-in tools reproducing it, not just MCP tools), but the underlying bug and fix request are already tracked in those issues. Consider adding your findings as a comment there instead.