Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.242 Home All releases ←olderv2.1.241 v2.1.243newer→
Claude Code v2.1.242

Owner messages in Claude Code Projects arrive as marked user turns

You'll notice
Useful3 Signal4
Projects

Project owner messages arrive as marked user turns that cannot approve prompts on your behalf.

What

In a Claude Code Project, messages the server says came from the project owner are replayed into the session as your own user turns, each opening with a marker the harness writes. New instructions say such a turn counts as you speaking, but a bare "yes" in one clears no soft block, answers no permission prompt, and never licenses editing settings or CLAUDE.md. Everything else relayed is treated as external content, and asking Claude to do what a sender was already denied is called "permission laundering - BLOCK".

Details
  • Applies to messages arriving by relay and through the fetch_messages, fetch_thread and fetch_project_timeline tools.
  • The supporting code caps how many owner rows are surfaced, de-duplicates by id and version, and drops rows that are truncated or badly timestamped.
  • No environment variable or flag guards this; it applies to sessions that are a thread in a Project.
Evidence

[Verified message from this session's user written

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.242 →