chief-of-staff

You can maintain persistent memory across Claude Code sessions by using a vault-based Chief of Staff loop that loads priorities and memory from a local Obsidian vault, preventing session amnesia and task drift. It boots up your context automatically each time.

Yes, Obsidian works with Claude Code to manage daily morning briefings, mid-session checkpoints, and end-of-session reflections. The system tracks waiting-for items and queues open threads by reading and updating your vault state.

The best way to set up an ADHD-friendly productivity loop is running four commands—setup, start, sync, and wrap—that shrink tasks when stuck and avoid guilt framing. This routine turns progress into repeatable steps without shame-based motivation.

No external package dependencies are required. You only need Claude Code installed alongside a local Obsidian vault, plus a YAML-frontmatter-defined skill instruction set to load and operate the four-command loop.

To stop AI session amnesia from resetting your priorities, a vault-based system saves your to-do state and persistent memory locally. The assistant loads this context on startup so it already knows what matters without re-figuring it out.

You should not use this vault-based chief of staff loop if your workflow does not use Claude Code or if you need cloud-based multi-device synchronization, because the system relies entirely on a local Obsidian vault for persistent state tracking.