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

GLM 4.7 Max sub is slow and dumb #7666

New Issue
Open
opened 2026-02-16 18:07:52 -05:00 by yindo · 16 comments
yindo commented 2026-02-16 18:07:52 -05:00
Owner
Copy Link
Copy Source

Originally created by @moonray on GitHub (Jan 26, 2026).

Originally assigned to: @rekram1-node on GitHub.

Description

The free version was actually pretty good for tool calling and orchestration. Now that I'm using the z.ai max sub, it feels slow and dumb. That has to be a bug.

Is there some config that was applied to the free model by default, such as thinking levels (don't see any high thinking variants in opencode) or anything else? Using GLM 4.7 max sub feels like significant downgrade to the free version.

Plugins

No response

OpenCode version

No response

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

No response

Terminal

No response

Originally created by @moonray on GitHub (Jan 26, 2026). Originally assigned to: @rekram1-node on GitHub. ### Description The free version was actually pretty good for tool calling and orchestration. Now that I'm using the z.ai max sub, it feels slow and dumb. That has to be a bug. Is there some config that was applied to the free model by default, such as thinking levels (don't see any high thinking variants in opencode) or anything else? Using GLM 4.7 max sub feels like significant downgrade to the free version. ### Plugins _No response_ ### OpenCode version _No response_ ### Steps to reproduce _No response_ ### Screenshot and/or share link _No response_ ### Operating System _No response_ ### Terminal _No response_
yindo added the bug label 2026-02-16 18:07:52 -05:00
yindo commented 2026-02-16 18:07:53 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Jan 26, 2026):

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

  • #6074: Differences between the free and paid versions of GLM 4.7

Feel free to ignore if this doesn't address your specific case.

@github-actions[bot] commented on GitHub (Jan 26, 2026): This issue might be a duplicate of existing issues. Please check: - #6074: Differences between the free and paid versions of GLM 4.7 Feel free to ignore if this doesn't address your specific case.
yindo commented 2026-02-16 18:07:53 -05:00
Author
Owner
Copy Link
Copy Source

@moonray commented on GitHub (Jan 27, 2026):

I'm wondering if it's related to this:

From docs.z.ai

Preserved Thinking

This capability is enabled by default on the Coding Plan endpoint and disabled by default on the standard API endpoint. If you want to enable Preserved Thinking in your product (primarily recommended for coding/agent scenarios), you can turn it on for the API endpoint by setting “clear_thinking”: false, and you must return the complete, unmodified reasoning_content back to the API.
All consecutive reasoning_content blocks must exactly match the original sequence generated by the model during the initial request. Do not reorder or edit these blocks; otherwise, performance may degrade and cache hit rates may be affected.

Turn-level Thinking

“Turn-level Thinking” is a capability that lets you control reasoning computation on a per-turn basis: within the same session, each request can independently choose to enable or disable thinking. This is a new capability introduced in GLM-4.7, with the following advantages:

  • More flexible cost/latency control: For lightweight turns like “asking a fact” or “tweaking wording,” you can disable thinking to get faster responses; for heavier tasks like “complex planning,” “multi-constraint reasoning,” or “code debugging,” you can enable thinking to improve accuracy and stability.
  • Smoother multi-turn experience: The thinking switch can be toggled at any point within a session. The model stays coherent across turns and keeps a consistent output style, making it feel “smarter when things are hard, faster when things are simple.”
  • Better for agent/tool-use scenarios: On turns that require quick tool execution, you can reduce reasoning overhead; on turns that require making decisions based on tool results, you can turn on deeper thinking—dynamically balancing efficiency and quality.
@moonray commented on GitHub (Jan 27, 2026): I'm wondering if it's related to this: From [docs.z.ai](https://docs.z.ai/guides/capabilities/thinking-mode#:~:text=Preserved-,thinking,-GLM%2D4.7%20introduces) > ## Preserved Thinking > This capability is enabled by default on the Coding Plan endpoint and disabled by default on the standard API endpoint. If you want to enable Preserved Thinking in your product (primarily recommended for coding/agent scenarios), you can turn it on for the API endpoint by setting “clear_thinking”: false, and you must return the complete, unmodified reasoning_content back to the API. > All consecutive reasoning_content blocks must exactly match the original sequence generated by the model during the initial request. Do not reorder or edit these blocks; otherwise, performance may degrade and cache hit rates may be affected. > ## Turn-level Thinking > “Turn-level Thinking” is a capability that lets **you control reasoning computation on a per-turn basis**: within the same session, each request can independently choose to enable or disable thinking. This is a new capability introduced in GLM-4.7, with the following advantages: > - **More flexible cost/latency control**: For lightweight turns like “asking a fact” or “tweaking wording,” you can disable thinking to get faster responses; for heavier tasks like “complex planning,” “multi-constraint reasoning,” or “code debugging,” you can enable thinking to improve accuracy and stability. > - **Smoother multi-turn experience**: The thinking switch can be toggled at any point within a session. The model stays coherent across turns and keeps a consistent output style, making it feel “smarter when things are hard, faster when things are simple.” > - **Better for agent/tool-use scenarios**: On turns that require quick tool execution, you can reduce reasoning overhead; on turns that require making decisions based on tool results, you can turn on deeper thinking—dynamically balancing efficiency and quality.
yindo commented 2026-02-16 18:07:53 -05:00
Author
Owner
Copy Link
Copy Source

@vladlearns commented on GitHub (Jan 27, 2026):

Same here. Very slow and very dumb

@vladlearns commented on GitHub (Jan 27, 2026): Same here. Very slow and very dumb
yindo commented 2026-02-16 18:07:53 -05:00
Author
Owner
Copy Link
Copy Source

@ravshan-oxagile commented on GitHub (Jan 27, 2026):

Maybe this is because openai api is used rather than anthropic api. Also afaik z.ai supports only chat completions api (the legacy one) not the new responses api

@ravshan-oxagile commented on GitHub (Jan 27, 2026): Maybe this is because openai api is used rather than anthropic api. Also afaik z.ai supports only chat completions api (the legacy one) not the new responses api
yindo commented 2026-02-16 18:07:53 -05:00
Author
Owner
Copy Link
Copy Source

@maarteNNNN commented on GitHub (Jan 29, 2026):

I subscribed for the Max for one year after a worse than Claude performance but better pricing using GLM 4.6. Since 4.7 it's just obnoxious how bad this is performing. It's slow as f*** and not performing nearly as close as it used to be. I feel cheated.

On contacting Z.ai when I received some errors about rate-limiting they replied with the following:

However, we notice that you receive error codes in Chinese, which is un-expected. The api endpoint you are using 'https://bigmodel.cn/claude-code' is incorrect, since you are a user in z.ai platform, please ensure to use the correct api endpoint with domain name api.z.ai.
For Claude Code: https://api.z.ai/api/anthropic
For Other Tools: https://api.z.ai/api/coding/paas/v4

@maarteNNNN commented on GitHub (Jan 29, 2026): I subscribed for the Max for one year after a worse than Claude performance but better pricing using GLM 4.6. Since 4.7 it's just obnoxious how bad this is performing. It's slow as f*** and not performing nearly as close as it used to be. I feel cheated. On contacting Z.ai when I received some errors about rate-limiting they replied with the following: > However, we notice that you receive error codes in Chinese, which is un-expected. The api endpoint you are using 'https://bigmodel.cn/claude-code' is incorrect, since you are a user in z.ai platform, please ensure to use the correct api endpoint with domain name api.z.ai. > For Claude Code: https://api.z.ai/api/anthropic > For Other Tools: https://api.z.ai/api/coding/paas/v4
yindo commented 2026-02-16 18:07:53 -05:00
Author
Owner
Copy Link
Copy Source

@maarteNNNN commented on GitHub (Jan 29, 2026):

I seemed to be able to increase performance with manually putting it in the config:

    "zhipuai-coding-plan": {
      "options": {
        "baseURL": "https://api.z.ai/api/coding/paas/v4"
      },
      "models": {
        "glm-4.7": {
          "limit": {
            "context": 100000,
            "output": 4096
          }
        },
        "glm-4.5": {
          "limit": {
            "context": 100000,
            "output": 4096
          }
        },
        "glm-4.5-air": {
          "limit": {
            "context": 100000,
            "output": 4096
          }
        },
        "glm-4.5-flash": {
          "limit": {
            "context": 100000,
            "output": 4096
          }
        },
        "glm-4.5v": {
          "limit": {
            "context": 100000,
            "output": 4096
          }
        },
        "glm-4.6": {
          "limit": {
            "context": 100000,
            "output": 4096
          }
        },
        "glm-4.6v": {
          "limit": {
            "context": 100000,
            "output": 4096
          }
        },
        "glm-4.6v-flash": {
          "limit": {
            "context": 100000,
            "output": 4096
          }
        }
      }
    },
    "zai-coding-plan": {
      "options": {
        "baseURL": "https://api.z.ai/api/coding/paas/v4"
      },
      "models": {
        "glm-4.7": {
          "limit": {
            "context": 100000,
            "output": 4096
          }
        },
        "glm-4.7-flash": {
          "limit": {
            "context": 100000,
            "output": 4096
          }
        },
        "glm-4.6": {
          "limit": {
            "context": 100000,
            "output": 4096
          }
        },
        "glm-4.6v": {
          "limit": {
            "context": 100000,
            "output": 4096
          }
        },
        "glm-4.5": {
          "limit": {
            "context": 100000,
            "output": 4096
          }
        },
        "glm-4.5-air": {
          "limit": {
            "context": 100000,
            "output": 4096
          }
        },
        "glm-4.5-flash": {
          "limit": {
            "context": 100000,
            "output": 4096
          }
        },
        "glm-4.5v": {
          "limit": {
            "context": 100000,
            "output": 4096
          }
        }
      }
    }
  },

I reduced the context as well for faster speed.

Would it by default be connecting to Chinese servers?

I also don't know what's the difference between zai-coding-plan and zhipuai-coding-plan...

When removing my API key it really seems to be a Chinese endpoint as per error message: 您的GLM Coding Plan套餐已到期，暂无法使用，前往官方续订后即 可恢复https://bigmodel.cn/claude-code。

I will do some more testing hopefully it's resolved.

@maarteNNNN commented on GitHub (Jan 29, 2026): I seemed to be able to increase performance with manually putting it in the config: ```json "zhipuai-coding-plan": { "options": { "baseURL": "https://api.z.ai/api/coding/paas/v4" }, "models": { "glm-4.7": { "limit": { "context": 100000, "output": 4096 } }, "glm-4.5": { "limit": { "context": 100000, "output": 4096 } }, "glm-4.5-air": { "limit": { "context": 100000, "output": 4096 } }, "glm-4.5-flash": { "limit": { "context": 100000, "output": 4096 } }, "glm-4.5v": { "limit": { "context": 100000, "output": 4096 } }, "glm-4.6": { "limit": { "context": 100000, "output": 4096 } }, "glm-4.6v": { "limit": { "context": 100000, "output": 4096 } }, "glm-4.6v-flash": { "limit": { "context": 100000, "output": 4096 } } } }, "zai-coding-plan": { "options": { "baseURL": "https://api.z.ai/api/coding/paas/v4" }, "models": { "glm-4.7": { "limit": { "context": 100000, "output": 4096 } }, "glm-4.7-flash": { "limit": { "context": 100000, "output": 4096 } }, "glm-4.6": { "limit": { "context": 100000, "output": 4096 } }, "glm-4.6v": { "limit": { "context": 100000, "output": 4096 } }, "glm-4.5": { "limit": { "context": 100000, "output": 4096 } }, "glm-4.5-air": { "limit": { "context": 100000, "output": 4096 } }, "glm-4.5-flash": { "limit": { "context": 100000, "output": 4096 } }, "glm-4.5v": { "limit": { "context": 100000, "output": 4096 } } } } }, ``` I reduced the context as well for faster speed. Would it by default be connecting to Chinese servers? I also don't know what's the difference between `zai-coding-plan` and `zhipuai-coding-plan`... When removing my API key it really seems to be a Chinese endpoint as per error message: `您的GLM Coding Plan套餐已到期，暂无法使用，前往官方续订后即 可恢复https://bigmodel.cn/claude-code。` I will do some more testing hopefully it's resolved.
yindo commented 2026-02-16 18:07:53 -05:00
Author
Owner
Copy Link
Copy Source

@TotalLag commented on GitHub (Feb 1, 2026):

Max plan user as well. The config worked for me too and opencode is zippy as well. I know on GLM docs they make mention to use the specific URL so I thought it was default on opencode. Thank you!

What also helped me was adding in concurrency settings for all the models so opencode can make use of its queues.

Zhipu is the China branch of zai.

@TotalLag commented on GitHub (Feb 1, 2026): Max plan user as well. The config worked for me too and opencode is zippy as well. I know on GLM docs they make mention to use the specific URL so I thought it was default on opencode. Thank you! What also helped me was adding in concurrency settings for all the models so opencode can make use of its queues. Zhipu is the China branch of zai.
yindo commented 2026-02-16 18:07:53 -05:00
Author
Owner
Copy Link
Copy Source

@diegohb commented on GitHub (Feb 2, 2026):

Right, is this not accounted for in OpenCode fault auth flow for z?

Image

Instructions on Z website says default opencode auth flow works: https://docs.z.ai/devpack/tool/opencode

@diegohb commented on GitHub (Feb 2, 2026): Right, is this not accounted for in OpenCode fault auth flow for z? <img width="697" height="153" alt="Image" src="https://github.com/user-attachments/assets/78f79e98-7c21-48c1-bd3f-5ff44dbbd5f8" /> Instructions on Z website says default opencode auth flow works: https://docs.z.ai/devpack/tool/opencode
yindo commented 2026-02-16 18:07:53 -05:00
Author
Owner
Copy Link
Copy Source

@mikaelj commented on GitHub (Feb 2, 2026):

@TotalLag could you please share the settings you use? specifically the part about concurrency.

@mikaelj commented on GitHub (Feb 2, 2026): @TotalLag could you please share the settings you use? specifically the part about concurrency.
yindo commented 2026-02-16 18:07:53 -05:00
Author
Owner
Copy Link
Copy Source

@maarteNNNN commented on GitHub (Feb 2, 2026):

as per config:

    "zai-coding-plan": {
      "options": {
        "baseURL": "https://api.z.ai/api/coding/paas/v4",
        "concurrency": 5
      },

@TotalLag what number did you define and are you getting good results? Mine still aren't that great compared to Claude Sonnet using GH Copilot...

@maarteNNNN commented on GitHub (Feb 2, 2026): as per [config](https://opencode.ai/config.json): ```json "zai-coding-plan": { "options": { "baseURL": "https://api.z.ai/api/coding/paas/v4", "concurrency": 5 }, ``` @TotalLag what number did you define and are you getting good results? Mine still aren't that great compared to Claude Sonnet using GH Copilot...
yindo commented 2026-02-16 18:07:53 -05:00
Author
Owner
Copy Link
Copy Source

@moonray commented on GitHub (Feb 2, 2026):

I checked my outgoing network traffic, and my endpoint is not pointing to the Chinese servers, but to the correct international servers (I didn't add the z.ai models to my config).
So that's definitely not the issue for me.

@moonray commented on GitHub (Feb 2, 2026): I checked my outgoing network traffic, and my endpoint is not pointing to the Chinese servers, but to the correct international servers (I didn't add the z.ai models to my config). So that's definitely not the issue for me.
yindo commented 2026-02-16 18:07:53 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Feb 2, 2026):

In opencode if you are using zai coding plan we use:

If you are using Zhipu coding plan we use:

@rekram1-node commented on GitHub (Feb 2, 2026): In opencode if you are using zai coding plan we use: - https://api.z.ai/api/coding/paas/v4 If you are using Zhipu coding plan we use: - https://open.bigmodel.cn/api/coding/paas/v4
yindo commented 2026-02-16 18:07:53 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Feb 2, 2026):

So if your config is like this:
"zai-coding-plan": {
"options": {
"baseURL": "https://api.z.ai/api/coding/paas/v4"
},

It should make 0 difference

@rekram1-node commented on GitHub (Feb 2, 2026): So if your config is like this: "zai-coding-plan": { "options": { "baseURL": "https://api.z.ai/api/coding/paas/v4" }, It should make 0 difference
yindo commented 2026-02-16 18:07:53 -05:00
Author
Owner
Copy Link
Copy Source

@diegohb commented on GitHub (Feb 3, 2026):

does setting concurrency up help? is there thinking modes to configure manually? I have no special config for my z.ai subscription, just connected through OC provider auth and let it add whatever its adding for it to configure. should I use my own config?

@diegohb commented on GitHub (Feb 3, 2026): does setting concurrency up help? is there thinking modes to configure manually? I have no special config for my z.ai subscription, just connected through OC provider auth and let it add whatever its adding for it to configure. should I use my own config?
yindo commented 2026-02-16 18:07:53 -05:00
Author
Owner
Copy Link
Copy Source

@LeoNardo-LB commented on GitHub (Feb 3, 2026):

I seemed to be able to increase performance with manually putting it in the config:

"zhipuai-coding-plan": {
  "options": {
    "baseURL": "https://api.z.ai/api/coding/paas/v4"
  },
  "models": {
    "glm-4.7": {
      "limit": {
        "context": 100000,
        "output": 4096
      }
    },
    "glm-4.5": {
      "limit": {
        "context": 100000,
        "output": 4096
      }
    },
    "glm-4.5-air": {
      "limit": {
        "context": 100000,
        "output": 4096
      }
    },
    "glm-4.5-flash": {
      "limit": {
        "context": 100000,
        "output": 4096
      }
    },
    "glm-4.5v": {
      "limit": {
        "context": 100000,
        "output": 4096
      }
    },
    "glm-4.6": {
      "limit": {
        "context": 100000,
        "output": 4096
      }
    },
    "glm-4.6v": {
      "limit": {
        "context": 100000,
        "output": 4096
      }
    },
    "glm-4.6v-flash": {
      "limit": {
        "context": 100000,
        "output": 4096
      }
    }
  }
},
"zai-coding-plan": {
  "options": {
    "baseURL": "https://api.z.ai/api/coding/paas/v4"
  },
  "models": {
    "glm-4.7": {
      "limit": {
        "context": 100000,
        "output": 4096
      }
    },
    "glm-4.7-flash": {
      "limit": {
        "context": 100000,
        "output": 4096
      }
    },
    "glm-4.6": {
      "limit": {
        "context": 100000,
        "output": 4096
      }
    },
    "glm-4.6v": {
      "limit": {
        "context": 100000,
        "output": 4096
      }
    },
    "glm-4.5": {
      "limit": {
        "context": 100000,
        "output": 4096
      }
    },
    "glm-4.5-air": {
      "limit": {
        "context": 100000,
        "output": 4096
      }
    },
    "glm-4.5-flash": {
      "limit": {
        "context": 100000,
        "output": 4096
      }
    },
    "glm-4.5v": {
      "limit": {
        "context": 100000,
        "output": 4096
      }
    }
  }
}

},
I reduced the context as well for faster speed.

Would it by default be connecting to Chinese servers?

I also don't know what's the difference between zai-coding-plan and zhipuai-coding-plan...

When removing my API key it really seems to be a Chinese endpoint as per error message: 您的GLM Coding Plan套餐已到期，暂无法使用，前往官方续订后即 可恢复https://bigmodel.cn/claude-code。

I will do some more testing hopefully it's resolved.

@mikaelj After I used your parameters, I feel the speed has increased a lot. But should 128k context be the standard?
By the way, what does the output parameter do? Is it used to control the number of output tokens?

@LeoNardo-LB commented on GitHub (Feb 3, 2026): > I seemed to be able to increase performance with manually putting it in the config: > > "zhipuai-coding-plan": { > "options": { > "baseURL": "https://api.z.ai/api/coding/paas/v4" > }, > "models": { > "glm-4.7": { > "limit": { > "context": 100000, > "output": 4096 > } > }, > "glm-4.5": { > "limit": { > "context": 100000, > "output": 4096 > } > }, > "glm-4.5-air": { > "limit": { > "context": 100000, > "output": 4096 > } > }, > "glm-4.5-flash": { > "limit": { > "context": 100000, > "output": 4096 > } > }, > "glm-4.5v": { > "limit": { > "context": 100000, > "output": 4096 > } > }, > "glm-4.6": { > "limit": { > "context": 100000, > "output": 4096 > } > }, > "glm-4.6v": { > "limit": { > "context": 100000, > "output": 4096 > } > }, > "glm-4.6v-flash": { > "limit": { > "context": 100000, > "output": 4096 > } > } > } > }, > "zai-coding-plan": { > "options": { > "baseURL": "https://api.z.ai/api/coding/paas/v4" > }, > "models": { > "glm-4.7": { > "limit": { > "context": 100000, > "output": 4096 > } > }, > "glm-4.7-flash": { > "limit": { > "context": 100000, > "output": 4096 > } > }, > "glm-4.6": { > "limit": { > "context": 100000, > "output": 4096 > } > }, > "glm-4.6v": { > "limit": { > "context": 100000, > "output": 4096 > } > }, > "glm-4.5": { > "limit": { > "context": 100000, > "output": 4096 > } > }, > "glm-4.5-air": { > "limit": { > "context": 100000, > "output": 4096 > } > }, > "glm-4.5-flash": { > "limit": { > "context": 100000, > "output": 4096 > } > }, > "glm-4.5v": { > "limit": { > "context": 100000, > "output": 4096 > } > } > } > } > }, > I reduced the context as well for faster speed. > > Would it by default be connecting to Chinese servers? > > I also don't know what's the difference between `zai-coding-plan` and `zhipuai-coding-plan`... > > When removing my API key it really seems to be a Chinese endpoint as per error message: `您的GLM Coding Plan套餐已到期，暂无法使用，前往官方续订后即 可恢复https://bigmodel.cn/claude-code。` > > I will do some more testing hopefully it's resolved. @mikaelj After I used your parameters, I feel the speed has increased a lot. But should 128k context be the standard? By the way, what does the output parameter do? Is it used to control the number of output tokens?
yindo commented 2026-02-16 18:07:53 -05:00
Author
Owner
Copy Link
Copy Source

@TotalLag commented on GitHub (Feb 4, 2026):

@TotalLag could you please share the settings you use? specifically the part about concurrency.

I am using the numbers z.ai gives from the dashboard. However they noted that it's API and not Coding Plan so I'm unsure if it's actually effective or placebo, but I've seen in logs where my agents will wait so I assume the concurrency is working. I just noticed it's not core opencode so ymmv:

oh-my-opencode.json:

{
	"$schema": "https://raw.githubusercontent.com/code-yeongyu/oh-my-opencode/master/assets/oh-my-opencode.schema.json",
	"agents": {
		"sisyphus": {
			"model": "zai-coding-plan/glm-4.7"
		},
		"hephaestus": {
			"model": "zai-coding-plan/glm-4.7"
		},
		"librarian": {
			"model": "zai-coding-plan/glm-4.5-air"
		},
		"explore": {
			"model": "zai-coding-plan/glm-4.5-air"
		},
		"oracle": {
			"model": "zai-coding-plan/glm-4.7"
		},
		"frontend-ui-ux-engineer": {
			"model": "zai-coding-plan/glm-4.6v"
		},
		"ultrabrain": {
			"model": "openrouter/openai/5.2-codex"
		},
		"document-writer": {
			"model": "zai-coding-plan/glm-4.5-air"
		},
		"multimodal-looker": {
			"model": "zai-coding-plan/glm-4.6v"
		}
	},
	"categories": {
		"quick": {
			"model": "zai-coding-plan/glm-4.5-air"
		},
		"writing": {
			"model": "zai-coding-plan/glm-4.5-air"
		},
		"unspecified-low": {
			"model": "zai-coding-plan/glm-4.5-air"
		},
		"artistry": {
			"model": "zai-coding-plan/glm-4.6v"
		},
		"visual-engineering": {
			"model": "zai-coding-plan/glm-4.6v"
		}
	},
	"background_task": {
		"modelConcurrency": {
			"zai-coding-plan/glm-4.6": 1,
			"zai-coding-plan/glm-4.6v-flashx": 3,
			"zai-coding-plan/glm-4.7": 2,
			"zai-coding-plan/glm-image": 1,
			"zai-coding-plan/glm-4.5": 10,
			"zai-coding-plan/glm-4.6v": 10,
			"zai-coding-plan/glm-4.7-flash": 1,
			"zai-coding-plan/glm-4.7-flashx": 3,
			"zai-coding-plan/glm-4-plus": 20,
			"zai-coding-plan/glm-4.5v": 10,
			"zai-coding-plan/glm-4.6v-flash": 1,
			"zai-coding-plan/autoglm-phone-multilingual": 5,
			"zai-coding-plan/glm-4.5-air": 5,
			"zai-coding-plan/glm-4.5-airx": 5,
			"zai-coding-plan/glm-4.5-flash": 2,
			"zai-coding-plan/glm-4-32b-0414-128k": 15,
			"zai-coding-plan/cogview-4-250304": 5,
			"zai-coding-plan/glm-asr-2512": 5,
			"zai-coding-plan/viduq1-text": 5,
			"zai-coding-plan/viduq1-image": 5,
			"zai-coding-plan/viduq1-start-end": 5,
			"zai-coding-plan/vidu2-image": 5,
			"zai-coding-plan/vidu2-start-end": 5,
			"zai-coding-plan/vidu2-reference": 5,
			"zai-coding-plan/cogvideox-3": 1
		}
	}
}
@TotalLag commented on GitHub (Feb 4, 2026): > [@TotalLag](https://github.com/TotalLag) could you please share the settings you use? specifically the part about concurrency. I am using the numbers z.ai gives from the dashboard. However they noted that it's API and not Coding Plan so I'm unsure if it's actually effective or placebo, but I've seen in logs where my agents will wait so I assume the concurrency is working. I just noticed it's not core opencode so ymmv: oh-my-opencode.json: ``` { "$schema": "https://raw.githubusercontent.com/code-yeongyu/oh-my-opencode/master/assets/oh-my-opencode.schema.json", "agents": { "sisyphus": { "model": "zai-coding-plan/glm-4.7" }, "hephaestus": { "model": "zai-coding-plan/glm-4.7" }, "librarian": { "model": "zai-coding-plan/glm-4.5-air" }, "explore": { "model": "zai-coding-plan/glm-4.5-air" }, "oracle": { "model": "zai-coding-plan/glm-4.7" }, "frontend-ui-ux-engineer": { "model": "zai-coding-plan/glm-4.6v" }, "ultrabrain": { "model": "openrouter/openai/5.2-codex" }, "document-writer": { "model": "zai-coding-plan/glm-4.5-air" }, "multimodal-looker": { "model": "zai-coding-plan/glm-4.6v" } }, "categories": { "quick": { "model": "zai-coding-plan/glm-4.5-air" }, "writing": { "model": "zai-coding-plan/glm-4.5-air" }, "unspecified-low": { "model": "zai-coding-plan/glm-4.5-air" }, "artistry": { "model": "zai-coding-plan/glm-4.6v" }, "visual-engineering": { "model": "zai-coding-plan/glm-4.6v" } }, "background_task": { "modelConcurrency": { "zai-coding-plan/glm-4.6": 1, "zai-coding-plan/glm-4.6v-flashx": 3, "zai-coding-plan/glm-4.7": 2, "zai-coding-plan/glm-image": 1, "zai-coding-plan/glm-4.5": 10, "zai-coding-plan/glm-4.6v": 10, "zai-coding-plan/glm-4.7-flash": 1, "zai-coding-plan/glm-4.7-flashx": 3, "zai-coding-plan/glm-4-plus": 20, "zai-coding-plan/glm-4.5v": 10, "zai-coding-plan/glm-4.6v-flash": 1, "zai-coding-plan/autoglm-phone-multilingual": 5, "zai-coding-plan/glm-4.5-air": 5, "zai-coding-plan/glm-4.5-airx": 5, "zai-coding-plan/glm-4.5-flash": 2, "zai-coding-plan/glm-4-32b-0414-128k": 15, "zai-coding-plan/cogview-4-250304": 5, "zai-coding-plan/glm-asr-2512": 5, "zai-coding-plan/viduq1-text": 5, "zai-coding-plan/viduq1-image": 5, "zai-coding-plan/viduq1-start-end": 5, "zai-coding-plan/vidu2-image": 5, "zai-coding-plan/vidu2-start-end": 5, "zai-coding-plan/vidu2-reference": 5, "zai-coding-plan/cogvideox-3": 1 } } } ```
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 bug
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#7666
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?