Industry Brief

Why invisible AI overlays beat classic browser proctoring

Browser lockdown was built for tab switches and forbidden sites. Invisible interview assistants were built to look like a normal meeting. If your integrity stack still assumes cheating looks like a second face or a focus-loss event, you are measuring the wrong generation of fraud.

Back home

01

Generation 1 controls vs generation 3 cheating

Classic proctoring watches for focus loss, copy-paste, extra faces, and phones. Overlay assistants render answers without leaving the interview surface. Audio copilots listen and coach without a visible second window. Earpiece-plus-phone workflows never touch the enrolled browser. Each generation made the previous control less sufficient.

  • Gen 1: tab switch, notes, second person in room
  • Gen 2: hidden ChatGPT windows and second monitors
  • Gen 3: invisible overlays, audio pipelines, earpieces, open-source forks

02

What Cluely-class tools changed

Products marketed as undetectable meeting or interview assistants listen to audio, read on-screen context, and feed real-time answers through overlays that often stay off shared screens. Even when vendors rebrand toward “meeting notes,” hiring teams still face the same capability used against interviews and exams. Named detection pages help buyers find coverage; durable programs detect the pattern class.

03

Where webcam theater still helps-and where it fails

Webcam checks can still catch downward glances at a second phone, obvious coaching, or identity mismatches. They fail against calm candidates using overlays engineered for eye contact, or hardware channels entirely off the enrolled device. Use webcam as one signal among many-not the primary control.

Integrity gate

Threats get intercepted. Genuine candidates pass through.

A four-scene integrity loop: live session, anomaly detection, layered interception, and verified pass—built for AI-era cheating.

  • Device & session
  • Behavior & language
  • AI assistance
Honrly integrity
Session live
Candidate sessionLive

“When a renewal was at risk, I called the customer the same day and owned the save through Q3…”

Response · 00:14:22
Integrity watch
  • Identity checkok
  • Device postureok
  • Response cadenceok

Hiring pipeline

Without a gate, risk flows into every hire. With Honrly, it doesn't.

Watch one hiring wave: intake, unchecked advance, gated interception, then a shortlist built only from verified sessions.

Candidate stream
Intake
Hiring wave · CSM6 sessions
A. Chen
Ownership 5
In queue
R. Okonkwo
AI assistance
In queue
M. Patel
Judgment 4
In queue
J. Rivera
Hidden overlay
In queue
S. Kim
Evidence 5
In queue
T. Brooks
Paste burst
In queue

Integrity layer

Signals you can review—not a vague risk score

From live feed to flagged event to human resolution—every integrity decision leaves an audit trail.

Integrity timeline
Live feed
Monitoring
  • Identity check
    00:01:02
    clear
  • Hidden overlay
    00:12:04
    flagged
  • Assistance pattern
    00:18:41
    review

Workflow

Integrity in the assessment loop

Detection and evidence review sit alongside scoring—not as a bolted-on afterthought.

Assessment loop
Select
Role · Customer Success Manager
Customer empathy
30%
Ownership
25%
Communication
20%
Adaptability
15%
Conflict resolution
10%

04

What works instead

Composite integrity signals, OS-aware assistance detection where policy allows, ownership probes that break prompt-and-read fluency, custom and rotating problems, and human evidence review. For hardware channels, lean harder on process design and multi-stage corroboration-software alone has honest limits.

05

Candidate experience without false security

Heavy lockdown that still misses overlays trains honest candidates to resent you while sophisticated cheaters pass. Prefer proportionate monitoring, clear rules, and assessments that reward demonstrated reasoning. Integrity should raise signal quality, not only friction.

06

How Honrly positions against overlay-era cheating

Honrly focuses on stealth-assistance patterns, reviewable timelines, live or async operator workflows, and verified behavioral assessments. We do not pretend a browser lockdown is enough-and we do not auto-reject on a single ambiguous cue.

FAQ

Frequently asked questions

Not reliably. Hardware off the enrolled device is an honest boundary. Combine integrity signals with ownership probes and multi-stage checks.

Next step

Still relying on browser lockdown against overlays?