No Response Requested

So I have an issue with using GLM 4.6. I've added it correctly but I get:

"No response requested."

Also my previous attempt was stuck on generating for a while and couldn't see any code being generated so was worried it was just stuck so aborted.

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

No support for z.ai GML-4.6 and Github claude-sonnet-4.5 #2883: Same GLM-4.6 model support issue (closed, but directly mentions GLM-4.6 not being available)
Opencode with GLM 4.5 String issue #1880: GLM 4.5 string issue with similar error symptoms and model problems
Opencode stuck in "generating" #2512: Opencode stuck in "generating" - same stuck behavior you experienced
AI_APICallError: The messages parameter is illegal. Please check the documentation. - Zhipu AI GLM-4.5 #2557: GLM-4.5 API parameter issues that cause hanging/errors (closed, but shows similar GLM model problems)
Message generation interrupted, stuck at Generating #2137: Message generation interrupted, stuck at "Generating" - very similar symptoms

Feel free to ignore if none of these address your specific case.

Hmm I need to signup for the plan to test this better, can you share the session by chance?

It almost seems like the model just "said" that?

I've switched to my CC plan atm but can switch back and see if I can replicate again then share the session

I encountered this message ( or only : OK. too after using continue on an alternative routing provider with GLM 4.6 whom we already had 'stuck in sessions' with GLM 4.5.
looking at the logs, this 'stuck' behaviour or 'weird' message just happens after automated tool pruning.
It happened also under GLM 4.5 for this specific provider, also after a pruning.

These tool pruning did happen without auto compaction --> Session summary, which let me think that the model exhausted its context ( tool use in majority ) without possibility of recovery.

In regard to the anomalies with this specific proxying provider, my hypothesis is that somehow the served model announced 128K available context but had a smaller internal context windows, which exhausted far before the ide might trigger compaction --> Summary.

I was able to reproduce this kind of anomaly by using the Z.ai anthropic endpoint with GLM 4.6 ( setup as a custom provider) and let the context expire by itself with a moderate code or refactor task with edits and slight use of context7.

The log show exactly the tool auto prune before the anomaly appears.
INFO 2025-10-01T18:08:53 +22ms service=session.compaction pruned=10282 total=46436 found

Hope it helps.

that does help ty

It happened to me after interrupting the agent with esc. Any request after that just returned the "No Response Requested" error.

# Conversation History

---

**User** (*2025-10-05 05:13:37*)

@sage hi

Use the above message and context to generate a prompt and call the task tool with subagent: sage

---

**Assistant** (*2025-10-05 05:13:38*)



No response requested.

---

**User** (*2025-10-05 05:14:11*)

hi

---

**Assistant** (*2025-10-05 05:14:11*)



No response requested.

I am using the zhipu coding plan.

it happens a lot here.

happens all the time. sometimes it fixes itself by just reminding the model you are requesting a response, & sometimes that session is done lol

@thdxr

@thdxr you were asking for GLM 4.6 feedback, has this quirk been addressed? I've been using Opencode and GLM 4.6 for 6 days and this is the main blocker, along with timeouts, random 40x/50x API errors, and no retries. This is via ZAI Coding Plan. Works better with Claude Code because it more aggressively retries, whereas Opencode craps out fast and idles until you say 'Continue'.

still happening, sometimes after we have to stop it to change course with ESC, sometimes out of nowhere after a task

it's related to interrupting using the ESC key. confirmed.

and yes, unfortunately it's happening all the time.

If anyone is still facing this issue, please report your opencode --version too.

I haven't seen this happen for a while, despite using GLM 4.6 via Coding Plan and pressing ESC often.

Make sure you're using the latest version (bunx opoencode-ai@latest).

v0.15.12

latest. the issue still persists

Happened in 1.0.25 after I aborted a previous command.

This question is about whether to use the API (z.ai) version or the open-source model deployed in SGLang or vLLM.

This also happens with cerebras provider with GLM 4.6. So I suppose it's not directly related to z.ai endpoint but to the model itself ?

yeah it seems like it, when I get a chance ill try to look into it more

Seems to be specifically in the thinking blocks. On Cerebras, the schema doesn't seem to be followed correctly, and the AI SDK struggles with it.

Same here with Cerebras Z.ai GLM-4.6, every now and then it just halts, sometimes very often - a compact does help sometimes, but not always

I’ve created a pull request for this. It works on my machine so far :-) #4584

Need to also cover these more generally:

I'm guessing reasoning ✅️ but no text ❌️ or something.

I’ve created a pull request for this. It works on my machine so far :-) #4584

Please do not merge this, it is footgun

While we struggle to fix this, disable reasoning as a workaround:
#3259 (comment)

I find GLM's reasoning pretty useless anyway

@JosXa

Having the same issues with using local models in https://github.com/cubist38/mlx-openai-server
@JosXa I am surprised it has something to do with parsing the reasoning bits!
@ShamanicArts how are reminders done again? Maybe it's just a "dumb zone" thing?

To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.

Navigation Menu

Repository navigation

No Response Requested #2892

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

No Response Requested #2892

Description

Activity

github-actions commented on Oct 1, 2025

rekram1-node commented on Oct 1, 2025

JoshuaRileyDev commented on Oct 1, 2025

slipstr28 commented on Oct 1, 2025

rekram1-node commented on Oct 1, 2025

n0cloud commented on Oct 2, 2025

towry commented on Oct 4, 2025

williamhrs commented on Oct 6, 2025

ShamanicArts commented on Oct 9, 2025

kierr commented on Oct 10, 2025

williamhrs commented on Oct 17, 2025

bennyzen commented on Oct 21, 2025

kierr commented on Oct 21, 2025

bennyzen commented on Oct 21, 2025

david-crespo commented on Nov 5, 2025

zRzRzRzRzRzRzR commented on Nov 7, 2025

pnocera commented on Nov 14, 2025

rekram1-node commented on Nov 14, 2025

JosXa commented on Nov 20, 2025

burka commented on Nov 21, 2025

burka commented on Nov 21, 2025

JosXa commented on Nov 21, 2025

towry commented on Nov 21, 2025

JosXa commented on Nov 21, 2025

TomLucidor commented on Jan 19, 2026

github-actions commented on Mar 26, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions