advise

Ask the council about this conversation.

What makes this different from /ask

/ask sends a question you typed. This sends a slice of the conversation itself, so the providers can see the reasoning rather than your summary of it. That is the point: a model given only your framing tends to agree with your framing, and agreement produced that way measures the framing, not the work.

It is also why every run shows you the payload before anything is sent.

Step 1: Resolve this conversation's transcript

The session id is substituted into this file at invocation:

bash ${CLAUDE_PLUGIN_ROOT}/scripts/session-transcript.sh ${CLAUDE_SESSION_ID}

If that fails, stop and report why. Do not search for a transcript by modification time or pick the newest file: a teammate agent running in the same directory writes its own transcript, and the newest file is frequently theirs.

Step 2: Digest a bounded window

Default to the last 25 turns. --turns=last:N overrides it; --turns=all is available but say plainly that it sends the whole conversation.

DIGEST=$(mktemp -t council-digest)
bash ${CLAUDE_PLUGIN_ROOT}/scripts/transcript-digest.sh --turns last:25 "<path>" > "$DIGEST"
wc -c "$DIGEST"

Use a plain temporary name. The file path is interpolated into the prompt the providers receive, so a name carrying the session or directory tells them things the digest itself does not.

The digest carries human turns and assistant replies. It excludes tool results, tool inputs, thinking blocks, hook output, teammate and peer messages, and compact summaries.

Step 3: Show the payload, then ask

This step is the privacy control and it is not optional. The script cannot be the gate: inside a subagent the ambient session id names the parent conversation, so nothing the script can read tells it whose words it holds.

Show the user, before sending:

• the byte size and how many turns it covers
• the first few lines of the digest, via head
• which providers will receive it