{"version":"2.1.224","anchor":"clearer-message-for-a-relative-memory-path","canonical_anchor":"clearer-message-for-a-relative-memory-path","heading":"Clearer message for a relative memory path","tier":"notice","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/clearer-message-for-a-relative-memory-path","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Clearer message for a relative memory path\n\nThe error for a relative memory path now suggests a properly joined path.\n\n**What**\n\nThe refusal you get for passing a relative memory path now quotes a correctly joined suggested path instead of gluing a prefix onto it.\n\n**Details**\n\n- Memory conflict errors now also carry the conflicting path.\n- Pre-creating the team-memory directory for team-scope stores was dropped from the load path.\n\n**Evidence**\n\n`Memory paths are absolute and start with \"\/\"`\n\n- Area: Memory\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}