Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.265 ·

Agents list screen instance now reused across re-renders

The 'claude agents' list screen now reuses its render object instead of recreating it each frame

TierUnder the hoodhow much it should matter to you
Useful1my rating, 1 to 5
Signal0worth watching, 1 to 5
AreaBackground Agentswhat it touches
KindInternal Changesin v2.1.265,
Under the hood

The 'claude agents' list screen now reuses its render object instead of recreating it each frame

What

The screen shown by the claude agents command now caches and reuses the same underlying screen/render object across re-renders, instead of implicitly building a new one every time the screen redraws.

Why

This is an internal efficiency change to how the agents list screen renders; it doesn't change what the screen shows.

Read from
Names in the bundleclaude agents
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 A small documentation edit on What's new touched a line naming claude agents after this was published. Also this week: **fork mode** is on by default in interactive sessions, so Claude can delegate a side task to a subagent that inherits the full conversation; **GitLab** merge request URLs work with `--worktree` and the `claude agents` view… whats-new/index see the edit
Confirmed since Anthropic's documentation has since written up claude agents, on Claude Code changelog. * Fixed `claude agents`: pressing ← again at a natural pace to go back to the agent list no longer gets ignored until you pause for over a second changelog see the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up claude agents, on Claude Code changelog.

See this entry in the whole of v2.1.265 →

Feedback