Claude Code 2.1.293

When running multiple background sessions, the agent list and bottom-bar information now correctly reflect the current state. Previously, when the system briefly couldn't read the session folder (for example, because too many files were open), the agent count in the bottom bar would vanish and the list would be wiped out by placeholders. Now read errors no longer scramble the interface. Custom agents named worker are no longer mislabeled as Agent at startup, and the detail dialog title keeps the original type after they finish. claude agents previously offered an option to skip permission checks, but if the consent existed only in .claude/settings.local.json or a --settings file, background sessions would ignore that option; now consent is asked for first, and sessions that still ignore the option keep showing a short notice.

When you press the left arrow ← key mid-run to switch a session to the background, unsent text and pending-question states are no longer accidentally interrupted. Previously, as long as the input box held unsent text, or the screen was waiting for you to answer a question, pressing ← would still switch to the background after 10 seconds. Now the background switch is automatically canceled in these situations. When a queued message cannot be transferred to the background, the system stays in place and explains why, instead of losing the message. If a permission confirmation appears right after you press ←, pressing Esc, or choosing No without feedback, also stops that turn as expected.

When developing custom modules or plugins, tool registration and testing flows are more reliable. $.tool.register supports isDeferred; setting it to false lists the tool schema directly in the prompt without going through tool search. When the plugin hook (a small program triggered by specific events) worker process restarts, a module's classic.* event hooks are no longer dropped, avoiding a situation where only settings hooks respond alone. Modules calling $.session.append used to make claude plugin test fail; tests can now read back the appended records via mock.session. On Macs with Docker Desktop installed, symlinks (shortcut files pointing to another location) under ~/.docker/bin used to make claude plugin eval reject every execution granted Bash permission. This bug is fixed, and the rejection message now indicates which part of the credential store (where login proofs are kept) holds the link.

When conversing through remote control or cloud environments, long replies display and background status behave more normally. Previously, in long conversations text would occasionally freeze in a block and then suddenly pop out; it now displays smoothly word by word. After credentials are restored, the system no longer re-uploads the history from the start of the session. When launched via the claude remote-control command, push notifications no longer falsely report that remote control is not enabled.

When uploading projects with code review or /ultrareview, file checks and error guidance are clearer. Previously on Linux, sandboxed command execution could wrongly reject some repositories because a config file "couldn't be parsed"—for example, when the repository sat inside another checked-out copy of the project. This read problem is now fixed. When a split index file is rejected, the system no longer suggests a fix that could leave Git unable to read the index. In Code Review's add-repository dialog, repositories that can't be added are now listed one by one, each with its reason (such as missing GitHub write permission).

When you had just edited a custom skill's description on the web, Claude in the terminal sometimes couldn't read the change. After editing a skill description synced from claude.ai, you no longer sometimes need to start a new conversation or type /clear for the model to pick up the revised description. When no session is in use, the background sync that checks for skill changes now runs about every 40 minutes instead of every 10 minutes.

When pasting text in the terminal, setting shortcuts, or picking model parameters, input detection is more accurate. Pasted text whose first and last words matched used to be treated as typed by hand. After pasting a skill name, an accent mark typed or pasted right after it that merged into the last letter could make the skill name count as manual input; both issues are fixed. In the /model menu, using the left and right arrows to adjust thinking depth no longer wraps past the highest or lowest value, avoiding accidentally saving Low as the default. Previously, when sending a report via /feedback, pressing Ctrl+O or Ctrl+Z jumped back to the draft list, making it impossible to cancel sending; this is now fixed. keybindings.json accepts a single space key " ", and shows a warning for extra spaces like "ctrl+ k".

For users accustomed to editing commands with Vim mode enabled in the terminal, indentation and deletion operations are now more intuitive. Previously, pressing >> or << to indent on blank lines caused the cursor to drift past the end of the line, preventing a subsequent x from deleting characters. The cursor now remains in the correct position. After deleting an entire line in Visual mode using V followed by d, the cursor lands on the first non-blank character, and pressing . correctly repeats the operation on that line.

Process management and cleanup commands are now more reliable during routine maintenance and file cleanup. Running claude logs, claude stop, claude kill, claude rm, claude daemon status, claude daemon stop, or claude daemon uninstall no longer causes unexpected logouts when login credentials are near expiration or already expired. When encountering files or directories that cannot be deleted, claude purge previously exited silently or hung in the terminal; it now finishes deleting the remaining items, lists failures, and exits with code 1. On Windows, stopping the status line, hooks, or commands no longer terminates unrelated programs that happen to share the same process ID.

Claude tracks historical progress and permission notifications more reliably during long conversations or automated tasks. Previously, triggering context compaction (a mechanism that condenses long transcripts to free up space) could cause Claude to misjudge tasks finished before compaction as just completed, leading to duplicate work or reverted progress. This timeline confusion has now been fixed. A change to auto-mode rejection messages has been reverted, no longer telling Claude that a rejection covers the entire outcome rather than a single command. When cloud container restarts lose pending /loop wakeups or scheduled tasks, notifications are no longer sent to Claude, allowing the session to stay dormant.

Memory consumption and server load are more balanced when projects connect multiple external tools or run at scale in self-hosted environments. Previously, HTTP MCP (a protocol connecting AI to external tools) connections retained every sent request until closed. This caused a memory leak (where data no longer needed continues occupying memory), which is now resolved. In the list of agents and MCP servers provided to the model, names with non-ASCII characters are sorted after ASCII names. OpenTelemetry (a tool for collecting application runtime telemetry) claude_code.at_mention log entries now emit at most 100 agent events and 100 MCP resource events per prompt read. Self-hosted environments replaced fixed 5-second polling with a 4–6 second jitter interval, preventing multiple instances in the same environment from sending requests simultaneously.

Message routing and permission updates are smoother when collaborating with Claude or running routine tasks in Slack channels. In Enterprise Grid shared channels across multiple workspaces, Claude no longer erroneously reports that a workspace is unconfigured upon encountering an unconnected workspace tag. When administrators update connectors, plugins, skills, or rules mid-task, Claude avoids abrupt interruptions and instead applies changes after finishing the current task. Triggering routine tasks in threads with notes now reliably executes and reports back within the thread. When Claude joins announcement channels where only administrators can post, it joins quietly without posting an unprompted introduction.