{"version":"2.1.242","anchor":"session-journal-keys-are-checked-for-consistency","canonical_anchor":"session-journal-keys-are-checked-for-consistency","heading":"Session journal keys are checked for consistency","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/session-journal-keys-are-checked-for-consistency","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Session journal keys are checked for consistency\n\nA key naming a session's own journal is rejected if it also carries agent or run details.\n\n**What**\n\nA key that names a session's own journal is now rejected if it also carries an agent id, an agent path or a run journal, with a message spelling out the rule.\n\n**Evidence**\n\n`a session journal key names the session's own journal: no agentId, agentRelPath or run journal`\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}