How to detect Cluely without playing detective on vibes

Start with a disclosed technical check, then use the guide's prompts and evidence notes to separate real signals from awkward interview behavior.

Buy the $17.99 guide

The private check

The exact macOS/Linux command is packaged inside the paid guide with output notes, false-positive handling, and the Windows equivalent.

locked command card

$ xxxxx xxxxx 'xxxxxx|xxxxxxxx.xxxxx'

Use the check as a fast signal, not a final verdict. The guide shows what the output can prove, what it cannot prove, and what to ask next.

You do not control the candidate's computer. This workflow only works when expectations are clear, the candidate shares willingly, and the interviewer treats the output as evidence to discuss rather than power over the machine.

Responsible detection

Five-step detection process

Disclose the tool policy before the interview.

Ask for candidate consent before any screen-share or terminal check.

Run the private process-name check from the guide and review the output.

Validate suspicious answers with follow-up constraints.

Document the facts, the explanation, and the next action.

Signal calibration

Strong signal

Visible process match, admission, or refusal to follow a disclosed condition.

Medium signal

Cannot explain details they just introduced or quality drops when constraints change.

Weak signal

Uniform pauses, eye movement, or polished generic wording without other evidence.

Get the private command card

The paid guide includes the macOS/Linux check, Windows fallback, consent script, stop-command guidance, evidence log, scorecard, and prompt templates.

Get launch access for $17.99