One chat that runs all your other chats is a real trick. Here is why it breaks after a week, and the setup I use instead, with the exact prompts.
In Claude Code, one session can check your other sessions, rename them, and send them messages. Anthropic also has an official screen for this called agent view.
HYPEIt is not a new feature called "master session". It is a prompt you give one chat.
CATCHThat boss chat is still just a chat. It reads every other chat, so it fills up fast. Start a fresh one and it forgets your whole setup. And it only knows what is going on when you ask it.
The memory file is the fix for "it forgets". Separate threads are the fix for "it fills up".
You are my coordinator for [project name]. Keep a file called MEMORY.md with my decisions, preferences, links and open tasks. Read it at the start of every session. Update it the moment I decide something. When I give you a task, do not do it here. Start a separate session for it, name it with a verb and the goal, and track it. Only bring me two things: work that is finished, and decisions that need my yes. Keep your replies short.
New task: [what you want done]. Start a separate session for it. Tell it to keep a checklist, to read MEMORY.md first, and to stop and ask me before anything that can't be undone (publishing, sending, deleting, spending money).
What's waiting on me? Check every task session and give me three short lists: needs my yes, finished, still working. One line each, most urgent first.
Works best in Claude Code, where sessions can start and message each other. In the regular Claude app, create a Project, put MEMORY.md in the project files, and open one chat per task inside it.
My part was the amber dots.
One email unlocks the whole library - every guide, free, forever.
FREE · NO SPAM · YOU'LL ALSO GET OCCASIONAL AI TIPS FROM @AI.WITHMB
Something went wrong - email mb@thewickfirm.com and I'll send you the guide directly.