anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 02:05:26 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

500 Internal Server Error when sending tool_calls array in request body. (Open AI compatible api) #1288

New Issue
Closed
opened 2026-02-16 17:30:19 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 17:30:19 -05:00
Owner
Copy Link
Copy Source

Originally created by @Shine1i on GitHub (Aug 13, 2025).

Title: 500 Internal Server Error when sending tool_calls array in request body

Description:
When using an OpenAI-compatible API (specifily Parasail in my case), I encountered a 500 Internal Server Error from https://api.parasail.io/v1/chat/completions only when the request body contains a tool_calls array.
If I remove tool_calls, the request succeeds as expected.

Steps to Reproduce:

  1. ask it to use like read tool (thats where it mostly fails)

interecepting the request and examining it i found that this specific part of the payload causes it to fail.

  "model": "parasail-glm45", 
  "messages": [
    {
      "role": "assistant",
      "content": "\n<think>....</think>\nI'll help you build this home page layout using Hero UI. Let me first explore the current project structure and then use the Hero UI MCP server to understand the available components.\n",
      "tool_calls": [
        {
          "id": "call_44ce0834dfd54bf18d4ab019",
          "type": "function",
          "function": {
            "name": "read",
            "arguments": "{\"filePath\":\"/home/wasim/Code/kato/package.json\"}"
          }
        }
      ]
    }
  ]
}

any ideas why parasail provider fails. works in roocode and other cli agents like crush.
PS. not all tools fails sometimes it can go on but at someone point fails. but for that specific tool after it calls it. it retry 4 times and 500.

Originally created by @Shine1i on GitHub (Aug 13, 2025). **Title:** 500 Internal Server Error when sending `tool_calls` array in request body **Description:** When using an OpenAI-compatible API (specifily Parasail in my case), I encountered a `500 Internal Server Error` from `https://api.parasail.io/v1/chat/completions` **only** when the request body contains a `tool_calls` array. If I remove `tool_calls`, the request succeeds as expected. **Steps to Reproduce:** 1. ask it to use like read tool (thats where it mostly fails) interecepting the request and examining it i found that this specific part of the payload causes it to fail. ```{ "model": "parasail-glm45", "messages": [ { "role": "assistant", "content": "\n<think>....</think>\nI'll help you build this home page layout using Hero UI. Let me first explore the current project structure and then use the Hero UI MCP server to understand the available components.\n", "tool_calls": [ { "id": "call_44ce0834dfd54bf18d4ab019", "type": "function", "function": { "name": "read", "arguments": "{\"filePath\":\"/home/wasim/Code/kato/package.json\"}" } } ] } ] } ``` any ideas why parasail provider fails. works in roocode and other cli agents like crush. PS. not all tools fails sometimes it can go on but at someone point fails. but for that specific tool after it calls it. it retry 4 times and 500.
yindo closed this issue 2026-02-16 17:30:19 -05:00
yindo commented 2026-02-16 17:30:19 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Aug 13, 2025):

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

  • #1890: Very similar issue with OpenCode sending tools parameter and Jinja tool templates to OpenAI-compatible APIs (llama.cpp) causing 500 errors. The issue describes the same core problem where OpenCode includes tools even when not configured, causing server-side failures.

If none of these address your specific case, please let us know how this issue differs.

@github-actions[bot] commented on GitHub (Aug 13, 2025): 👋 This issue might be a duplicate of existing issues. Please check: - #1890: Very similar issue with OpenCode sending tools parameter and Jinja tool templates to OpenAI-compatible APIs (llama.cpp) causing 500 errors. The issue describes the same core problem where OpenCode includes tools even when not configured, causing server-side failures. If none of these address your specific case, please let us know how this issue differs.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#1288
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?