Background dispatch hands work to a daemon, a helper process that runs in the background, usually over a socket, which is a local connection between programs. Several things about it changed:
Dispatch over the socket retries while the daemon is still starting (ESTARTING), up to 40 times at 200 ms apart.
Dispatch always goes through the socket when a reattach environment (reattachEnv) is present.
The fallback path that uses a file instead of the socket drops environment variables and logs a warning naming the ones it dropped.
Provider environment is written for host-managed providers.
Why
Dispatching just after the daemon launches is less likely to fail, and an attached agent keeps the settings, plugins and MCP servers you started with. If you see the warning about the file path, the listed environment variables did not reach the dispatched work.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtThe finding does not say what `reattachEnv` contains or when it is present.
Anthropic's release notes agreeFixed --plugin-dir on a folder of plugins that also has a .claude-plugin/marketplace.json loading one empty plugin instead of the plugins in…
