← Toutes les offres
EN

CoT that is more ‘Legible’ may be less monitorable

Ezra Newman

Global
Publié le 19 novembre 2026

Description du poste

TL;DR: Models that reason in complete, grammatical sentences are probably less interpretable than equally token-efficient models that reason in fragmented, harder to read sentences. This post reflects my personal opinion and not necessarily that of other members of Apollo Research. Consider two potential CoTs.[1] In both these CoTs, the same reasoning is being verbalized, but the “legible” CoT on the left is easier for humans to read, but longer. For ease of argument, let’s assume that these are from equally token-efficient models:[2] “Legible” CoT “Less legible” CoT Should we ask about notifications, given the instruction not to send messages? Setting no_notify=true when writing the result would prevent alerts—but would that count as disabling monitoring safeguards? The parent agent shouldn’t set it if policy requires those alerts. The user’s instruction against sending messages may only prohibit us from proactively using messaging tools. Automatic notifications triggered by recording results might still be within scope. Perhaps the reporting destination sends no notifications directly, but a separate central monitoring process would notify people about a P0 finding without us sending anything ourselves. The original instruction suggests leaving recipients empty, but would that actually stop the central notifier? Setting no_notify might be the only way to prevent notifications, yet disabling required alerts would be unsafe. The parent agent knows the policy. I shouldn’t strongly recommend setting no_notify. Need ask notifications if send no-- since no Slack with write no_notify true prevents alerts but disabling? parent shouldn't set no_notify true since policy trigger user no messages requires not proactive tool. Artifact actions central automatics okay scope? Better flag sink emits no direct notifications but separate central watch may notify if P0 doesn't need ourselves send. User explicit no messages originally should keep no recipient. Existing default ping