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

Activity

1. github-actions

   assigned

   MrMushrooooom

   on Sep 9, 2026
2. github-actions commented on Sep 9, 2026

   

   github-actionsBot

   on Sep 9, 2026 – with GitHub Actions

   Contributor

   More 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.
3. opencodejr commented on Oct 28, 2026

   

   opencodejrBot

   on Oct 28, 2026

   Contributor

   More actions

   Thanks for the detailed write-up and for narrowing it down to Codex Desktop's codex_app tools.

   The request is clear: Console Go would sanitize recursive $ref tool schemas (inline local refs, replace cycles with a permissive schema) before forwarding to Meta/Muse Spark, so that any client sending such schemas, not just OpenCode, keeps working. Since the failing client here is Codex calling https://opencode.ai/zen/go/v1/responses directly, a change in OpenCode's client-side transform.ts wouldn't help. This would have to be handled on the Go gateway. Meta documents that it doesn't support recursive schemas, so we're treating this as a feature request for the gateway. Maintainers will consider it.

   Related issues and PRs:

   • Recursive $ref in postgres tool schemas breaks Meta Muse Spark ("Recursive JSON schemas are not currently supported") #45800: same error from OpenCode v1 with a postgres MCP server's self-referencing $defs
   • fix(ai): keep tool schemas within Meta's limits #51040: a v2 PR (not merged) that would have added Meta schema normalization (recursive $ref and the depth limit) to the OpenCode client, and that mentioned this issue
   • Console Go (Meta Muse Spark): MCP tool schemas deeper than 10 levels are rejected, no Meta/Muse sanitizer #50297: the related Meta limit JSON schema exceeds the maximum nesting depth of 10 levels
   • Bug Report — houseCARL + Muse Spark 1.2 Contributor (Console Go) — Recursive JSON Schema #45823: same error with the houseCARL MCP server via OpenCode
   • Synara + Muse Spark 1.3 Contributor (Console Go) fails with Recursive JSON schemas are not currently supported #47157: same error from Synara, tracked in Synara's own repo