GPT-5.2 detector
What the GPT-5.2 detector adds to a review
You already noticed something. The GPT-5.2 detector turns that into language: paste the passage, our server hands it to one hosted model, and the response describes the writing signals present with a reason attached to each one. It reads back as an argument you can quote in a note, which a percentage never does.
The route is remote, so the text leaves your device. Five runs are free in any rolling 24 hours, the window is 1 to 12,000 characters, and there is no account to create or manage.
What it never returns is an authorship claim. The instruction behind these routes tells the model to describe observable signals and their limits and never to say which AI wrote a text, so plan your process around evidence rather than verdicts.
The three steps
How to run the GPT-5.2 detector in three steps
The run is quick. Choosing what to run is the part that matters.
- Step 1
- Pick a representative stretch, not the single paragraph that irritated you. One paragraph is a thin basis for a conversation about someone's work.
- Step 2
- Run the check. One call, one of your five daily runs, and a written response describing what the passage does.
- Step 3
- Set the findings beside the writer's earlier work and any draft history you have before deciding whether there is anything to raise.
Update your heuristics
The formatting tell your team should retire
Most review teams still spot AI by its shape: bulleted lists, bolded subheads, everything neatly chunked. That heuristic is now pointing the wrong way, and a team applying it to recent submissions will misjudge in both directions.
- What the test found
- Summarising dense material, the previous version broke copy into bolded subheads and bullet points while GPT-5.2 returned solid blocks of text the testers called much less digestible.
- The scores
- Across eight writing tasks the older version scored 60 out of 80 and the newer one 52, so the decline is measured rather than anecdotal.
- What it means for review
- An unbroken wall of prose is no longer a mark of human effort, and a clean bulleted summary is no longer a mark of a machine.
- What replaced it
- Title case in headings, which the same testers docked a point for and called one of the most obvious signs of AI copy.
- The register check
- Asked to write a price increase email, both versions produced flat formal phrasing with no attempt at warmth. A message that should soften and does not is worth reading twice.
After the run
What to write down
If a check ever becomes part of a conversation with a student, a writer or a manager, these are the details you will want to have kept. None of them takes more than a minute.
- The passage and its length
- A finding on 200 words and a finding on 2,000 words are not the same evidence and should not be recorded as if they were.
- The date of the run
- Models change and so do checkers. A result is a reading taken on a particular day.
- The findings word for word
- Copy what the check returned rather than your paraphrase, so the reasoning survives being retold.
- What you knew already
- Earlier drafts, previous work, the brief. This context is what turns a signal into a concern or dissolves it.
- The claim not made
- Note that no version or authorship claim was produced, because the tool does not make one.
When to discount a flag
Submissions where a flag means little
Build the exceptions into the process rather than discovering them during a difficult meeting. A detector vendor that advertises a 97 per cent detection rate publishes the caveat itself: short, generic and essay-like text is the most likely to be flagged wrongly.
Formulaic genres belong in the same bucket. Methods sections, policy summaries, legal boilerplate and product copy written to a template are repetitive because the form requires it, and a signal reading variety will read the genre instead.
Non-native English writing is the third known population. The same vendor is blunt about the rule that follows: no current AI content detector should be used as a standalone check.
Planning
Five runs against a stack of submissions
The allowance is the real constraint. Five runs per rolling 24 hours means a marking session cannot check everything, so spend runs where your own reading has already raised a question.
Each run takes 1 to 12,000 characters, about two thousand words. For a long piece, run a representative section rather than trying to fit the whole thing, because a section normally answers the same question.
There is no queue, no batch upload and no API. One passage, one run, one written answer, and the count rolls forward from each use rather than resetting overnight.
Worth knowing
Why GPT-5.2 prose became a talking point
It is unusual for a model's writing to be criticised by the company that shipped it. At a developer town hall in January 2026, OpenAI's chief executive said of the writing complaints: I think we just screwed that up, and explained that most of the effort in 5.2 went into intelligence, reasoning, coding and engineering.
For a reviewer, that context is reassurance rather than a method. If recent submissions read worse than the ones you saw last year, you are not imagining it. It still does not let anyone say which model produced a given paragraph, and this tool does not try.
In use
Where a GPT-5.2 detector fits in a team
It fits where you need words for a concern: preparing to ask a student about their process, deciding whether to send a commission back, comparing a written application against how someone speaks in an interview.
It does not fit as a gate or a grading input. No output here is proof of authorship, we hold no affiliation with OpenAI, and nothing predicts what a different checker would say about the same text.