Remote Control users can run /effort, /model, /rename and /usage…

What

Remote Control lets a person follow and drive a Claude Code session from another device. Slash commands (commands typed after a /) sent that way while Claude is still working on a reply now run straight away instead of waiting. Only these are allowed:

This is controlled remotely per account, and when the server sends nothing, the code's fallback is to allow it. Separately, when typed input is waiting in the queue, Claude Code now also waits for certain commands sent through Remote Control, including /clear, before moving on.

Why

A person using Remote Control no longer has to wait for Claude to finish before changing the model or effort level, renaming the session or checking usage.

Read from

Names in the bundle/effort/model/rename/usage

Feature flag

tengu_humming_locket Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.290: on

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.290. It isn't a statement about your account. What a flag value here can and cannot tell you

Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Added since 8 Oct 2026 A small documentation edit on pricing touched a line naming /usage after this was published. Contact the sales team at [[email protected]](mailto:[email protected]) or through the [Claude Console](https://platform.claude.com/usage/limits) to discuss enterprise pricing options. about-claude/pricing see the edit

Confirmed since 8 Oct 2026 Anthropic's documentation has since written up /rename, on Manage multiple agents with agent view. * A session that's working: `/model`, `/effort`, `/rename`, and `/usage` run right away. Other replies join the session's [message queue](/docs/en/interactive-mode#queue-messages-while-claude-works) instead of interrupting the response, an… agent-view see the edit

Confirmed since 8 Oct 2026 Anthropic's documentation has since written up /usage, on Manage multiple agents with agent view. * A session that's working: `/model`, `/effort`, `/rename`, and `/usage` run right away. Other replies join the session's [message queue](/docs/en/interactive-mode#queue-messages-while-claude-works) instead of interrupting the response, an… agent-view see the edit

Confirmed since 7 Oct 2026 Anthropic's documentation has since written up /effort, on claude-on-amazon-bedrock-legacy. A `role: "system"` message can also set `output_config.effort` to [change effort mid-conversation](https://platform.claude.com/docs/en/build-with-claude/effort#change-effort-mid-conversation-beta) on Claude Fable 5.1 and Claude Opus 5.5. T… build-with-claude/claude-on-amazon-bedrock-legacy see the edit

Added since 6 Oct 2026 A small documentation edit on Models overview touched a line naming /effort after this was published. Each model's `capabilities` object includes `thinking.types.disabled`, which reports whether the model accepts `thinking: {type: "disabled"}`, the setting that [turns thinking off](https://platform.claude.com/docs/en/build-with-claude/thin… models/overview see the edit

Added since 6 Oct 2026 A small documentation edit on Personal connectors in channels touched a line naming /model after this was published. On the Enterprise plan, keep Claude Opus 5 turned on under **Model access** on your organization's [**Models**](https://claude.ai/admin-settings/models) page, which an Owner or Admin can edit. With Claude Opus 5 turned off for the organiza… claude-tag/concepts/personal-connectors see the edit

How sure we are

Two sources agreeTwo things we can check say the same as this entry.

Anthropic's documentation agreesAnthropic's documentation has since written up /model, on Customize Claude Tag.

Anthropic's release notes agreeFixed agent view's /loop run count freezing and its countdown disappearing after /clear; the count now restarts with the new conversation

The name it cites is new in this buildNew in this build: tengu_humming_locket

See this entry in the whole of v2.1.290 →

The build it came inv2.1.290

5 Oct 2026 · 548 entries, this one is #53.

Use it now36
You'll notice386
Nothing to try yet8
Under the hood118

Either side of it

v2.1.289Older
v2.1.291Newer

Open the release →

Names in this entry

slash/effort
Set the effort level: low to xhigh, max, ultracode, or auto; status prints it. max and ultracode are session-only; the ultracode key persists. Run it while Claude is responding and, once you confirm the cache warning, if Claude Code shows one, Claude Code applies the new level to the next request in that turn. Before v2.1.242, Claude Code decided from a feature flag it fetched from Anthropic whether to run the command mid-turn or queue it until the turn finished, and always queued it in a session that doesn't fetch feature flags, such as on a third-party provider. Works in -p
slash/model
Switch the AI model and save it as your default for new sessions. For models that support it, use left/right arrows to adjust effort level. With no argument, opens a picker; press s on a row to switch for the current session only. See when Claude Code asks you to confirm the switch. Once you confirm the switch, if Claude Code asks, Claude Code applies the change without waiting for the current response to finish. Before v2.1.242, Claude Code decided from a feature flag it fetched from Anthropic whether to run the command mid-turn or queue it until the turn finished, and always queued it in a session that doesn't fetch feature flags, such as on a third-party provider. Also available in non-interactive mode (-p) with a model argument instead of the picker, where it applies to the current session only and isn't saved as your default; requires Claude Code v2.1.205 or later
slash/rename
Rename the current session and show the name on the prompt bar. Without a name, auto-generates one from conversation history. Also available in non-interactive mode (-p); requires Claude Code v2.1.205 or later. From every rename surface, including claude.ai and the desktop app, Claude Code replaces control and invisible characters in the new name with spaces and caps the name at 200 characters. If the name is empty once invisible characters are removed, Claude Code rejects it and shows That name is empty once invisible characters are removed. Usage: /rename <name>. The character replacement and length cap require Claude Code v2.1.221 or later. If another live session on this machine already uses a name you pass, Claude Code applies a variant of it instead
slash/usage
Show session cost, plan usage limits, and activity stats. On a Pro, Max, Team, or Enterprise plan, includes a breakdown of what counts against your plan limits. /cost and /stats are aliases
slash/clear
Start a new conversation with empty context. Pass a name to label the previous conversation in the /resume picker. To free up context while continuing the same conversation, use /compact instead. Resume the previous conversation with /resume, or, in the same Claude Code process, restore it from the rewind menu's previous-session entry. Aliases: /reset, /new

Anthropic's notes

Upstream's own release notes for v2.1.290 name something this entry names, so the two are probably about the same change. Probably: the pairing is made on a shared name rather than on the words around it.

Fixed agent view's /loop run count freezing and its countdown disappearing after /clear; the count now restarts with the new conversation
Changed /model, /effort and /rename sent from claude agents to a busy background session to apply right away, without a confirmation, instead of when the turn ends

Is this right?

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

v2.1.221 /rename rejects names that resolve to nothing
Both mention rename
v2.1.221 Renaming a session propagates the new name
Both mention rename
v2.1.232 A session that loses its name to another live session is renamed and told why
Both mention rename