{"version":"2.1.281","anchor":"minor-internals-sync-journal-versions-nested-memory-trigge","canonical_anchor":"minor-internals-sync-journal-versions-nested-memory-trigge","heading":"Minor internals: sync journal versions, nested-memory triggers, session tag timestamps","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/minor-internals-sync-journal-versions-nested-memory-trigge","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Minor internals: sync journal versions, nested-memory triggers, session tag timestamps\n\nSmall internal changes to sync journals, nested CLAUDE.md loading, session tags, a sync notice and MCP server adds\n\n**What**\n\nSeveral small internal changes:\n\n- Sync journal: it now accepts any version up to the current one, not just two exact versions.\n\n- Nested CLAUDE.md: triggers to load a CLAUDE.md file from a subfolder can be queued as pending and are then merged together.\n\n- Session tags: reading a session's tags now also returns `created_at`, the time each tag was made.\n\n- \"Kept your version\" notice: this sync notice now has an `onceKey`, so it is shown only once.\n\n- MCP server adds: adding MCP servers is debounced, so several adds made close together are handled as one. MCP servers are external tools that Claude Code connects to.\n\n**Why**\n\nIn practice, the \"kept your version\" notice should stop repeating. The other changes affect how Claude Code handles work behind the scenes."}