{"version":"2.1.246","anchor":"storage-backend-gains-two-host-supplied-options-with-no-call","canonical_anchor":"storage-backend-gains-two-host-supplied-options-with-no-call","heading":"Storage backend gains two host-supplied options with no caller","tier":"internal","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/storage-backend-gains-two-host-supplied-options-with-no-call","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Storage backend gains two host-supplied options with no caller\n\nStorage can accept a host-supplied config path and per-space service declarations, but nothing passes them.\n\n**What**\n\nThe v5 storage backend constructor accepts two new options from an embedding host: a global config file path, and a per-space declaration of which storage spaces the host will serve. Both occur only inside the factory in this build, so the defaults hold: every space is served by the host and the global config path resolves as before.\n\n**Details**\n\n- Each space in the serve declaration must be true, false or `absent`, making it `host`, `refused` or `absent` respectively; refused spaces produce messages such as the backend not serving `system`.\n- Seeding the global config path when it was already resolved logs a warning and keeps the first answer.\n- This is surface for programs embedding Claude Code, not something reachable from the CLI.\n\n**Evidence**\n\n`createLocalHostFiles: each serve[space] must be true, false or 'absent'`\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Present in the build but not switched on"}