From 69763056fa4183f1772a994da3400bb71de2b06d Mon Sep 17 00:00:00 2001 From: tegwick Date: Thu, 26 Mar 2026 17:48:52 +0100 Subject: [PATCH] chore(session): read .custodian-brief.md before MCP call in session init Co-Authored-By: Claude Sonnet 4.6 --- CLAUDE.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/CLAUDE.md b/CLAUDE.md index 396c3dc..02f7183 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -10,13 +10,13 @@ exposes tools for reading and writing state without touching the API directly. ### Session Protocol -**On receiving your first message — before writing any response text — call -`get_state_summary()` immediately.** Do not greet, do not ask what to do. -Call the tool first, then respond based on what you find. +**On receiving your first message — before writing any response text — orient +yourself immediately.** Do not greet, do not ask what to do. **At the start of every session:** -1. Call `get_state_summary()` — orients you to active workstreams, blocking decisions, - and recent progress. If it fails, the API is likely offline: +1. Read `.custodian-brief.md` — offline-safe orientation that works without MCP. +2. Call `get_state_summary()` for richer cross-domain context (skip if unreachable). + If it fails, the API is likely offline: ``` cd ~/the-custodian/state-hub && make api ```