{"version":"2.1.248","anchor":"non-restricted-remote-sessions-treated-as-local-for-read-db-","canonical_anchor":"non-restricted-remote-sessions-treated-as-local-for-read-db-","heading":"Non-restricted remote sessions treated as local for read_db output paths","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/non-restricted-remote-sessions-treated-as-local-for-read-db-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Non-restricted remote sessions treated as local for read_db output paths\n\nArtifact database write limits only apply to remote sessions that are also restricted.\n\n**What**\n\nThe safety check on where the artifact database may write documents now only applies its remote-session rules when the session is also marked restricted. The refusal wording is unchanged.\n\n**Evidence**\n\n`read_db does not save artifact database documents as`\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}