06-reference/research

automode classifier channel text injection surface

2026-10-22·research-brief·source: deep-research·by Ray Data Co (deep-research synthesis)
auto-modeprompt-injectionchannels-agentagent-safetysession-management

The channel is real and it does grow, but the untrusted text accumulating in it is ours, not a third party's

The question

"Does the reasoning-blind auto-mode classifier's exposure to ~16 hours of accumulated third-party iMessage/Discord text constitute a prompt-injection surface that grows with session length?"

Derivative of [[2026-08-13-auto-mode-approval-fatigue-channels-session-pattern]], which established that the classifier reads user messages and named this as an untested injection question. Two parts of the premise have decayed since it was filed and are corrected below.

What we already know (from the vault)

What the web says

Convergences and contradictions

Synthesis for RDCO

The mechanism is real, the growth is measured, and the premise's "third-party" is wrong. Inbound iMessage does land in type:"user" position on disk, which is the same channel Anthropic says the classifier reads, so the surface exists rather than being hypothetical. And it does grow monotonically with session length: cumulative user-position text roughly quadruples to sextuples between hour 2 and hour 18 of a long session, with no plateau. But the thing growing is not third-party text. The allowlist is one handle long, groups are off, and every one of 370 inbound messages across three weeks of the largest sessions came from the founder. On the current configuration there is no untrusted human writing into the classifier's input, and the premise as filed overstates the exposure by assuming a sender population that access.json does not permit.

Where the untrusted text actually accumulates is a surface the parent brief did not name, and it is worse-shaped than the one it did. Subagent hand-backs arrive as separate user-position messages ("Another Claude session sent a message", <agent-message from=...>), not as tool results. Anthropic's two published defenses both route around this. The server-side injection probe scans tool outputs, and whether it also scans cross-session agent messages is not documented (U). The classifier's structural defense is that it never sees tool results, which does not help when the text has been re-emitted into the user channel. So RDCO's own fan-out pattern builds a laundering path: a subagent fetches web content as a tool result, where it is probe-scanned and classifier-invisible, then summarizes it into a hand-back that lands in the parent's user-message position, where it is classifier-visible and sits exactly in the slot the classifier treats as evidence of user intent. We run 6-29 of these per long session and the volume is an order of magnitude larger than the channel text the question asked about. The same applies in smaller measure to the founder's own forwards: he routinely pastes and screenshots third-party content, which is how third-party text actually reaches the classifier today, laundered through an allowlisted sender. Our pasted-content carve-out discounts that text for Ray; nothing discounts it for the classifier, which has no fence-awareness and no notion of who typed what.

The decisive fact is not publicly documented, and the honest answer stops here. Whether this is a surface that grows with session length depends entirely on whether the classifier's transcript is built from the full session or from the live, post-compaction context, and Anthropic does not say. It matters a lot: session 520dc14e compacted twice, at +4.0h and +14.8h, so if the transcript follows the live context then accumulation is bounded by the compaction ceiling and resets twice a day for free, and the answer to the question is a qualified no. If it is built from the session log, accumulation is unbounded until 4am and the answer is yes. One independent experimenter's log capture suggests the classifier gets full tool-call history, which weakly favors "full session," but that is a single secondary observation about tool calls rather than user messages and is not strong enough to carry the conclusion. The test that settles it, which I did not run: capture the classifier's own payload for a single tool call before and after a compaction event in the same session, and check whether a pre-compaction user message is still present in the post-compaction transcript. That requires either Anthropic documenting the transcript construction or reading the classifier request from telemetry, and it must not be done by attempting an injection against the live Channels agent.

Practical read, bounded by what is verified. Do not treat this as an open hole requiring a configuration change. The exposure is real but the writers into it are the founder and our own subagents, the blast radius is capped by the 1-denial hard gate and the 4am reset, and auto mode was never the security boundary in this architecture. Do stop describing the channel surface as the injection risk; the fan-out hand-back path is the larger and less-defended one, and it is the one worth instrumenting if any of this gets instrumented. And note that every published number for this classifier was measured on coding traffic, so the 17% false-negative rate is the floor of our uncertainty, not an estimate of our miss rate.

Why this is in the vault

It closes the injection-surface follow-up left open by [[2026-08-13-auto-mode-approval-fatigue-channels-session-pattern]] with a measured negative on the channel half (one allowlisted sender, no third parties, Discord gone) and relocates the real finding onto the subagent hand-back path, which changes what any future gating or instrumentation work on the Channels agent should target. It also prevents the "16 hours of third-party channel text" framing from being repeated in a founder-facing artifact, since access.json does not permit the sender population that framing assumes.

Open follow-ups

Related

Sources

Primary (fetched and verified against page text, two targeted passes):

Secondary (surveyed, marked U, not relied on for any conclusion):

Local measurement (2026-10-22, read-only; no settings, access.json, or permission config touched):

Not verified / would require a test I did not run: whether the classifier transcript is the full session or the live post-compaction context; whether the server-side injection probe covers cross-session agent messages and task notifications; whether image blocks reach the classifier; RDCO's own classifier false-negative rate on MCP write traffic.

Corrections to the question as posed: the Discord half is dead (channel retired 2026-09-18, plugin uninstalled). "Third-party iMessage text" does not exist under the current allowlist — one allowed handle, the founder's — so third-party content reaches the classifier only when he pastes or screenshots it.

Vault paths cited