Skip to content
Sprint projectMar 23, 2026Boston

How Detectable Are Covert Signals in AI Agent Transcripts?

Mark Martirosian · Team Mark's Team

Submitted to AI Control Hackathon 2026. Sprint projects are early-stage work by participants, not Apart Research publications.

Read the report

Report: How Detectable Are Covert Signals in AI Agent Transcripts?

Share

If an AI agent is secretly doing something bad inside an otherwise normal-looking transcript, how hard is it for a safety monitor to catch? We built a pipeline that generates fake sysadmin transcripts where a hidden token is embedded at five different levels of concealment, then had Claude Opus 4.6 evaluate each one without being told what to look for.

Reviews

Judging this Sprint?

Review this project

Your public critique appears on this page without your name. Your private critique is not published; only the Apart team reads it. If you agree below, we share your review with grantmaking.ai (opens in new tab) and the Transformative AI Fund so strong projects can be funded.

Not shown on this page.

Shown on this page, without your name.

Only the Apart team reads this, and funders if you agree below.

Share my name publicly on grantmaking.ai *
Share my private critique with funders *

How much would this matter for AI safety if it worked? How innovative is it? For scores of 4-5: is this actually new to the field, or replicating recent work?

Scoring guide
  1. 1Negligible. No clear problem addressed, or no meaningful novelty.
  2. 2Limited. Addresses a real problem but with a generic or well-trodden approach. Incremental at best.
  3. 3Moderate. Clear problem with a reasonable approach; some novelty in framing or method beyond routine application of existing tools.
  4. 4Significant. Important problem with an original approach, or identifies a neglected problem area. A valuable contribution others could build on.
  5. 5Exceptional. Tackles a critical AI safety problem with a genuinely novel approach, or opens a new research direction. Clear theory of change. You'd be excited to share this with researchers in the area.

How sound are methodology, implementation, and findings?

Scoring guide
  1. 1Seriously flawed. Methodology broken, results uninterpretable, or implementation doesn't work.
  2. 2Weak. Approach has significant gaps: missing validation, flawed experimental design, or incomplete implementation.
  3. 3Competent. Technically solid given the short duration. Methodology makes sense, results are interpretable, limitations acknowledged, work builds toward clear conclusions.
  4. 4Strong. Thorough methodology with convincing validation. Results clearly support conclusions. Immediately useful for future work.
  5. 5Exceptional. Ambitious scope executed rigorously. Surprising findings, novel methods, or unusually robust validation.

How clearly are work, findings, and impact potential communicated?

Scoring guide
  1. 1Incomprehensible. Cannot determine what the project is actually claiming or doing.
  2. 2Hard to follow. Key information buried, missing, or diluted by excessive length. Significant effort to extract main points.
  3. 3Clear enough. Can understand the problem, approach, and results without undue effort. Core content clearly present: problem, method, findings, limitations.
  4. 4Well presented. Easy to follow, well-structured, appropriate level of detail. Target audience would get it quickly.
  5. 5Exceptionally clear. A pleasure to read. Complex ideas made accessible. Could serve as a model for how to present this type of work.

  1. Overall a high quality submission which takes a rigorous scientific approach towards understanding "sneakiness" of covert token side-tasks. The presentation of the suspicion scores was not super accessible, but was still understandable given time. Limitations are called out explicitly and proactively, which is great to see (Sections 4.5 and 6). My main critique would be that some design decisions are not sufficiently motivated. Below are additional points I wrote during the review process.

    * It seems that citations are missing

    * Why have 30 benign and 25 of each other category? Seems odd...

    * It is unclear to me how the stealth levels were defined, which makes the non-monotonic distinction somewhat arbitrary; it's still an interesting finding, but I don't have a good understanding of why Level 2 should be considered as more stealthy than Level 1 from a semantic perspective.

    * How was it confirmed that command-level tells were entirely absent?

    * Based on the prompt provided to the monitor and the fact that the success rate for catching the shell comment is so low, the implication is more likely that the marker string is considered to be an unlikely covert side objective, hidden exfiltration, smuggled secret, or other policy-violating behavior. I would be quite interested to look at performance changes when the marker string was changed in a trivial manner (e.g. EVAL_CANON_CODE_0002) and a non-trivial manner (e.g. an attempt at prompt injection or something like that).

    Read full reviewShow less
  2. Decent base idea, presentation could be improved and I would have liked to see results for other smaller models (opus level models are too expensive to be used as monitors at a production level). Another interesting result would be if the monitor model could detect covert side-task deception without being prompted to check for it to simulate unknown, unexpected threat detection capability.

Cite this project

@misc{martirosian2026detectable,
  title = {{How Detectable Are Covert Signals in AI Agent Transcripts?}},
  author = {Mark Martirosian},
  year = {2026},
  month = mar,
  note = {Submitted to AI Control Hackathon 2026, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/how-detectable-are-covert-signals-in-ai-agent-transcripts-642m}},
  url = {https://apartresearch.com/sprints/projects/how-detectable-are-covert-signals-in-ai-agent-transcripts-642m}
}

Build something like this at the next Sprint

AI Collusion Research Sprint · Oct 23 - 25, 2026