From 17a75d2726603ba7300a6e78d248df9d3ffba4ab Mon Sep 17 00:00:00 2001 From: tegwick Date: Tue, 24 Feb 2026 23:48:28 +0100 Subject: [PATCH] Make first-message behaviour explicit in CLAUDE.md template MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Add one-line imperative at the top of the Session Protocol: 'On receiving your first message — before writing any response text — call get_state_summary() immediately.' Previously Claude would wait for a substantive prompt before acting. Now any first message (including 'start', 'go', or just Enter) triggers the tool call immediately, after which the First Session Protocol takes over. Co-Authored-By: Claude Sonnet 4.6 --- state-hub/scripts/project_claude_md.template | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/state-hub/scripts/project_claude_md.template b/state-hub/scripts/project_claude_md.template index 88171b6..e0cf2a0 100644 --- a/state-hub/scripts/project_claude_md.template +++ b/state-hub/scripts/project_claude_md.template @@ -10,6 +10,10 @@ 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. + **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: