{"version":"2.1.239","anchor":"empty-placeholder-registry-runs-when-you-open-the-background","canonical_anchor":"empty-placeholder-registry-runs-when-you-open-the-background","heading":"Empty placeholder registry runs when you open the background agents view","tier":"internal","area":"Agents","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/empty-placeholder-registry-runs-when-you-open-the-background","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Empty placeholder registry runs when you open the background agents view\n\nOpening the background agents view runs an empty registration step with no visible effect.\n\n**What**\n\nOpening 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.\n\n**Details**\n\n- `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.\n- 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.\n\n**Evidence**\n\n`registerToolHosts`\n\n- Area: Agents\n- Names: `\/agents`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}