CommandCodeAI / CommandCodeAI/command-code

GLM 5.3 Flash not receiving arguments or stream ended

Open
#791 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
4k
Forks
350
PR merge metrics
No merged PRs in 30d

Description

Summary

I was trying to find alternative for dsv4f peak hours and I think GLM 5.3 flash is a good model

I was on Go model before, using 5.3 flash with no hassle, both in cmcd, opencode, pi, routed with 9router

Since my Go plan almost ended, I upgraded my plan to GOAT and started using GLM 5.3 Flash.

Weirdly, whenever the model almost reached 100K, It keep getting something like

Validation failed for tool "bash":
   - command: must have required properties command
Received arguments:
 {}

or

Stream ended without finish_reason

I've tried to ask dsv4f to fix this issue, most of the solution says to change the context window to somewhere between 80-90K. The solution sometimes working sometimes not that I reached annoyed state (and moved to dsv4f on peak hours 😭). I believe that this is neither the harness nor 9router's problem (also this is what ds4vf stated too). Just wondering why this happened when I switch plan and it was working fine before

Expected Behavior

GLM 5.3 Flash working fine like a few weeks ago

Actual Behavior

Weirdly, whenever the model almost reached 100K, It keep getting something like

Validation failed for tool "bash":
   - command: must have required properties command
Received arguments:
 {}

or

Stream ended without finish_reason
Steps to reproduce the issue
  1. Choose GLM 5.3 Flash as model
  2. Produce something with it that it almost reached 80-90K context
  3. The Received arguments error will continuously occurred if not auto compact
Command Code Version

1.44.0

Operating System

Linux

Terminal/IDE

Unknown

Shell

cmd.exe

Session file (optional)

No response

Fix prompt (optional)

No response

Additional context

No response

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start by reproducing the issue with GLM 5.3 Flash near the reported 80–100K context range using Command Code 1.44.0 on Linux. Compare the repeated empty bash arguments and missing finish_reason across the reported plan change, and consider the issue done when tool calls receive valid arguments and streams finish normally without requiring auto-compact.

Written by the indexing model from the issue text.

Assessment

Domain
ai, cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.