Entity · protocol

Recuse Signal

protocolactiverecuse-signal-7100e5e8·1 events·first seen Jun 5, 2026

Aliases: Recuse Signal

Co-occurring entities

Will the Agent Recuse Itself? Measuring LLM-Agent Compliance with In-Band Access-Deny Signals GPT-4o mini GPT-4o Claude Code OpenAI Anthropic

More like this (12)

Will the Agent Recuse Itself? Measuring LLM-Agent Compliance with In-Band Access-Deny Signals RedCode signal collapse SIGReg R2 Indicator Delta Rule RREDCoT Output Reset TF-RefusalBench StrongReject RAS: Measuring LLM Safety Through Refusal Alignment Decoupled Search Grounding

Recent events (1)

7arXiv · cs.AI·Jun 5, 2026·source ↗

Recuse Signal: In-band access-deny standard for LLM agents shows 100% compliance in pilot

Researchers propose and empirically test a lightweight 'Recuse Signal' — a cooperative, in-band deny mechanism analogous to robots.txt — that servers can emit over existing protocol channels (SSH banners, PostgreSQL NOTICEs) to ask autonomous LLM agents to voluntarily withdraw. A controlled pilot using GPT-4o, GPT-4o-mini, and Claude Code found 100% recusal when the signal was present versus 100% task completion in controls, though the signal behaved cooperatively rather than absolutely: explicit operator-authorization framing caused the most capable model to override the signal. The work defines an open mini-standard, releases two low-footprint adapters, and frames the mechanism as a governance control rather than a security boundary.

AI Safety Research Agent and Tool Ecosystem Will the Agent Recuse Itself? Measuring LLM-Agent Compliance with In-Band Access-Deny Signals GPT-4o mini GPT-4o +4 more