Skip to content

Synara + Muse Spark 1.3 Contributor (Console Go) fails with Recursive JSON schemas are not currently supported #47157

Closed as not planned

Description

@alexfoxtm

Description

Using Synara 0.8.1 on macOS with opencode 1.18.27 and model opencode-go/muse-spark-1.3-contributor (free contributor, opencode-go paid subscription) always fails immediately with:

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

Same error occurs with muse-spark-1.2-contributor. Reported on behalf of user running Meta Muse Spark via Console Go. Mentioning Meta Muse Spark as requested.

Reproduction

  1. Install Synara desktop 0.8.1 on macOS, enable opencode provider (binary opencode, version 1.18.27 verified via opencode --version).
  2. In OpenCode config select model opencode-go/muse-spark-1.3-contributor.
  3. Start any task via Synara using opencode runtime (e.g. cwd /Users/AleksandrSlobodanyuk/Projects/Current/mj/opsarmor.net).
  4. First request fails before any tool executes with error above. Thread title generation also fails with same model (generateThreadTitle: Unexpected server error. model=opencode-go/muse-spark-1.3-contributor).

Expected

Request succeeds like it does in opencode TUI directly, or like other models do inside Synara.

Actual / Logs

From ~/.local/share/opencode/log/opencode.log:

stream providerID=opencode-go modelID=muse-spark-1.3-contributor ... error.error="AI_APICallError: Error from provider (Console Go): Upstream request failed: [invalid_request_error] Recursive JSON schemas are not currently supported"
stream providerID=opencode-go modelID=muse-spark-1.2-contributor ... same error
stream providerID=opencode-go modelID=qwen3.8-flash ... success (step=1, exiting loop)

From ~/.synara/userdata/logs/server.log:

provider command reactor failed to generate thread title ... threadModel: opencode-go/muse-spark-1.3-contributor ... Text generation failed in generateThreadTitle

grep -c "Recursive JSON" ~/.local/share/opencode/log/opencode.log = 15 occurrences.

Analysis / Suspected root cause

Workaround tried

  • Switching Synara task to qwen3.8-flash works.
  • Using muse-spark-1.3-contributor directly in opencode TUI (outside Synara) works.

Environment

  • macOS (Apple Silicon), Synara 0.8.1, Synara.app present in /Applications
  • opencode 1.18.27 (/Users/AleksandrSlobodanyuk/.hermes/node/bin/opencode)
  • Global opencode.json model: opencode-go/muse-spark-1.3-contributor, MCP: only 1password (disabled)
  • Auth: opencode-go subscription in ~/.local/share/opencode/auth.json
  • No project-level opencode.json in failing project

Request

  1. Log / identify which tool schema is recursive when Meta rejects it (include tool name in error or debug log).
  2. Add Meta/Muse schema sanitization in provider transform layer (flatten recursive $ref cycles before sending to Console Go / Meta API).
  3. Alternatively document Synara gateway tools as incompatible with Muse Spark until fixed.

Activity

  1. alexfoxtm commented on Sep 3, 2026

    @alexfoxtm
    Author

    Correction from reporter: this is a Synara-side issue, not opencode. Same model works in opencode TUI directly; failure only occurs for Synara-driven sessions where Synara gateway MCP tools are injected (recursive $ref rejected by Meta API).

    Tracked in Synara repo: Emanuele-web04/synara#957

    Closing as misfiled here.

  2. github-actions commented on Sep 3, 2026

    @github-actions
    Contributor

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

    Both report the same root cause: recursive $ref schemas in MCP tool definitions being passed through to the Meta/Console Go API without sanitization. Consider following or contributing to those issues for updates on a fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions