Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Command code GOAT used via API: MiMo V2.6 Pro stream consistently fails at ~785s with

Open
  • Is something wrong?
#940 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Domain
api, backend, observability

Research direction

Start by inspecting CommandCode trace b416c51c0eb32fde7cd20646bfd99625 and the Provider API route for the xiaomi/mimo-v2.6-pro request. Compare the 785.097-second termination with the gateway_stream_timeout and the COMPLETED record in CommandCode Studio. Done means identifying the timeout source and determining whether the failure status and upstream handling need correction.

Written by the indexing model from the issue text.

Description

Summary

I am using the CommandCode GOAT API through OpenCode in Zed. Long-running autonomous agent sessions occasionally fail when an individual xiaomi/mimo-v2.6-pro inference runs for approximately 13 minutes.

The latest failure produced:

Internal error: {"code":"gateway_stream_timeout","message":"Stream exceeded maximum duration before function timeout","origin":"gateway"}: {
  "service": "session",
  "errorName": "UnknownError"
}

The corresponding request in CommandCode Studio is:

Model: xiaomi/mimo-v2.6-pro
Duration: 785.097s
Input tokens: 0
Output tokens: 0
Cost: $0.0000
Status: COMPLETED
Trace ID: b416c51c0eb32fde7cd20646bfd99625

Dashboard timestamp: Sep 27, 2:54:10 PM (as displayed in Studio).

Expected Behavior

Continue streaming without ~13 minutes timeouts.

Actual Behavior

"Stream exceeded maximum duration before function timeout"

Steps to reproduce the issue
  1. Configure OpenCode in Zed to use the CommandCode API (Provider API?).
  2. Select xiaomi/mimo-v2.6-pro.
  3. Run a long autonomous coding-agent session. ZDR is not enabled.
  4. When an individual MiMo inference runs for approximately 13 minutes, the request terminates with:
Internal error: {"code":"gateway_stream_timeout","message":"Stream exceeded maximum duration before function timeout","origin":"gateway"}: {
  "service": "session",
  "errorName": "UnknownError"
}
  1. In CommandCode Studio, the corresponding request is recorded as:
Model: xiaomi/mimo-v2.6-pro
Duration: 785.097s
Input tokens: 0
Output tokens: 0
Cost: $0.0000
Status: COMPLETED
Trace ID: b416c51c0eb32fde7cd20646bfd99625

Other MiMo requests in the same session completed successfully, including requests lasting approximately 545s, 399s, and 317s.

The overall agent session was about 32m25s long. The failure appears tied to the duration of one individual streaming inference, not the total session duration.

Command Code Version

N/A

Operating System

Linux

Terminal/IDE

Zed + OpenCode via ACP

Shell

N/A — issue occurs through Zed/OpenCode

Session file (optional)

Not attached. The relevant CommandCode trace is:

b416c51c0eb32fde7cd20646bfd99625

Fix prompt (optional)

Please inspect trace b416c51c0eb32fde7cd20646bfd99625 and determine which gateway or upstream generated the timeout.

The request terminates at 785.097 seconds with:

gateway_stream_timeout
Stream exceeded maximum duration before function timeout

Please check whether the MiMo V2.6 Pro Provider API route has an approximately 785-second maximum streaming duration.

If this limit is imposed by an upstream gateway, please consider routing long MiMo requests through an upstream without this limit, or implementing transparent retry/failover.

Also check why CommandCode Studio records this timed-out request as COMPLETED with 0 input tokens, 0 output tokens, and $0 cost instead of marking it as failed.

Additional context

This has happened several times during one day on the same account - though only this one occurrence is captured.

Dominant language
No language data
Stars
4k
Forks
357
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CommandCodeAI/command-code

All issues in CommandCodeAI/command-code

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.