{"version":"2.1.281","anchor":"bg-dispatch-carries-reattachenv-and-retries-while-the-daemon","canonical_anchor":"bg-dispatch-carries-reattachenv-and-retries-while-the-daemon","heading":"bg dispatch carries reattachEnv and retries while the daemon starts","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/bg-dispatch-carries-reattachenv-and-retries-while-the-daemon","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### bg dispatch carries reattachEnv and retries while the daemon starts\n\nBackground dispatch now retries while the daemon starts, carries a reattach environment, and forwards flags like `--settings` when attaching\n\n**Unclear.** The finding does not say what `reattachEnv` contains or when it is present.\n\n**What**\n\nBackground 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:\n\n- Dispatch over the socket retries while the daemon is still starting (`ESTARTING`), up to 40 times at 200 ms apart.\n\n- Dispatch always goes through the socket when a reattach environment (`reattachEnv`) is present.\n\n- The fallback path that uses a file instead of the socket drops environment variables and logs a warning naming the ones it dropped.\n\n- Attaching to agents now passes along `--settings`, `--plugin-dir`, `--mcp-config` and similar flags.\n\n- Provider environment is written for host-managed providers.\n\n**Why**\n\nDispatching 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."}