{"version":"2.1.290","anchor":"model-turns-refused-on-remote-transport-or-disabled-query-sc","canonical_anchor":"model-turns-refused-on-remote-transport-or-disabled-query-sc","heading":"Queued messages are now also refused in remote mode, and refusals are recorded","tier":"notice","area":"Messaging","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/model-turns-refused-on-remote-transport-or-disabled-query-sc","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Queued messages are now also refused in remote mode, and refusals are recorded\n\nQueued messages and deferred slash commands are refused in remote mode as well as when sending is disabled, and each refusal is now recorded\n\n**Unclear.** It is not settled whether held turns in remote mode ever reached this point before, so the practical difference in remote mode is unclear.\n\n**What**\n\nSometimes a message you typed is held in a queue, or a slash command (a command typed after `\/`) is held until later. Claude Code refuses to send these held turns to the model in two situations:\n\n- when sending to the model is turned off on the current screen\n\n- when the session is running in remote mode\n\nBefore, only the first situation applied, and Claude Code simply stopped without recording anything. Remote mode now counts as well, and each refusal records an analytics event, `tengu_model_turn_refused_by_screen`, saying which kind of screen refused it.\n\n**Why**\n\nIn remote mode, held messages and commands are now turned away at this point instead of going on to the model, and the new event lets these refusals be counted.\n\n- Area: Messaging\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}