Under the hood
Useful1 Signal2
Opening the background agents view runs an empty registration step with no visible effect.
A placeholder registry is called from the /agents view but registers an empty object nobody reads.
What's wrong with this entry?
Anonymous. No account, no email.
/agents
What
Opening the background-agents fleet view (/agents) now loads an extra module and calls a registration step before drawing anything. It registers an empty object and no code reads it back, so there is no visible effect either way.
Details
registerToolHosts()stores a literal{}into a per-host singleton; the singleton exposes a runtime value that falls back to a frozen empty object, plus a flag saying whether anything was registered.- Neither of those is read anywhere in the build, and
{}is the only value ever registered. This is a seam wired up ahead of what will eventually fill it.
Evidence
registerToolHosts
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.235
Question options with identical text are no longer confused with each other
Both mention agent
-
v2.1.236
Teammate messages whose summary swallowed the body are split back apart
Both mention agent
-
v2.1.238
Claude is told to stay in a worktree even when it did not create one
Both mention agent