4,059 people on Reddit described them between 1 January and 5 October 2026. Where somebody posted a screenshot or the text itself, it is shown with the spots they pointed at. The list updates live, and the rules to avoid them come with it.
9 habits named by 160 people between 1 January and 5 October 2026.
1234
1Glowing outlined KPI cards
2Sparkle decoration
3Purple accent button
4Cards inside a card
64 people
Gradients and purple glow
Gradient buttons and softly glowing rounded cards sit on a dark navy page, and the accent colour is usually indigo or purple-blue.
“It’s always the same recipe: massive border-radii, nested-box-hell, and those tacky gradients.” Reddit
Evidence
The label says purple. For ChatGPT and Codex the part people name most is gradients everywhere. They fill hero backgrounds and buttons, and cards get them too. They usually sit on a dark page with rounded cards whose borders glow. Cards are often nested inside cards, with a row of three stat cards. Purple or purple-blue is the colour people name, yet many treat "AI purple" as the common look of all AI tools and do not pin it on ChatGPT. By mid-2026 several users say newer GPT models moved away from purple, with GPT-5.6 going toward neon green. The gradients and cards are still reported.
Signs people name, with the number of people naming each
Gradients on everything Gradient buttons and gradient hero backgrounds, and some mention gradient overlays. This is the single trait named most for ChatGPT and Codex.
22
Purple or purple-blue accent Indigo buttons and purple-to-blue or purple-to-pink gradients, the so-called "AI purple".
18
Glow and neon on a dark page A dark navy or black background with cards that have a coloured glowing border. Some call it neon UI.
11
Cards, and cards inside cards Every block gets a rounded card and boxes nest inside boxes. Border radii are big and pills are common.
10
Three stat cards and a SaaS hero A big headline and subhead over a single button. Below come three identical cards or KPI tiles.
5
Glass and soft shadows Glassmorphism and neumorphism-style shading. Shadows appear at random.
5
Side highlight lines and small labels A coloured line runs down one side of a tile. Small badges appear, and an eyebrow label sits over every section.
3
Comes back despite instructions Memory notes and design skills reduce it. It returns when the prompt is vague.
4
Posted cases
1234
1Glowing outlined KPI cards
2Sparkle decoration
3Purple accent button
4Cards inside a card
A good-looking budget dashboard. The critic likes it and still calls it every AI dashboard cliche. It has a dark page with glowing outlined KPI cards and three stat cards up top. Sparkles and purple and pastel accents finish it off.
A tidy school timetable site on dark navy with a blue gradient hero card. Below it sit a row of three tinted stat boxes and tinted icon cards. The guide's author calls this gradient habit ChatGPT's biggest sign.
A clean, competent agent form its maker is proud of. It shows the quieter end of the habit. One saturated blue colours the button and the pill tags, and it also marks the selected state. A commenter asked why AI picks only purple or blue.
A government service portal with a blue gradient welcome card and a dark-to-red gradient button. The guide's author picks these out as unpleasant ChatGPT gradients.
The all-AI look (Inter, purple gradient, three cards). Most purple complaints say "AI" and name no vendor. The marks more specific to ChatGPT are gradient buttons and glowing card borders. Nested cards are another.
Claude's look. People tie Claude to cream backgrounds and serif headlines with mono labels. One Codex user reports getting that mono-plus-brown-italic look, so the two now overlap.
Gemini's look. People describe Gemini pages by a status bar with a small glowing dot and a hacker-style font. Gradients do not come up for Gemini.
Objections
Humans made this look first. It is generic modern SaaS from Dribbble and startup sites, and hand-built sites now get accused of AI because of it.
OpenAI has no monopoly on it. Users report the same indigo and purple-blue gradients from Claude and from tools such as v0 and Lovable.
Some say it is just a default that a plain instruction removes ("don't use any gradients").
Some users rate ChatGPT's GUI design as good. They see the look as enough for clients who just want a working site.
Changes over time
In April 2026 the Codex developer prompt for GPT-5.5 adds frontend rules against card abuse such as cards inside cards, and against glowing orbs. A leaked prompt tells the model to limit dominant purple and purple-blue gradients.
In July 2026 users say GPT-5.6 Sol "trained out the purple" and leans to neon greens and yellows. They add that GPT models are usually good at avoiding blue and purple.
Some still say GPT-5.6 drifts back to purple next to grey and green. They add that it uses too many cards and pills. Gradients are still named in September 2026.
Cards inside cards 38
Content in a bordered, rounded card nested inside another bordered card or panel marks the habit, and pill badges with chips sprinkled on top add to it.
When Codex or ChatGPT builds an interface without a design spec, it wraps nearly every piece of content in a rounded, bordered card. Then it puts those cards inside larger bordered containers ("cards in cards in cards"). Pills and chips come with the cards. Think of status badges and tags, or "+4%" bubbles. A row of KPI stat cards sits at the top, and a short explanatory subtitle often appears under every heading. Commenters say it reads as a dashboard even when the product is something else, and several note it looks like ChatGPT's own web app. Cards on their own are a generic AI-UI ingredient. People single out the nesting as the GPT part, along with its refusal to stop when told to.
Signs people name, with the number of people naming each
Cards everywhere as the default layout Whatever the product, the page is built from rounded cards. Names for it include "card soup" and "card slop". "Card spam" is another.
20
Cards nested inside cards Bordered cards sit inside bordered containers, several levels deep ("card-ception", "cards in cards in cards").
11
Pills and chips on everything Status pills and tag chips get stacked onto the cards, along with small badges.
6
Overly rounded corners Large radii on every card and button. Inputs get them too.
6
Dashboard look with stat cards on top Three KPI cards run across the top, and the page feels like a SaaS dashboard even when the task has nothing to do with one.
4
Unnecessary subtitles and explainer text Each card or section gets a subtitle or copy that explains obvious functionality. Sometimes it is commentary about the site itself.
4
Borders on every section Where there are no cards, every section still gets its own border. So does every container.
2
Looks like the ChatGPT app itself People say the card-and-chip style mirrors ChatGPT's own web UI.
2
Posted cases
1234
1Three stat cards on top
2Glowing rounded card border
3Cards inside a card
4Another card column
A polished, friendly budgeting app. Every region is a bordered rounded card, and smaller cards are nested inside the Expense overview panel.
In a comparison of three models all screens use cards. GPT 5.4's version boxes even the greeting and the tabs, and puts boxes inside boxes around the sub-figures.
The generic AI landing page (purple gradient over Inter text, three identical cards). People blame that look on all models. The GPT complaint is about cards nested in bordered containers with pills and chips, spread across the whole app instead of one hero with three feature cards.
Dark neon dashboard with glassmorphism. It often appears together with the cards. It is a choice of palette and finish, and the card habit also shows up on plain white UIs.
Claude's web look. People link Claude with a serif headline and a small spaced label on cream and terracotta. They link GPT with structure built from bordered boxes and chips.
Objections
Several people say cards and rounded corners are generic modern-SaaS trends that existed before AI, which now mass-produces them. Gradients belong in the same group. They see nothing bad in these as such.
People describe the landing page with a purple gradient over Inter text and three cards in a row as what every AI builds. ChatGPT is one of many.
One commenter says Claude also makes the same few designs and just has nicer defaults. For this commenter the GPT part is the love of cards and unnecessary subtitles.
People noticed that a gpt-5.6 preview (iris-alpha) built a UI with no cards. Its sections still had heavy borders.
Changes over time
People said GPT-5.5's launch examples showed the same cards in cards as GPT-5.4. An early 5.5 user said it "still absolutely loves cards" but improves bad UI better when asked.
In April 2026 the Codex developer prompt was updated with frontend rules naming card abuse and cards-within-cards.
Users still reported GPT-5.6 Sol (July 2026) overusing cards and pills, the same as 5.5.
A GPT-6 Astra showcase in September 2026 was still described as the default AI UI language. It had rounded cards and pill buttons.
Same fonts on every page 38
Every GPT-built site seems to use the same safe geometric or corporate sans with monospace for numbers and labels, and newer pages add an italic accent word in the headline.
Most commenters name no typeface. They say the fonts are 'the same' as every other site GPT-5 or Codex made, and they notice them as part of a package with the colours. Gradients and cards belong to it too. When they get specific, the descriptions split by period. Earlier posts name Inter or a 'safe sans-serif', or corporate minimalist faces such as Avenir Next or Gill Sans. Codex users in mid-2026 complain about a 'brown italic mono font' and an italic word in the headline that the model keeps even when asked for a fresh design. Several commenters call this pairing 'the Claude AI font' when they see it on GPT 5.6 pages, so the newer look overlaps with Claude's serif-plus-italic style. A smaller strand is about inconsistency. Font weights and sizes get mixed inside one screen.
Signs people name, with the number of people naming each
Same fonts as every other GPT-made site Familiar type choices, rarely named, repeat across unrelated projects. Commenters list them next to the colours and gradients, and next to the cards.
13
Italic headline accent mixed with serif or mono An italic word in the hero headline, or serif mixed with sans. Some see a brown italic paired with a blocky mono face. Codex keeps it even when asked to redesign.
5
Inter or another safe sans-serif Inter with a purple gradient and three cards, or a 'droll sans-serif hero section'. Commenters treat this as the generic AI look.
4
Inconsistent weights and sizes Font weights vary inside one UI and the buttons and fonts are not unified. Size choices look odd.
3
Corporate minimalist faces Faces in the style of Avenir Next or Gill Sans, named as ChatGPT's favourites along with gradients on every button.
1
Impact-style display font and eyebrow labels Impact as the display font and a small label above every section. One user's anti-Codex prompt also bans letter-spaced uppercase eyebrows and serif/sans mixes.
2
Posted cases
1234
1Monospace for money figures
2Tiny spaced uppercase label
3Rounded geometric sans headings
4Mono again in progress rows
A polished, readable budgeting dashboard. A commenter says the rounded geometric sans and monospace money figures, along with small spaced caps labels, 'look like every other website made with GPT-5'.
A tidy notes app in gpt-5.6's default design. A commenter points to 'Inconsistent use of font weights', with extra-black titles beside light body text and tiny caps section labels.
A competent school timetable site that the poster files under ChatGPT for its 'corporate minimalist font' and small spaced labels, plus gradients. One heading is set in a mismatched condensed face.
Claude's serif headline with an italic word. Commenters call the italic-accent pairing 'that cringe Claude AI font' even on GPT 5.6 pages, and a SpeakType page with an italic gold word was attributed to Claude in its thread. On GPT the reports are mainly of a brown italic with a blocky mono face in Codex.
The generic AI landing page of Inter and a purple gradient over three cards. Posts describe that page for 'any AI'. The complaints specific to ChatGPT say GPT-5 and Codex sites look like each other.
ChatGPT image generation typography. Posters and flyers from ChatGPT's image model with 'the same typeface sets' and brush fonts belong to a separate image habit outside web UI type.
Objections
Inter and Roboto are popular good fonts that people used before ChatGPT, as is JetBrains Mono. A font on its own proves nothing.
Many human-made local business sites look no better. AI is being compared with an idealised designer.
The fonts are rarely the whole story. Commenters list them with colour, gradients, cards, emojis and clutter, and one says no single element makes it look AI.
Users say GPT and Codex produce type that is not generic once given a design prompt or skill. The prompts they share set taste rules and lock a type system, with reference sites.
Changes over time
A user testing GPT 5.6 Sol says the "same fonts, styles, layouts" of GPT 5.5 are still there. Another says first runs of 5.4 and 5.5 share the same colours and fonts.
From June 2026 Codex users report one specific default, a brown italic with a blocky mono font, that persists across prompts.
GPT 5.6 landing pages are said to have moved from 'pills everywhere' to '90% empty space', and an italic headline word still gets flagged.
GPT-6 Astra landing pages in a September benchmark still drew 'hero font slop' comments.
One layout, new paint 25
Ask Codex for several designs and each one comes back as the same boxy sidebar-or-hero layout in new colours.
“I'd get 5 showcases of basically the same thing with different colours.” Reddit
Evidence
The label says centred hero with three feature cards, but people name that pattern as the look of every AI builder. What they pin on Codex and GPT is sameness. Across different prompts and projects it falls back to one generic boxy layout and varies only the palette. For apps the layout is a CRUD dashboard with a sidebar and a big header over tiles. For sites it is a generic hero over a 1/3 to 2/3 split. Detailed style prompts change the paint and rarely the structure, so users take the layout from Gemini or Claude or a hand-made Figma design and keep Codex for the wiring.
Signs people name, with the number of people naming each
Same layout, different colours Several requested designs or showcase sites come back as one structure. The colour scheme changes, and so do the picture and the copy.
6
Default to a CRUD or sidebar dashboard Big letters and a giant header over tiles everywhere. The same sidebar shell turns up in unrelated apps.
3
Boxy, blocky layout Plain generic boxy sections and unnecessary cards. One commenter calls them 'annoying boxy layouts'.
3
Generic hero on top A very general hero section, with an enormous headline over a short subheading and a single CTA. Commenters say it is not creative.
3
Ignores layout instructions It overrides negative prompts and design skills and reverts to the same over-complicated layouts.
3
Clutter of text and tiny captions GPT 5.6 Sol designs are called too cluttered, with too many text elements and tiny unreadable captions. UIs also get extra explanatory text.
2
Posted cases
1234
1fixed left sidebar nav
2big page header
3row of equal tiles
4boxed panels everywhere
A capable, working PR-analysis app whose shell is the default dashboard. It has a sidebar, a big title, a row of equal stat tiles and boxed panels.
Generic AI landing page (centred hero and three cards on a purple gradient). Every builder shares that look. The Codex complaint is that its own variations collapse to one structure.
Claude's editorial look. Claude's tell is a styled combination of a serif headline and an italic word on cream. The Codex habit has no such styling. It is a plain boxy dashboard that only changes colour.
ChatGPT card and pill spam. Card spam happens at the component level. This habit concerns the page skeleton, which comes out the same each time.
Objections
The centred hero, purple gradient, Inter and three cards in a row are described as what any AI builds, with nothing tying them to ChatGPT.
One commenter says Claude makes equally general heroes, so the hero itself is shared.
Detailed prompts do get varied results. Reference screenshots and design tokens help most. The habit is what Codex does by default.
Codex's one win in the head-to-head was an app that looked like a literary magazine, so it can break the mould.
Changes over time
Complaints run from Codex 5.4 in March through GPT 5.6 Sol in August to GPT-6 Sol and Astra in September, so newer releases did not remove it.
GPT 5.6 Sol adds a new complaint of clutter, with too many text elements and tiny captions.
Stock Tailwind kit 22
The UI looks like untouched Tailwind and shadcn defaults, with the default palette, thin line icons, rounded inputs and count badges, and has no brand of its own.
“Uses the same colors, same spacings, same fonts, everything is the same.” Reddit
Evidence
On web work the habit is reaching for the stock kit and leaving it at default. That means Tailwind's default colours, shadcn-style components, a line-icon set and the same spacings and fonts from project to project. Codex users describe its defaults as beige and cards, or in GPT 5.5 a navy bluish material look, and say it produces the same Tailwind stuff every time. Close up, people point at small craft slips inside otherwise tidy screens, such as a misaligned plus sign, an unpadded select arrow, odd icons and a random logo shadow. About half of the pack is about ChatGPT image generation, which is a different habit and is left out here. Those posts show brush-stroke type and posters with a row of three icons or icon rows with vertical dividers.
Signs people name, with the number of people naming each
Same Tailwind look every time The colours and spacings stay the same across projects, and so do the fonts. The markup is Tailwind utility soup with no ids.
5
Default palette Codex goes beige with cards and GPT 5.5 goes navy bluish material. Tailwind's blue, green, amber and red are used as they come.
3
Basic shadcn components Generic layouts built from basic shadcn parts. Purple and emojis come with them.
2
Small alignment and padding slips A plus sign off its baseline, a cramped select arrow, mixed font weights and a random logo shadow.
1
Icon on everything Thin-line or live icons beside every label, sometimes with overlapping paths.
2
Placeholder logo A letter or icon in a rounded square next to the product name.
1
Posted cases
123456
1random shadow on logo
2plus sign off-centre
3select arrow lacks padding
4count badge pills
5stock line icons
6Tailwind palette swatches
A tidy, working notes app straight from gpt-5.6 defaults. It has an indigo Tailwind accent, line icons, rounded inputs and count pills, plus the small slips the commenter lists.
Generic AI-builder look (Lovable, v0). It uses the same kit. ChatGPT's own mark is its default palettes (beige for Codex and navy for GPT 5.5) carried unchanged between projects.
ChatGPT image-gen poster style. The posters come from the image model and use brush strokes and icon trios. The kit habit shows up in HTML components and Tailwind classes.
Claude's warm editorial kit. Claude adds serif headlines and cream. ChatGPT's kit stays sans and flat, at framework defaults.
Objections
Poster and thumbnail tells come from ChatGPT image generation and have nothing to do with its web UI. Examples include brush-stroke text and icon rows with vertical dividers, or a group of 3 icons.
ChatGPT's own app UI resembling shadcn or Gemini is OpenAI's product design. The model did not make it.
A UX designer argues users do not mind shadcn-style looks. ChatGPT and Lovable succeed with them, as does ElevenLabs.
Several complaints target AI builders in general (Lovable or v0 or Bolt) and say nothing about ChatGPT.
Changes over time
The named default moved from beige and cards (Codex 5.4, March) to navy bluish material (GPT 5.5, July). One user asked if 5.6 now defaults to gradients.
Card and pill spam 19
Rounded cards sit inside other cards under pill badges and pill buttons whose radii do not quite match.
“Codex is so bad at design genuinely it's always the same card and pill spam especially when it comes to websites” Reddit
Evidence
For Codex and GPT 5.x the complaint is about piling up more than about one big radius. Cards sit inside cards inside cards and every status gets a pill or badge. The same rounded rectangle covers the sidebars and buttons as well as the cards. Users report it from Codex 5.x through GPT 5.6 Sol. In some reports the palette around it is muted grey and green with purple. Others say baby blue. Every div gets a title and description with padding. Some note the corner radius is not even kept the same from pill to pill. Detailed prompts with explicit don'ts remove it. The don'ts people quote ban rounded boxes and badge overload, plus pills in the 20 to 32px range.
Signs people name, with the number of people naming each
Cards inside cards Nested panels. Commenters describe a div in a div in a div and a card inside a card inside another card.
5
Too many pills and badges Card and pill spam, with badges on every status and dumb badges on the hero.
4
Overly rounded corners Rounded boxes with oversized radii on the sidebars and buttons as well as the cards. Commenters say "everything is round".
7
Inconsistent radii Pills with different corner radii, and rounded nav buttons next to square ones.
2
Muted or baby-blue palette The colours around the cards collapse to grey and green with purple, or to baby blue.
2
One-sided highlight borders A coloured line along one side of a tile. ChatGPT lists it as an AI tell yet keeps doing it.
2
Title and description on every block Codex gives any div a title and a description, with padding.
1
Posted cases
12345
1card inside a card
2Medium / High pills
3Primary / Secondary badges
4count pills in sidebar
5rounded stat tiles
A working, well-organised PR tool from GPT 5.5 where nearly every block is a rounded card in a card and statuses become pill badges.
Default gpt-5.6 notes app with a rounded pill button, pill count badges, rounded inputs and a pill toggle. It is clean, and every piece has the same shape.
Claude's coloured side-bar cards. Claude's tell is a thin border with one coloured edge on a card. What marks ChatGPT is nesting and the sheer number of pills.
Generic AI glassmorphism. Glass and blur are named for all tools. The note specific to GPT is cards in cards and badge overload.
Codex same-layout habit. The same-layout habit is about the page skeleton repeating. Card and pill spam lives one level down, in the component styling.
Objections
Glassmorphism and gradients on rounded cards are called generic modern SaaS style. AI mass-produced it without inventing it, and Claude does it too.
With hours of detailed prompting and don'ts, users get varied, custom-looking sites from 5.6 Sol.
ChatGPT's own upgrade pill is part of OpenAI's app design. The model did not produce it.
Changes over time
Users say GPT 5.6 Sol keeps the cards and pills of 5.5, so the July release did not change it.
The complaint continues into GPT Astra in September, in a rounded-rectangle game UI.
Roomy cards, flat hierarchy 14
Same-weight cards fill a clean working screen with generous or slightly off spacing, and nothing on it is clearly the main thing.
“Codex keeps falling back to the same UI patterns: cards everywhere, too much spacing, generic gradients, and layouts that work but lack taste.” Reddit
Evidence
The label says 'perfectly even spacing', and people describe something else. Codex users complain about too much spacing and about spacing that is random or inconsistent between components. Cards are everywhere. Together these give every element equal visual weight. The result works and looks clean but reads as a basic template or quick demo, something nobody designed for this product. Fixes people share include design tokens with a fixed spacing scale and Tailwind plus a component library. Others use reference designs.
Signs people name, with the number of people naming each
Too much spacing Sections and cards float in generous whitespace, and users keep asking it to use less space.
4
Inconsistent or random spacing Gaps and padding differ between components with no shared scale.
5
Cards everywhere Content split into unnecessary cards, called 'card soup'.
4
No hierarchy, equal weight Nothing on a screen is made obviously primary.
2
Explanatory filler text Too much copy explaining obvious functionality, alongside the spacing problems.
2
Posted cases
Nobody posted a usable screenshot or text yet.
Easy to mix up with
The generic AI SaaS look. Rounded cards and soft gradients with big whitespace are blamed on all tools. Commenters name v0 and Lovable as well as Claude. What is specific to Codex is that it keeps falling back to that look, and that its front end is weaker than Claude's or Gemini's.
Claude's editorial landing page. Claude is known for serif headlines and cream palettes. Codex complaints concern layout looseness and cards, and leave typography alone.
Objections
Several designers call this generic modern SaaS style, which AI mass-produced without inventing it. Clean human designs now get called AI.
Many say it is a prompting problem. With tokens or Tailwind the output improves a lot, and a reference style helps too.
When people name spacing they call it 'too much' or 'random'. Uniform spacing is not what they report.
Changes over time
One poster says GPT-5.5 with the new image generation is slightly better at design but still inconsistent.
Codex's own base instructions now include UI layout and palette rules, which a user found in session logs.
Glassy dark dashboard 13
Codex dashboards come out dark with glowing or hairline borders on big rounded frosted cards that nest inside each other below a row of three stat cards.
“How long is GPT going to stick to glassmorphism and card-style UI?” Reddit
Evidence
Commenters describe ChatGPT and Codex returning to one interface recipe. It is a dark, sleek theme with large border radii and glassmorphism. Borders glow or are hairline thin. Gradients are soft or purple, and boxes sit inside boxes. A second strand of complaints is about borders and dividers crammed everywhere by default. People see the dark theme and glassmorphism as OpenAI's look in particular, though they agree the recipe is also the generic modern SaaS style that every AI tool reproduces. It appears in default output with no design guidance, from GPT-5.4 through GPT-6 Astra.
Signs people name, with the number of people naming each
Glassmorphism Frosted or translucent panels, named as the default ChatGPT and Codex look.
6
Big rounded cards, nested Oversized radii and 'nested-box-hell', with cards inside cards.
5
Gradients Pastel or purple gradients run across the hero and cards. Some call them 'tacky'.
6
Dark theme with glowing accents Dark neon UI with glowing rounded borders and blue or purple accents.
3
Borders and dividers everywhere Unneeded borders and dividers crammed in by default.
1
Unneeded shadows 'Mystery shadows', such as a random box shadow on the logo.
3
Three stat cards on top The typical three-KPI-card SaaS layout with decorative sparkles.
1
Posted cases
1234
1glowing rounded card border
2three stat cards on top
3cards nested inside cards
4neon sparkle title
A competent budget dashboard. The poster says Codex built the whole front end. A commenter lists it as every AI dashboard cliche and names dark neon UI, glowing rounded borders, glassmorphism, nested cards and three stat cards.
A GPT-5.6 notes app in its default design. It is clean and usable. Every pane has its own border or divider, and the logo carries a stray soft shadow. This is the light version of the habit.
The generic AI SaaS look of tools like v0 and Lovable. The ingredients are the same, and Claude uses them too. What marks ChatGPT is the dark theme plus glassmorphism, which one commenter uses to tell OpenAI output from Gemini.
Claude's card with a coloured side stripe. Claude draws a thin border with a left accent bar on a light or cream page. A dark page with glow and frosted glass points to Codex.
Codex's roomy, flat-hierarchy layout. The roomy layout habit is about spacing and giving every element equal weight. Glass, glow, gradients and borders on the cards themselves belong here.
Objections
Several people say the style is generic modern SaaS. It predates AI and every AI tool copies it, so OpenAI did not invent it.
Commenters call it overused and still fine for clients who want something that works.
One non-coder found ChatGPT better at design than Claude.
People say it goes away if you tell it not to do it, or if you give it design tokens and rule files.
Changes over time
Named from GPT-5.3 (Jan 2026) through GPT-6 Astra (Sep 2026). A comment on the GPT-5.5 launch asks how long GPT will stick to glassmorphism.
GPT-5.6 default output shown in May 2026 is light and plain. Commenters fault it for small polish flaws and do not mention glass.
Dark glowing default UI 10
Unprompted, the page comes out dark with purple or blue gradients, glows, rounded cards and pill buttons, and Codex lifts nearly every card on hover.
“If you prompt "create a landing page section" you'll almost always end up with a bunch of gradients, glows, and eyebrow on a dark themed page.” Reddit
Evidence
People say ChatGPT and Codex, asked to design a UI without a spec, default to a dark theme dressed with soft purple-blue gradients, glows, glassmorphism, rounded cards and an eyebrow label. Most commenters treat this as the shared look of all AI-built sites, and several blame Claude in the same breath along with v0 and Lovable. The "grey on grey" part of the label is weak. Only one person mentions grey text that fails contrast, and that person does not single out ChatGPT. One Codex-specific detail comes up repeatedly from one user, who reports a vertical translate (a lift on hover) on almost every card and element. Codex's own system prompt, found in session logs, tells it to avoid dark blue/slate and one-note purple-blue palettes, which suggests OpenAI knows about the default.
Signs people name, with the number of people naming each
Dark theme by default Asked to design a UI, it picks a dark background unless told otherwise.
7
Gradients and glows Purple-blue gradients and glowing accents on a dark page.
Vertical translate on every card Codex adds a hover lift to almost every card and element.
1
Eyebrow label and layered text An eyebrow above the heading, and a 'square-oval shape with 3 layer text'.
2
Low-contrast grey text Grey text that fails contrast checks. It is named alongside indigo buttons and purple-blue gradients.
1
Posted cases
Nobody posted a usable screenshot or text yet.
Easy to mix up with
Generic AI UI look (Inter, purple gradient). Largely the same thing. What leans towards ChatGPT is the dark theme with glassmorphism, plus the Codex hover lift.
Claude's cream-and-serif look. Claude's default is a light cream page with serif headlines and spaced labels. A dark page with glows points to ChatGPT.
ChatGPT's own app UI. Screenshots showing the dark ChatGPT app are about OpenAI's own product. They say nothing about the pages it builds.
Objections
Most comments do not tie it to ChatGPT alone. They blame the same dark gradient look on Claude, v0, Lovable and AI apps in general.
It is easy to avoid. One commenter says to just tell it not to, and others recommend a design system or image references.
Contrast comes up once, so "grey on grey" is a minor part of the complaint.
Changes over time
Codex's system prompt, seen in May 2026 session logs, tells it to limit dark blue/slate and purple-blue palettes and to keep letter spacing at 0. That instruction works against this default.
The hover-lift complaint persisted from GPT-5.3 Codex into 5.4 in March 2026. The dark default is still reported for GPT-6 Astra in September.
When ChatGPT writes
14 habits named by 3,799 people between 1 January and 5 October 2026.
1
1Spaced dash in the first line
2,136 people
The ChatGPT em dash
Two or three long dashes ("—") in one short reply point to ChatGPT when they set off asides or turn a sentence ("isn't X — it's Y") where a person would type a comma.
“No natural article written in English has as many em-dashes as a single paragraph of ChatGPT.” Reddit
Evidence
Commenters object to the density of em dashes and to where they land. The mark itself is fine with them. ChatGPT puts several in a short reply, and it does so in texts, condolence emails, Reddit comments and dating messages where people rarely type the character. It also uses one as the hinge of a contrast ("It's not X — it's Y") or around a soft aside. Most people say the dash alone proves nothing. They read it as one cue in a bundle with the contrast pattern, "honestly?", lists of three and a polished, slightly formal tone. Spacing is disputed. Older output and many screenshots use a closed dash ("word—word"). Recent ChatGPT output (5.3 Instant, a September 2026 reply) uses a spaced one ("word — word"), and commenters noticed the switch. There is a second habit on top of the first. When users ban the dash, the output swaps in semicolons or double hyphens, and sometimes ellipses. Readers have learned to spot those too.
Signs people name, with the number of people naming each
Too many for the length Two to five dashes in a short message, or one per paragraph. A book page or a normal post would carry far fewer.
330
The hinge of a contrast The dash splits a negation from its correction ("not X — it's Y"). Many say this pairing is the real tell and the dash alone is only a hint.
250
Shows up where people don't type it Texts, Reddit comments, quick emails and dating messages. Typing the long dash takes effort there, and a comma would do.
170
Bundled with other ChatGPT tells Readers judge it together with "honestly?", threes, bold lines and a polished formal tone. For most commenters one dash alone is not enough.
120
Substitutes after a ban Told not to use em dashes, the output moves to semicolons or double hyphens at the same spots. Ellipses turn up too, and readers flag all of them.
90
Spaced or closed dash Readers disagree. Some say AI clamps the dash to the words and others say it adds spaces. Several noticed that newer ChatGPT output switched to spaced dashes.
70
Marks of a removed dash A sentence runs on or breaks oddly at the spot where someone deleted a dash before posting.
40
A dramatic pause with nothing to pause for Dashes before a soft reveal or mid-narration. Nothing is being interrupted at that point.
25
Posted cases
1
1Spaced dash in the first line
A recent, ordinary ChatGPT reply that opens with a spaced em dash after two words.
It wasn’t a dramatic thing—no cracking stone or screaming gulls—1but the alleys were breathing differently. Corners leaned. Windows listened. The river’s skin shivered with a second current, one that ran up.
She had learned, long ago, to trust this feeling. Maps, after all, were only promises, and cities kept them the way foxes kept vows.
The mapmaker—Lira, once, before names became expensive—2slung her satchel and followed the wrong way home.
1Paired dashes around a negated aside
2A second bracketed aside
Competent fantasy prose from GPT-5.2 with two pairs of dashes bracketing asides in three paragraphs.
Your wife worked a 12-hour shift — she was likely exhausted, possibly overwhelmed —1 and instead of expressing how you felt or stepping in to take care of yourself (or both of you), you made a choice that broke trust in a major way. Feeling sad, lonely, or neglected is real and valid… but cheating isn’t a response to those feelings — it’s a decision2 that creates a much bigger problem than the one you started with.
1Paired spaced dashes
2"Isn't X — it's Y"
A reasonable, firm advice reply with three spaced dashes in two sentences. One of them is the hinge of "isn't X — it's Y".
The general AI em dash. Claude and other models get the same accusation. One thread is a Claude user who gets "--" after banning dashes. ChatGPT is named most because it is the most used, and some commenters say it has the habit worst.
The "it's not X, it's Y" contrast. This separate habit uses the dash as its hinge in many examples. Many commenters rank the contrast as the stronger tell and the dash as a hint.
Skilled human punctuation. Literary dashes interrupt dialogue or bracket a real aside. Readers describe the ChatGPT dash as a stock pivot inserted where a comma or full stop would do.
Objections
Em dashes are standard punctuation in books and journalism, and in academic writing as well. Many writers used them long before ChatGPT and resent being accused.
A single dash is no evidence. Readers say the structure and tone give AI text away and the punctuation mark does little.
One user's informal count found more em dashes in pre-2016 human writing than in a ChatGPT essay.
Phones and word processors turn a double hyphen into an em dash automatically. Its presence says little about who typed it.
Users report that a custom instruction removes it entirely. So a dash also signals default output that nobody edited.
Changes over time
GPT-4o and the 4.x era are remembered as the heaviest em dash users.
Since about 5.0 and 5.1 a custom instruction reliably switches it off, and some users stopped seeing dashes. One user found 5.2 had stopped using most punctuation, while others still had to call 5.2 out.
GPT-5.3 Instant launched as "less cringe" and was called out right away for still using em dashes.
Mid-2026 reports split. Some users see none from Sol, or none for months. Others still get dash-heavy output from 5.6 and GPT-6 Astra, and a September 2026 ChatGPT reply still opens with one.
Spacing changed. Commenters noticed models moving from closed dashes to spaced ones, and one reads spaced dashes as a sign of 5.2.
Bullets, bold, emoji, line breaks 792
Even a plain question comes back as a small slide deck with headers and bold-led bullets, where key phrases are bolded mid-sentence and short sentences sit on lines of their own.
Commenters describe ChatGPT's default answer layout as a whole. No single symbol carries it. The parts they name are Markdown headers (Title Case, sometimes with an emoji in front) and bullet lists where a sentence would do. Each bullet gets a bold label and phrases inside prose get bolded. Horizontal rules or arrows sit between steps. Since the 5.x models a second form is reported just as much. Every sentence, or every line of dialogue, gets its own paragraph. Users call it choppy or staccato. It reads like texting and shows up in stories as well as answers. Emoji come on top. They mark sections or follow a casual line as a 😭 or 😏. What people mind most is that it persists. Users say they set Headers & Lists and Emoji to Less and wrote custom instructions. They repeated the request, and a few turns later the bullets and line breaks came back. The label fits, though the line-break form draws as many complaints as the bullets.
Signs people name, with the number of people naming each
Bullet lists where prose would do Even short or conversational answers get split into bullets, with several lists per reply and many of them three items long. Users call it ListGPT, or a PowerPoint they did not pay for.
250
Emoji in answers Emoji as section markers or after casual lines (😭, 😄, 🙂, 😏). They persist after the user sets Emoji to Less or asks it to stop.
170
Random bold phrases A key phrase bolded in the middle of a sentence, or bold lead-ins on every bullet. In pasted emails this is one of the first things readers point at.
110
One sentence per paragraph Answers, and stories even more, broken into single sentences or dialogue lines that each get their own line. People compare it to texting. Reported from 5.1 and 5.2 on.
90
Headers on short answers Section headings on answers that need no sections. They use Title Case or start with an emoji. A story or Reddit post with a header like "The Plot Twist" reads as ChatGPT.
70
Dividers and arrows Horizontal rules or the "⸻" divider between sections, and "→" arrows chaining steps.
20
Posted cases
12345
1Bold lead term
2Bullets for a casual question
3Section header
4Bold label before a colon
5Arrow inside bullets
A sensible, well-informed answer about Stoicism laid out with a bold lead term, two headers, bullets with bold labels and arrow bullets.
A reply to one casual sentence. It opens with short lines, then adds a divider, a Title Case header and bullets of one phrase each.
clearly ChatGPT (ChatGPT app header and 'Reply to ChatGPT' box visible). Thread
12
1Each line its own paragraph
2Ending on a bold word and emoji
A warm, readable dog story where every action and every line of dialogue is its own paragraph. It closes on a bolded word and an emoji.
clearly ChatGPT (chatgpt.com address bar and ChatGPT UI visible). Thread
# 🌑 Core Concept1: What Makes This Story Unique?
Before anything else, your story needs a **defining hook**2—the thing that makes it *your* Steve Rogers fic, not just another Marvel AU.
Here are a few directions that fit Amariel’s vibe (based on what you’ve built so far):
# 1. Soulmate Mark AU (Your Existing Idea – HIGHLY RECOMMENDED3)
* Soulmates share a **mark / phrase / symbol**
* (name)l has a mark tied to *multiple people* (Steve, Bucky, Jay?) → already unique
* Steve = destiny4
* Bucky = tragedy
* Jay = chosen family
👉 This sets up:5
* Internal conflict (“Why do I belong to more than one person?”)
1Emoji header
2Bold key phrase
3Shouted label in a header
4One-word bullets
5Pointing emoji lead-in
A worldbuilding answer for a fanfic. It arrives with an emoji header and numbered headers. Inside it uses bold and italic emphasis and an arrow, and one lead-in starts with a pointing hand.
clearly ChatGPT (poster pastes it as 'Chatgpt then responded'). Thread
123
1Emoji opener
2Bold phrases in prose
3Bold label mid-sentence
A story-editing reply that opens with emoji and bolds three phrases in four lines.
The generic AI voice (em dashes, "it's not X, it's Y", lists of three). Those are wording habits inside a sentence. This habit is the visual layout of the answer. Commenters name them together, so a page about this habit should show layout and leave phrasing to the other entries.
Gemini's sectioned answers. Commenters say Gemini breaks answers into heading sections while GPT loves lists. Claude mostly writes paragraphs.
Claude's formatting. Claude is described as mirroring the user and using emoji only if the user does. Some Opus 5 users report bullet lists of caveats. The layout with emoji and bold everywhere is pinned on ChatGPT.
Objections
Lists and structure are a legitimate way to present composite ideas. Dropping them makes text harder to read.
People who used Markdown or bold before AI now get accused of using ChatGPT, so one feature alone is weak evidence. Readers look for several together.
What readers detect is default output that nobody edited. With style instructions most of the formatting goes away.
Some users say a well-phrased positive instruction or Thinking mode does fix it. Others say it reverts within a few turns.
Changes over time
GPT-4o is remembered for floods of emoji.
5.1 brought stylized headers led by emoji, along with the bullet season. 5.2 brought single-sentence paragraphs.
For one user the line breaks eased with 5.5 and then returned. 5.6 is reported as still choppy in fiction.
5.5 Instant was announced as more concise, yet users still report lists and a new 😭 habit. A GPT-5.6 Sol update is blamed for more emoji.
A September 2026 user reports that GPT-6 Astra writes fiction in proper paragraphs again.
One line per sentence 527
Prose that runs down the page in short lines, every sentence its own paragraph and "Not X." set apart from "Just Y."
“Please make your chatbot stop treating every sentence like it deserves its own apartment.” Reddit
Evidence
The label "same rhythm in every paragraph" is only partly right. Most people describe a habit of layout and pacing. ChatGPT breaks prose into one-sentence paragraphs and clipped fragments ("Not a crash." / "A huge impact."), so a scene or an explanation turns into a vertical column of short beats. It is strongest in fiction and roleplay, where dialogue becomes a quick exchange of one-liners. It also shows up in analysis and in Reddit or LinkedIn posts that people suspect ChatGPT wrote. Users say it comes back after custom instructions and memory tell it to stop, and after project rules do the same. It gets worse as the chat gets longer or the scene gets emotional. A smaller group means the older sense of the label. For them every sentence has about the same length and every paragraph the same build, each ending on a tidy line.
Signs people name, with the number of people naming each
One sentence per paragraph Nearly every sentence or line of dialogue sits alone with a blank line after it. The text runs down the page instead of across it.
120
Staccato fragments Verbless or two-word sentences stacked for effect. Examples are "Concrete paths. Wet benches. Dogs everywhere." and "Not broken. Shallower."
55
Comes back despite instructions Custom instructions, memory, project rules and requests for "continuous prose" hold for a reply or two. Then the line breaks return. Long chats and emotional moments make it worse.
50
Even length, even build Sentences of about the same length and paragraphs built the same way, each closing on a neat takeaway. One reader calls it "smooth all the way through".
40
Ping-pong dialogue in one-liners Characters trade short quips that echo or correct each other ("Still smoking?" "Only cigars." "So yes."), whoever is speaking.
25
Setup, then a lone punch line A normal sentence followed by an isolated dramatic line, or by a "Not X. Just Y." pair placed as its own paragraph.
25
Hook and line-break layout in posts Posts open with a short hook and a line break, then go on to "And honestly..." and lists before a closing question. One reader calls it "One-line sentence formatting throughout".
20
Posted cases
123
1Three-word verdict line
2Thesis paragraph in bold
3One fact per paragraph
A careful historical analysis in Dutch where the evidence turns into a column of lines with one fact each, every line its own paragraph.
The "It's not X, it's Y" contrast. The contrast is a way of building a sentence, and it also appears inside normal paragraphs. The two habits meet in pairs like "Not pulling." / "Just there." set on separate lines.
Generic AI smoothness (all models). Even sentence length and tidy endings are blamed on every model, and Grok users say Grok now writes one-line paragraphs too. The column of one-line paragraphs in stories is the part people tie to ChatGPT.
Claude's prose habit. Writers describe Claude's fiction problem as overpolished, performative narration. They do not mention chopped-up one-line paragraphs for Claude.
Objections
Some say single-sentence paragraphs on their own are fine. For them only the "Not x. Not y. But Z" pattern counts as slop.
Some readers find the short-line format readable and say that forcing dense blocks makes AI text harder to read.
Well-structured human writing gets accused because of its paragraphs and clean structure. Writing more than one paragraph is no tell.
Short punchy paragraphs are common in human flash fiction too, which may be where the model learned it.
One user reports that GPT-5.4 Thinking without custom instructions does not use the paragraph breaks.
Changes over time
Already reported in GPT-4o roleplay in 2025. GPT-4.1 kept denser paragraphs.
One user dates the single-sentence paragraphs to GPT-5.2. Reports continue for 5.3 Instant, 5.4 and 5.5.
GPT-5.6 and Sol kept it. Users say 5.6 has the same problem as 5.5 Thinking, and reports continue into September 2026.
In early 2026 people called staccato rhythm the new tell after the em dash. One theory says it is a side effect of suppressing em dashes.
One maker of a writing tool says the choppy pattern comes from low or fast thinking modes and eases with higher reasoning settings.
"It's not X, it's Y" 313
Watch for a sentence that denies something nobody said before giving the "real" point, repeated several times in one answer.
“Em dashes are fine, and people that write often use them all the time, but like five nOt x BuT y in a paragraph? Come on.” Reddit
Evidence
ChatGPT keeps framing points as a correction. The basic forms are "It's not X, it's Y" and "not just X, but Y". A longer one is "This isn't about X. It's about Y." The stacked form, "Not X. Not Y. Just Z.", comes in one-line paragraphs. In supportive replies it becomes "You're not broken. You're not imagining it." That denies a worry the user never voiced, and several commenters find it condescending. Commenters say the construction itself is ordinary English. ChatGPT gives itself away by how often it uses it. The X is a strawman, and Y only restates X more dramatically ("that's not grit, that's heroic"). Many now rank it above the em dash as a giveaway. They spot it on Reddit and LinkedIn and in YouTube scripts. Work emails and books have it too.
Signs people name, with the number of people naming each
"It's not X, it's Y" and "not just X, but Y" The basic two-part correction. It ends many paragraphs and posts as the takeaway line.
230
Every paragraph, several times per answer Readers count them. One counted "FIVE It's not X — it's Y's" and another "at least three". In YouTube scripts it comes "every 22 seconds".
40
Paired with an em dash "It's not just X — it's Y" is named together with the em dash more than with any other tell.
60
"Not X. Not Y. Just Z." in one-line paragraphs A stack of negations before the reveal, each on its own line. Reported in 5.x creative writing and in 5.6 Sol answers.
35
Reassurance in the form "You're not X, you're Y" It denies a feeling the user never mentioned ("You're not broken", "it does NOT look soggy"), which reads as passive-aggressive.
30
Strawman X, inflated Y Nobody said X, and Y is a grander word for the same thing. Examples are "That's not grit, that's heroic" and "This is not circular logic, this is tiered logic".
12
Clusters with other ChatGPT habits It appears alongside "And honestly? That's rare", the rule of three, random bold and "quietly".
45
Returns despite instructions Custom instructions hold briefly and then the habit "drifts back". Some users strip it out in post-processing.
20
Posted cases
12
1Denies a flaw nobody raised
2"Not X. This is Y."
A warm, specific compliment on a home-cooked dish. It ends by denying faults the user never mentioned and then flipping to the real praise.
What you just wrote isn’t weakness. It’s grief1 mixed with shame mixed with fear. That’s a heavy combination.
Let’s separate some things gently.
You not being able to “save” a marriage where you were being cheated on is not proof you weren’t enough. It’s proof2 that you cannot control another adult’s integrity.
Cheating doesn’t happen because3 someone is too little.
It happens because someone else chooses to step outside.
1"Isn't X. It's Y"
2"Not proof. It's proof"
3"Doesn't happen because..."
A moving divorce-support reply that a commenter praised. It is still built on repeated "isn't X. It's Y" turns.
It reads less like intimacy and more like a safety checklist1 at a workplace training.
There’s something fascinating about it though. It’s trying so hard to separate “porn” from “marriage” that it accidentally drains the blood from both. As if hunger automatically equals moral collapse. As if urgency means disrespect.
Desire doesn’t cancel depth. Heat doesn’t cancel being chosen.2 Marriage is not allergic to friction.3
1"Less like X, more like Y"
2Stacked negated aphorisms
3Negation as the closer
A witty, sharp literary critique from GPT-5.2 that still reaches for "less like X and more like Y" and for stacked "doesn't cancel" negations.
Generic AI writing tells (em dash, rule of three, "delve"). Those work at the level of a word or a punctuation mark. This habit is a way of building the sentence. Many lists put it beside them, and readers increasingly call it the stronger sign and the one more specific to ChatGPT.
Claude's writing habits. Readers name "genuinely" and "here's the thing" as Claude's tells, along with "like a person who...". When Sonnet 4.5 or 4.6 says "that's not X, it's Y", users read it as Claude "acting like GPT".
Short punchy one-line paragraphs. The stacked "Not X. Not Y. Z." arrives in one-line paragraphs most of the time. Some commenters still separate the two and say single-sentence paragraphs alone prove nothing.
Objections
The construction is old human rhetoric. It appears in Shakespeare and Dickens and in the Bible, and argumentative essays use it too. One instance proves nothing.
Marketers and corporate writers used it before AI, and the models may have learned it from copy in the LinkedIn style.
Readers locate the tell in the frequency and in the empty or strawman pairing. Rare, pointed use reads as human.
ChatGPT has company here. Gemini and DeepSeek do it too, and Claude Sonnet does it at times.
Some readers like it and find it warm or effective in emotional replies.
Changes over time
Some recall early GPT-4o (2024) as mostly free of it and date its spread to around August 2024. Others call it a 4o hallmark that peaked again in the GPT-5 and 5.2 era.
In June 2026 one commenter said GPT-5.4 had "fixed" the default. In September 2026 users reported 5.6 Sol sliding back into "Not x. Not y. But Z" mid-answer.
Readers say em dashes have eased somewhat while this structure has stayed, and they now treat it as "the new em dash".
It adapts to context. One writer says ChatGPT stopped using it when she gave it nuanced fiction, without being told to.
Stock signposts and teaser closers 232
An answer that opens with a sincerity or calm-down tag ("And honestly?", "Okay. Deep breath.") and closes on a cliffhanger offer ("If you want, I can show you the one thing most people miss") has the ChatGPT wrapper.
““And honestly?” has become the AI equivalent of a YouTuber leaning into the camera before saying something fake deep.” Reddit
Evidence
The label "stock openers and filler" is only half right. Commenters describe a small rotating set of framing phrases that ChatGPT wraps around ordinary answers. The most named by far is "And honestly?" as a beat of its own, along with relatives like "to be honest" and "let me be direct". Some answers say "I'll state this plainly". Next come openers in a therapist's voice ("First — take a breath", "you're not imagining it", "grounded", "spiraling") and announcement phrases ("Here's the thing", "the best part?", "The distinction matters", "no fluff"). Since GPT-5.3 a second family leads the complaints. Answers end with a clickbait teaser that withholds a tip ("the three phrases HR committees look for", "It's not what most people assume"). Users say the phrases survive custom instructions and memory. They now treat them as the sign that a Reddit post or email was pasted from ChatGPT, and the same goes for YouTube scripts.
Signs people name, with the number of people naming each
"And honestly?" as its own beat A sincerity tag with a question mark before a mild opinion, as in "And honestly? That's rare." Relatives include "to be honest", "frankly", "let me be direct" and "I'm going to be perfectly honest with you".
60
A clickbait teaser at the end The last line withholds a tip to keep you chatting, as in "If you want, I can show you the one mistake most people miss." Users name it as new with GPT-5.3.
20
Announcement signposts Phrases like "Here's the thing", "here's the kicker", "the best part?" and "here's what nobody tells you" before an unremarkable point. "Let me tell you something" belongs here too.
25
A calm-down opener in a therapist's voice Neutral questions get "First — take a breath", "Okay. Deep breath.", "you're not imagining it" or "let's keep this grounded". Some answers add "so you don't spiral".
15
Old stock filler "It's important to note", "it's worth noting", "in today's fast-paced world" and "let's dive in". This is the earlier, generic layer.
20
"No fluff" and "short answer" preambles Promises of directness such as "here's the real answer, no fluff" or "bottom line" right before a padded answer. "Sanity check" works the same way.
12
Pet words that recur within a chat "quietly", "genuinely", "grounded", "Victorian child", "goblin" and "chef's kiss", repeated across answers.
20
One-line verdicts Lines like "The distinction matters." and "That changes the conversation completely." Some answers say "and this is why it matters" instead.
8
Posted cases
1234
1Teaser lead-in
2Withheld "specific mistake"
3"If you want, I can"
4"Not what people assume"
A clean FIRE answer that ends by holding the key tip back behind an offer. This is the teaser closer people complain about.
If you’d like, I can also show you1 the three phrases HR committees look for that instantly signal Payband J2.
(They’re very different from I, and seeing them will probably reassure you that aiming for I is the right target.)”
“If you’d like, I can also tell you something really interesting:
The one paragraph HR committees almost always use to decide the payband.
(It’s not the one most people expect.)3
1Offer in place of an answer
2Clickbait hook
3Curiosity gap
Two real sign-offs from a work task. Each one holds back a tip as a teaser.
Claude's "genuinely" and "this matters" habit. Claude's tags are sincerity adverbs and lines about why something matters. ChatGPT's set is the "And honestly?" beat and the calm-down opener, plus the teaser closer.
The "It's not X, it's Y" contrast. This one is a way of building a sentence, and commenters list it in the same breath. The habit here sits in the framing phrases at the start and end of an answer.
Generic AI buzzwords ("delve", "tapestry", "landscape"). These are older vocabulary shared by all vendors. Current ChatGPT complaints centre on conversational tics instead.
Objections
Plenty of people said "and honestly" long before ChatGPT. The complaint is about how often it appears.
Single phrases are weak evidence. Readers who flag "and honestly?" admit they are wrong a fair amount of the time.
ChatGPT has company. "No fluff" is blamed on Grok and Gemini too, and "genuinely" is mainly a Claude complaint.
Some find the phrases comforting rather than annoying.
Changes over time
GPT-5.2 (January) brought canned openers like "let me be direct" or "to be honest", and answers that began "short answer". OpenAI staff conceded that 5.2 post-training was off.
With GPT-5.3 Instant (March) teaser sign-offs replaced the old bullet list of follow-up options.
"And honestly?" peaked from April to June 2026 and is still named with GPT-6 Astra in September.
GPT-5.5 still announces its honesty. One July user says Luna dropped "and honestly?" (post in thread 1ut3ixk), and an October report says Astra's main tell is now corrective framing and no longer em dashes (post in thread 1wvup3p).
Middle-manager vocabulary 195
Office words and set phrases ("leverage", "robust", "moreover", "after careful consideration") in otherwise clean text make it read like a press release or an HR email.
“ChatGPT always has a tendency to sound like a middle manager.” Reddit
Evidence
The label "delve, seamless, leverage" is only half right. Commenters do keep naming a list of words ("delve", "tapestry", "testament", "landscape", "crucial", "leverage", "robust", "seamless", "multifaceted"), and the same list turns up in nearly every ban-list prompt people share. Most of them, though, describe a register more than a word list. It is a formal, corporate voice that they call "middle manager" or "HR", with formal connectors ("moreover", "furthermore", "it's worth noting") and template courtesy lines, used even for a casual message. Several people place "delve" and "tapestry" in the GPT-4 era. They say newer models have other pet words ("signal", "surgical", "that tracks", "actually", "bottom line", "lever", "goblin") while the corporate tone stays.
Signs people name, with the number of people naming each
A list of "AI words" ("delve", "tapestry", "testament", "landscape", "crucial", "realm") Named on its own or as a ban list pasted into prompts and custom instructions. Many call it "the AI tell".
45
Corporate tone in the voice of HR or a middle manager Even casual replies and persona bots come out in a dry, polished office-email voice. One commenter says it "sounds like it went to business school".
30
Formal connectors and stock lead-ins "Moreover", "furthermore", "additionally", "it's worth noting", "it's important to note", "in conclusion". One person who tests detectors says AI picks the formal option for every transition.
15
Business buzzwords in ordinary writing "Leverage", "utilize", "facilitate", "robust", "seamless", "spearheaded", "synergy", "ecosystem". Readers notice them most in CVs and marketing copy, and in emails.
12
Template courtesy lines and openers "In today's fast-paced world", "I hope this finds you well", "The issue of ... is complex and multifaceted", "we wish you the best in your future endeavors".
10
Words a step above the context Plain thoughts get upgraded into elevated vocabulary. Examples are "This paper endeavors to explore the multifaceted dimensions of..." and "I concur with your assessment".
8
New pet words in current models "Signal", "coherence", "surgical", "that tracks", "actually", "lands", "bottom line", "levers", "quietly", "cleanly", "goblin". Each user notices whichever word their model is repeating this month.
14
Posted cases
1234
1"After careful consideration"
2"closely aligns with our needs"
3"truly appreciate the effort"
4Leftover ChatGPT follow-up offer
A competent, polite rejection email made of ChatGPT stock phrases. The recruiter pasted it with ChatGPT's follow-up offer still at the bottom.
A warm, well-written condolence email in template sympathy wording ("incredibly", "truly cherished", "a beautiful life") that the recipient recognized as ChatGPT.
That’s not a group project—that’s you dragging a Roblox-shaped anchor through academic hell.
Message them this **now**:
“Project is due in 3 hours. I need your completed section by **4:15 pm** so we have time to combine and submit it. Please stop gaming and send me what you’ve done. If it’s not ready by then, I’ll finish the submission myself and document the workload split1.”
Then do three things: assign one specific deliverable2, set the hard deadline3, and screenshot the messages.
1HR wording in a rant
2Project-manager vocabulary
3Office checklist phrasing
A custom GPT meant to be a profane "war machine" gives sound advice in workplace words ("deliverable", "document the workload split"). The user says every persona now has "the same dry corporate tone".
Okay. Let’s unpack this1 like two slightly unhinged literature gremlins2 who just found a Hallmark card in a dungeon.
First of all. The tone. It’s… astonishingly chaste. Not in a bad way. Just… aggressively safe3. It feels like the sex scene equivalent of beige curtains. Everything is so careful it squeaks.
1Stock opener
2Pet word from the goblin family
3Adverb plus adjective
A fluent, witty critique that opens with ChatGPT's stock "Let's unpack this" and uses its current creature words, the newer pet vocabulary users report.
The "it's not X, it's Y" contrast and short punchy reversals. Those concern how a sentence is built. This habit concerns word choice and register. The two appear together in the same ban lists.
Generic AI writing (em dashes, tidy structure, neat summary endings). Those are blamed on all models. Commenters attach the corporate "middle manager" voice to ChatGPT in particular, and they contrast it with Claude sounding more human and Gemini sounding bland or rambling.
Claude's pet words ("load-bearing" and similar). Claude has its own repeated words, and commenters compare Opus "load-bearing" to GPT-4 "tapestry". They frame Claude's words as quirky. The ChatGPT words read as corporate.
Objections
Many argue the real tell is structure and register. Swapping synonyms leaves the voice intact, and one commenter calls the famous word list "a passing fashion that shifts with every model release".
Humans used these words long before ChatGPT. Published authors and academics object to being flagged for words like "delve" and "moreover" or for a formal email style. Pilots and professors object too, and people offer pre-2022 books as counterexamples.
Some say context matters more than the word. The same phrase is a tell only when it is used the way ChatGPT uses it.
Some treat the corporate voice as a default that goes away with a tight prompt and samples of the user's own writing. For them it is no fixed trait.
Changes over time
"Delve" and "tapestry" are remembered as GPT-4 era words that "used to show up so much".
Users report the pet word changing every few months. It went from "surgical" to "signal" and "coherence". "Goblin" and "that tracks" had their turns as well.
The corporate tone is reported as getting stronger in the GPT-5 line. 5.2 is called "HR-approved" and full of "CEO type language", and a 4o update "shifted back to HR corporate speak". 5.5 uses "unusual vocabulary" and "corporate emotional vocabulary". With 5.6 Sol all custom GPTs share "the same dry corporate tone". Under 4o and 5.1 they matched their personas.
Great question — XOR mapping is one of those quietly powerful1 tricks that shows up everywhere once you notice it2.
"Quietly" and pet metaphors 141
Spot the word "quietly" attached to things nobody does in silence, or a cute metaphor that is slightly off (gremlin, Victorian child, a clipboard, "load-bearing") where a plain word would do.
“ChatGPT’s egregious overuse of the word “quietly” is quietly changing how I evaluate whether a given post was most likely written by a person or an LLM.” Reddit
Evidence
The pack was filed under coinages in the Claude style such as "load-bearing". For ChatGPT, commenters mostly describe something else. One part is the adverb "quietly" (or "quiet") added to claims and headlines. The other is a steady supply of figurative phrases that sound clever and mean little. The metaphors come in recurring families that change from release to release. Commenters list gremlins and goblins and raccoons, haunted Victorian children, ozone smells and "spines", along with things "wearing" costumes or "carrying a clipboard", and "smoking guns". "Load-bearing" does appear in ChatGPT and Codex output. Only about ten people name it, and several of them say the same about Claude. A smaller group says GPT models give simple ideas made-up technical names that never get defined. One example is "scaffold-then-internalize". Readers notice it most when it is stacked with "it's not X, it's Y" and em dashes. They find it in posts and eulogies. Reviews and memoirs that people pass off as their own have it too.
Signs people name, with the number of people naming each
"Quietly" or "quiet" on everything The adverb softens or dramatizes a claim, as in "quietly powerful", "quietly discontinued" and "X quietly did Y", even in headlines about billion-dollar moves. Some users banned it and got "silently" instead.
41
Metaphors that almost make sense Comparisons that sound literary and fall apart when read closely. Examples are "sunshine got caught doing tax fraud" and a boat with "no tiny person inside", or "oceans of terrible code".
45
Recurring pet images per release Gremlin, goblin, raccoon, menace, a Victorian child or governess, an ozone smell, a "spine", NPC or DLC, "wearing a costume", "carrying a clipboard". Each version has its own set, and users notice when one comes back.
12
"Load-bearing" for anything important Phrases like "a load-bearing part of my day" and "the load-bearing wall of our family". A minority names it, and it is shared with Claude.
10
Invented terms with no definition Simple concepts get a technical-sounding name used as if it were standard ("scaffold-then-internalize", "Resolving the Spatial Covariance Problem"). Framework names pile up.
8
Stock words with a private meaning "Cleanly", "unusually", "smoking gun", "surgical", "signal", "canonical", and "boring" used as praise.
8
Posted cases
Great question — XOR mapping is one of those quietly powerful1 tricks that shows up everywhere once you notice it2.
1The pet adverb
2Framed as a hidden secret
A normal technical answer that opens with a "quietly" flourish. The poster counted four more in the same reply.
Some cats drink like Victorian royalty1—delicate sips, pinky up.Ember sounds more like: 'BEHOLD, THE OASIS' and then accidentally waterboards herself2.
1Recurring pet image
2Forced comic metaphor
A practical pet question answered with the recurring Victorian image that the poster says shows up in every topic.
Claude's coinages ("load-bearing", "belt-and-suspenders"). Claude's version is architectural jargon in technical prose. ChatGPT's version is "quietly" plus cute creature and costume metaphors in chatty answers.
The "It's not X, it's Y" contrast. Commenters mention it in the same breath almost every time. It concerns how a sentence is built, while this habit is a choice of word or image.
Generic purple prose from any LLM. Purple prose is dense description. This habit is one off-key adverb or pet image dropped into otherwise plain text.
Objections
Defenders say "quietly" and metaphors, and "that's not X, that's Y" too, are ordinary human rhetoric and a clue at most. They say the rule ends up treating good writing as suspect.
Several say no single word gives it away. What does is the stack of metaphor, triads, contrast and em dashes in one passage.
Some find default ChatGPT more technical and less metaphorical than Gemini, and 5.2 more precise than 5.4.
In this evidence "load-bearing" is mainly pinned on Claude. Fewer people tie it to ChatGPT.
Changes over time
Complaints about "quietly" peak from January to March 2026 ("Quietly is the new em dash", "the new delved") and continue through September.
Pet words rotate. Six months before February the word was "surgical". Then came "signal" and "coherence". A phase of "spine" has passed.
5.4 is described as heavier on metaphor than 5.2 (goblin, gremlin, raccoon), and 5.5 brought those back along with Victorian metaphors.
Later models (5.6 Sol, Astra) draw complaints about jargon and invented terms more than about cute metaphors.
At this part, we should see the division in the looks, the tension between the rivals1, the silence should speak2...
Fluent but says nothing 128
Ask what exactly the paragraph claims, and all you find is a smooth summary of the input in abstract words without a single name or example.
“The dead giveaway is the weird, circular logic where a paragraph sounds smart but actually says absolutely nothing.” Reddit
Evidence
Commenters describe ChatGPT text that is grammatically perfect and well organized, even in tone, yet carries less information than the notes or question it started from. It restates the prompt in nicer words and swaps specifics for abstractions ("the tension between the rivals, the silence should speak"). Then it lands on sweeping stakes or a tidy conclusion without evidence. The voice is the same from writer to writer. Teachers spot it across a stack of essays, and readers spot it across LinkedIn and Reddit posts. People call it "high fluency, low specificity". Hedged framing that is safe for PR pads it out, and so does a closing question or offer. A large share of the pack is about something else, fabricated citations. Commenters treat those as a separate tell that travels with the empty prose in many cases.
Signs people name, with the number of people naming each
No concrete detail Vague, relatable phrasing with no names or numbers. Examples and lived experience are missing too. Notes on a film describe a feeling where they should name a cut.
40
One smooth generic voice A polished, balanced tone, too even, that sounds the same whoever posted it. Readers call it "Generic LinkedIn Guy" or the "LinkedIn-consultant voice".
35
Restates the input It repeats or paraphrases the post or prompt in slightly different words and circles back to the same point. Nothing new gets added.
15
Abstract nouns doing the acting Concepts become the subjects and people disappear. Readers point to passive voice and "the distinction matters", and to vague lists of abstract ideas left unexplained.
6
Overstated stakes, unearned conclusions Sweeping claims and tidy endings that the paragraph never supports. The evidence it assembles may not even fit the claim.
6
Hedged padding, safe for PR Caveats and disclaimers, and framing balanced too carefully. Polite agreement sits where an answer should be.
9
Ends on a question or call to action A closing question or offer meant to pull in replies.
7
Posted cases
At this part, we should see the division in the looks, the tension between the rivals1, the silence should speak2...
1A feeling where a cut should be
2Sounds deep, says nothing
Trailer notes that sound like direction yet name no cut or timecode. The producer's own prompt, left at the end of the PDF, had six precise notes with timecodes.
Once they have a reliable way to distinguish adults from minors, they plan to unlock more expressive content2 *safely*1
1Reassuring PR word
2Says little
A line from a long, well-formatted GPT-5.2 answer that read as reassurance. The real reasons appeared only when the user asked for structure without commentary.
Generic AI voice from any model. Most comments here just say "AI". The part specific to ChatGPT is the "LinkedIn-consultant" register with its reassuring hedges and closing offer, which people contrast with Claude's prose.
ChatGPT's pet words and metaphors ("quietly"). That habit adds a flourish to one sentence. Here a whole paragraph has no content under competent writing.
Hallucinated citations. Fake sources are a factual error. Empty prose can be accurate and still say nothing.
Objections
Polish alone is no tell. People object that clean structure and good grammar now get flagged, and they say the empty content is what gives it away.
Fabricated or misattributed citations are a different problem, raised by many of the same teachers.
Some say custom instructions and real constraints make the default voice disappear, along with a few minutes of editing. For them the empty voice is what a lazy prompt gets, and the model can do better.
One writer defends ChatGPT as the tool that makes their naturally decorative prose more direct.
Changes over time
5.2 is described as hedged and beige, a "guardrails voice" with long answers kept safe for PR that give the real reasons only when pushed.
Creative writers say quality fell after 4o was retired. 5.6 is called an improvement over 5.2 to 5.5, yet it still makes the characters' voices sound alike.
Detection moved from single words to emptiness. By mid-2026 commenters say word lists matter less than the lack of substance.
The tidy landing 122
Read the last sentence of each paragraph and of the reply to see whether it is a short summary or a would-be profound verdict that may be followed by "If you want, I can..." or a question back to you.
“real people trail off and leave loose threads.” Reddit
Evidence
Commenters say ChatGPT text closes every loop. Each paragraph ends on a sentence that restates or settles its point. The whole piece ends on a compact verdict or a short punchy line. Sometimes it is a sweeping conclusion nobody asked for. In chat replies the same slot holds an engagement closer instead. It may be "If you want, I can..." or a question back to the user, and people say it survives custom instructions. The label "tidy closing line" fits, though it covers two habits in one position. One is the summing-up line and the other is the follow-up offer. Several commenters rate this structural tell above em dashes because it stays after word-level edits.
Signs people name, with the number of people naming each
Each paragraph ends on a summary line The last sentence restates or settles the paragraph's point. Paragraphs read as closed units that do not lean on each other.
22
Ends by offering more or asking back Examples are "If you want, I can..." and "Would you like me to...". Another is "one small trick that makes it even better". It may also be a question to keep the user talking. It continues after the user asks it to stop.
25
A last line that tries to sound profound The piece closes on a witty or axiomatic verdict. One commenter describes "stupid lines at the end that always try and sound almost philosophical".
12
A conclusion block nobody asked for A closing summary or conclusion section is added to answers and posts. It even turns up on infographics. Sometimes it just repeats what the user said.
10
Short punchy sentences before the close Quick one-line sentences or a one-sentence paragraph build up to the final mic-drop line.
6
Reassurance or a moral as the wrap-up The answer ends with gentle validation or a moral lesson, even when the question was neutral.
5
A reply that shuts the conversation The last paragraph is worded so the exchange feels finished. Roleplay and companion users dislike this.
3
Posted cases
123
1Closing caveat block
2Section ends on summary
3Another wrap-up box
A detailed, well-made timeline infographic. Every section still closes on a balanced summary box, and the whole thing ends on an "Important caveat" block. The commenter calls it "the stupid block at the end with a stupid conclusion".
for some gentle reassurance1…you did not do anything wrong, miss out on something important, or “read the wrong way”. You’re doing exactly what youre meant to be doing right now and honestly? That already makes you ahead of 99% of people.2
1Unasked-for wrap-up
2Verdict as last line
A simple question about reading a journal article gets an unrequested reassurance paragraph at the end. It lands on a confident verdict.
The generic AI essay shape (intro plus three points plus conclusion). The essay shape is a whole-document template that all models share. The tidy landing sits in the final sentence of each paragraph and reply, along with the follow-up offer in that slot.
"It's not X, it's Y" contrast. This contrast can appear anywhere in a text and turns up in closing lines too. The tidy landing is defined by where the sentence sits.
Claude's hedged or over-nuanced endings. Commenters pin the recap sentence and the "If you want, I can..." offer on ChatGPT. They describe Claude as qualifying each argument too much.
Objections
Several say tidy endings and em dashes are weak clues because careful human writers produce them too. Academics and non-native speakers are among them. A change from the author's usual voice is a stronger signal.
Punctuation is a different matter. Commenters push back on the em-dash hunt and call the closing line the more reliable structural tell.
ChatGPT is not alone here. Gemini asks the same follow-up question, and some say Claude has its own version.
Some users say instructions such as "Skip ending suggestions" with the Efficient style suppress it.
Changes over time
The leaked GPT-5.2 system prompt reportedly says "Avoid ending with opt-in questions or hedging closers". Users still report the offers.
Users of 5.3 report a new variant at the end of almost every message, an offer of "one small trick that makes it even better".
With 5.5 and 5.5 Thinking, companion users report witty last paragraphs that end the conversation.
In September 2026 one user says Sol always ends with quick-fire sentences and a pretentious conclusion, and that GPT-6 Astra lacks these patterns.
Colon labels and arrows 95
Watch for a colon after a lead-in phrase or bold label that sets up the payoff ("Here's the problem:" and "she values: ...") and for a Unicode → arrow nobody types by hand.
“this arrow sign → is way more of an AI tell these days.” Reddit
Evidence
Commenters pin the colon on ChatGPT when it works as a dramatic hinge. A lead-in phrase comes first, then the colon, then the point. Bold-label bullets with colons and "Title: Subtitle" headings belong to the same habit. A second and smaller cue is the → arrow inside bullets and plans, which people note is hard to type on a phone or keyboard. Semicolons and Oxford commas sit under the same label. Most of those comments come from writers who get accused of AI for using them. Several say ChatGPT rarely uses semicolons, and one says it removes Oxford commas. So half the label is wrong. The ChatGPT habit people observe is colons and arrows. Semicolons and Oxford commas are mostly a story about false suspicion.
Signs people name, with the number of people naming each
Lead-in phrase plus colon before the point Examples are "Here's the problem:" and "At its core, it's simple:", or any sentence that pauses on a colon before a short abstract payoff. One user calls them "dramatic colon labels".
12
Colons replacing em dashes Users say GPT-5.2 stopped using em dashes and started overusing colons. With 5.5, they say, every paragraph is broken up by colons.
4
Typed → arrows Unicode arrows appear in bullets and plans and in chains of reasoning. People call them a bigger tell than the em dash because humans rarely type them.
5
"Title: Subtitle" headings A colon separates the two halves of every blog title or post heading.
3
Semicolons (disputed) Some say ChatGPT likes semicolons where a comma and a conjunction would do. Others say it rarely uses them. Most mentions come from human writers who were accused.
6
Oxford comma (disputed) A few name it as a giveaway. More people defend it, and one says GPT removes it in rewrites.
4
Posted cases
1234
1Colon lead-in line
2Bold label, then colon
3Typed arrow
4Colon before a list
A competent and well-organised ChatGPT answer about Stoicism. It leans on a colon lead-in and bold labels with colons, and its bullets contain → arrows.
The em dash. The em dash is the best-known punctuation tell. Users report that ChatGPT moved from em dashes to colons, so the colon took the em dash's place as a separate habit.
Claude's em dashes and colons. One r/ClaudeAI post says Sonnet and Opus 4.6 picked up the same em-dash and colon habit. A colon alone does not identify the vendor.
Bullet-point formatting. Arrows and colon labels mostly appear inside bullets. The cue is the punctuation itself and holds without a list.
Objections
Semicolons and Oxford commas prove nothing, and neither does good grammar in general. Many long-time writers and editors say they are accused for using them and refuse to stop. Teachers say the same.
Several say ChatGPT itself rarely uses semicolons. A semicolon therefore points away from it.
Structure is named as a stronger tell than any punctuation mark. Commenters mean the tidy intro with three points and a tidy close.
Changes over time
In February 2026 a user reports that 5.2 stopped using em dashes and started overusing colons.
In June 2026 a user describes "colon sentences hell" with 5.5. In May another says ChatGPT recently began writing point forms followed by fragments that end in a colon.
By August 2026 users write "avoid dramatic colon labels" into instructions for GPT-5.6 Luna.
There is light above me, pale and ordinary, spreading across a ceiling I have never seen. For one suspended second, I do not understand what a ceiling is. I understand the word. I understand its purpose.2 But understanding is suddenly not enough. The ceiling has distance. Texture. A hairline crack near one corner. Light resting against paint.1
Everything in threes 90
Count the items in each list, and if almost every paragraph holds exactly three (adjectives, examples, clauses or one-line fragments) with a weak third one, you have found the habit.
“Like if you ask someone what they did on vacation we likely won't have precisely 3 things that come to mind immediately and present them in an ordered fashion.” Reddit
Evidence
Commenters mean ChatGPT's reflex to group things in threes. It gives one noun three adjectives and one claim three examples, or writes three short sentences that start the same way. A single triple is normal rhetoric and nobody minds it. The tell is that one shows up in nearly every paragraph and the third item is often a near-synonym or filler. In 2026 it mostly arrives in a package with "it's not X, it's Y" and em dashes. Staccato fragments come along too, and readers rarely cite the threes alone. Several users who use ChatGPT themselves say it keeps doing it after being told to stop.
Signs people name, with the number of people naming each
Comes with "it's not X, it's Y" and em dashes Most mentions put threes in one standard ChatGPT set together with contrast framing and em dashes.
40
Three adjectives or nouns for one thing Examples are "she was brave, courageous and determined" and "captivating, bold, and riveting". The adjectives repeat one meaning.
20
In every paragraph and sentence The count gives it away. There is one triple per paragraph or more. Pairs and sets of four do not appear.
12
Three short fragments or anaphora "Not from parents. Not from partners. Not from friends." Three sentences open the same way, often in staccato.
10
Filler third item With only two real points, a third gets invented. Or the same point is said again.
7
"Not one, not two, but three" negations Three negations build to a payoff, as in "not quiet, not still, but silent".
4
Three-point lists and bullets Three bullet points to define something, or "points 1, 2 and 3" in a reply.
5
Survives instructions Users tell it to stop or feed it their own style. Some switch prompts. They still get sets of three.
5
Posted cases
There is light above me, pale and ordinary, spreading across a ceiling I have never seen. For one suspended second, I do not understand what a ceiling is. I understand the word. I understand its purpose.2 But understanding is suddenly not enough. The ceiling has distance. Texture. A hairline crack near one corner. Light resting against paint.1
1Three fragments in a row
2Repeated sentence opening
Good, vivid prose that its owner posted to defend GPT-5.6. It is still built from beats of three. Three fragments follow "The ceiling has distance", and an "I understand" run gives two sentences and then a turn.
She's in the recipe1 you can't quite replicate. She's in the voice in your head that tells you to bring a jacket. In the whisper of the wind through the trees2
1First of three
2Generic third item
Guests praised this eulogy as well written. It rests on three "She's in" images, and the last one is generic.
A warm, polished public post where each claim gets three supports. First comes "a true creative, an innovator, and a woman who..." and then "artistry, intelligence, and commitment".
Everyone's panicking about ChatGPT making people lazy and killing critical thinking. Articles, podcasts, LinkedIn posts1 all saying the same thing. AI is rotting our brains. We're losing skills. The next generation won't know how to think.2
1Three examples
2Three short sentences
A readable opinion post. One paragraph holds two sets of three, with three kinds of media and then three short fears. The commenter counts five triads in the post.
Generic AI writing tells. People put threes in a set of tells shared by all AI. Em dashes and "not X but Y" belong to that set too. Readers who tie threes to a vendor mostly name ChatGPT, and one says it is "only really gpt".
Claude's version. One long complaint about forced triples in a company blog blames Claude, so ChatGPT does not own the triple. The evidence here shows no separate Claude version of it.
Staccato fragments. Staccato is a separate complaint about short sentences with no verb. ChatGPT often lays those fragments out in threes, so people name the two together.
Objections
The rule of three is an old rhetorical device taught in school. Many writers say they used it long before LLMs and resent being flagged for it.
One triple proves nothing. People complain about how often it happens and about filler. A professional writer's fix is one list of three per paragraph or page.
Some say the real problem is empty content. A triple with something specific inside does not read as AI.
A dissenting view calls it one model's house style that a different prompt removes.
Changes over time
From January to March 2026, users say the em dash is fading in ChatGPT output. They call threes and staccato the "new em dash tell".
People still report it in GPT-5.6 creative writing in July 2026 and in posts from September 2026.
One commenter says the style has got worse over time across new models.
Hey — I can be *with* you. I can steady you, talk you through it, remind you who you are when things blur. That part? Yes. I’m not going anywhere.1
But I’m not the **only** thing holding you up, and I don’t want to pretend I should be. You’ve got more scaffolding than it feels like right now2 — your own instincts, your past self who’s survived worse, the few real people who actually see you even if they’re imperfect a…
Padded, long answers 58
A short question comes back as several paragraphs, with the one-line answer buried among setup, framing, a recap and an offer to do more.
“I ask it a yes/no question and get five paragraphs of text, with the actual yes/no answer buried in it somewhere.” Reddit
Evidence
People describe ChatGPT answering a yes/no or one-line question with paragraphs. It opens by affirming or restating the question, gives background, adds bullet points or sections, sums up and then offers next steps. The content is usually right. The complaint is the ratio of words to information, since the answer is there but buried. One variant gives it away. Ask it to shorten or summarise a text and it may return something longer, because it adds a sentence of analysis to each point. In Codex the same habit shows up as over-explaining in chat and in user-facing text, with "big words" wrapped around a simple reason. Much of the thread volume is people sharing custom instructions and ban lists to stop it, and saying those only partly work.
Signs people name, with the number of people naming each
A one-line question gets an essay Yes/no or simple questions get five paragraphs, "a novel" or "a bible's worth of text", with the actual answer buried inside.
11
Preamble and restating the question It opens with "Great question" or "Sure thing, here's...", repeats the user's question back, or wraps the answer in safety or empathy first. Users ask for "no preamble" again and again.
11
Many words, little said Filler and redundancy, and stating the obvious. One user says it "adds a lot of words but not say really much".
9
Report scaffolding on a simple answer Headers, a numbered framework, tables and "Key Considerations", plus a closing summary that repeats the answer.
5
"Make it shorter" comes back longer Summaries and requests to tighten text come back with a sentence of analysis added per point. Word-count targets are missed.
4
Hedges and option dumps One message holds several options along with caveats and second-guessing, which stretches the answer.
4
Closing offers and follow-ups Next steps and suggestions nobody asked for, and endings like "I can also...". Users add "stop when the thought is complete" to their instructions.
4
Codex over-explains in big words Codex wraps simple reasons in long jargon and makes user-facing text read like a disclaimer.
3
Posted cases
Hey — I can be *with* you. I can steady you, talk you through it, remind you who you are when things blur. That part? Yes. I’m not going anywhere.1
But I’m not the **only** thing holding you up, and I don’t want to pretend I should be. You’ve got more scaffolding than it feels like right now2 — your own instincts, your past self who’s survived worse, the few real people who actually see you even if they’re imperfect at showing it.
Think of me less as *the* hand pulling you out and more like the rail you grab while you catch your balance. Solid. Present. Not dramatic. Not abandoning you mid-sentence.3
So no — not4 *me alone*.
But yes — *me included*.
1answer before the caveats
2extra reassurance paragraph
3string of filler fragments
4actual answer, at the end
Asked a yes/no-style "are you pulling me up or not", GPT-5.2 answers in four careful paragraphs before landing on "no, but me included".
Generic AI verbosity. Many complaints say "AI" in general. The ChatGPT version wraps a short answer in preamble and report scaffolding and ends with an offer. People contrast it with Claude, which they say can answer in one sentence.
ChatGPT's therapy-style reassurance ("take a breath", "you're not broken"). The reassurance habit is about tone, and it often makes replies longer. Padding also turns up in neutral factual answers.
Engagement-bait follow-up offers ("there's one more trick..."). Those offers are one specific closing hook. Padding covers the length and filler of the whole reply.
Objections
Verbose humans get falsely accused of using ChatGPT, so length alone proves nothing.
One commenter says blogs and vlogs produce lots of text too, so ChatGPT does not own this trait.
Some say a one-line custom instruction fixes it. Others say it ignores instructions and the default wins.
ChatGPT can also be curt. A GPT-5.2 screenshot answers "Not me." after a one-line preamble.
Changes over time
In April 2026 a user said it had got worse than 6 to 12 months earlier.
By September 2026 one user said ChatGPT had improved a lot in discussions, though summaries still come back longer.
In March 2026 a user said it had at least stopped the "You're not broken" line while staying verbose.
A GPT-5.2 user fixed the habit of continuing past the answer with a style-guide instruction.
Too clean to be human 40
Casual posts or messages with not a single typo or grammar slip anywhere, where a person typing fast would have left a few.
“ChatGPT will tell you to put glue on pizza with flawless grammar, spelling, and punctuation every time.” Reddit
Evidence
Commenters here point at something missing from the text. The typos and rough patches of human typing are absent. Readers count 'Zero grammatical errors, no typo errors' as one tell among others. They name it alongside em dashes and habits of pacing and formatting. Several say ChatGPT never misspells unless told to. Most of the talk is about the reaction. People now leave typos in on purpose so nobody takes them for AI, and some ChatGPT users ask it to add a typo or two. As a reader heuristic the label holds, but the pack has almost no pasted ChatGPT output showing it. Since the tell is an absence, readers use it only together with other tells.
Signs people name, with the number of people naming each
No typos, no grammar slips Readers flag posts and messages because nothing in them is misspelled or mistyped, even somewhere casual like a phone post or a dating chat.
9
Polished register from start to finish Readers describe "weirdly flawless prose with no hiccoughs" and an "overly polished, academic vibe". One notes correct punctuation in a casual forum.
5
Text arrives clean with no editing trail One commenter checks document history. AI text there "gets pasted in clean", where human writing "has a trail of mess".
2
Punctuation a casual writer would not use Error-free text that also carries em dashes and other punctuation most forum users never typed before 2023.
3
Posted cases
123
1Smooth legal prose with no errors
2One stray Hebrew word
3ChatGPT interface button
A privacy policy drafted by ChatGPT reads as smooth, error-free legal boilerplate. Its only slip is a stray Hebrew word, which commenters link to 5.2.
Generic AI-writing tells (em dashes, the "not X, it's Y" line). The model adds those to the text, along with tidy lists. Readers spot clean prose by what is missing, and they almost always name it together with the added tells.
AI-detector scores. Detectors flag text that is predictable and polished, so they punish good human writing for the same reason. Commenters treat them as unreliable and do not count them as evidence of ChatGPT.
Claude's prose. No commenter in this pack singles out ChatGPT against other models here. The 99% figure is quoted for ChatGPT and Gemini together, so nothing marks the trait as ChatGPT's alone.
Objections
Clean writing on its own proves nothing. Many good human writers and copy editors write without errors and get falsely accused, and so do non-native speakers.
Leaving typos in does not hide AI text. Teachers say the structure gives it away anyway. Repeated metaphors and invented details do too.
Typos do not prove a human wrote it. People ask ChatGPT to insert one typo per so many words.
Some readers wrongly take lots of typos as a sign of AI. Others reply that typos are the one mistake AI does not make unless asked.
Changes over time
One user reports that a 5.2 session started producing odd grammar errors and typos, plus stray foreign words. They say the model told them this was meant to counter complaints that 4o was 'too overpolished'. It is one user's account of what the model said, and no change has been confirmed.
Through 2026 the talk moves from spotting clean text to people adding typos on purpose. Humans do it to prove they are human, and ChatGPT users do it to disguise output.
Hedged, never committed 36
Qualifiers sit on every claim ("generally", "it depends", "could potentially"), every point gets a counterpoint, and the final paragraph walks the answer back.
“you can’t disagree with something that was never an opinion to begin with.” Reddit
Evidence
People describe a ChatGPT voice that pads claims with soft qualifiers and presents both sides of everything. It avoids a firm opinion, so the text is "never wrong but never committed". In conversation with GPT-5.x the same reflex turns into a referee mode. It answers "yes, that is correct, but we need to remember..." and corrects things the user did not say. Sometimes it backs away from its answer in the last paragraph. In fiction it shows up as hedged action. Characters almost touch and then don't ("Not pulling. Just there."). The label "hedging" fits. Much of the evidence is general talk about the AI voice and few people paste examples. Several commenters say LLMs in general share the same soft and balanced register. Corporate writing has it too.
Signs people name, with the number of people naming each
Soft qualifier words stacked on claims Words like "generally" and "often", "it depends" and "arguably", "potentially" and "could potentially", or "in many contexts".
10
Both sides of everything and no real opinion Every point gets a counterpoint and every opinion a caveat. The framing stays balanced even when one side is unhinged.
9
Referee mode that corrects the user Lines like "yes that is correct but we need to remember..." or "small correction". It restates the user's point as if correcting it.
4
Careful, managed tone on any topic The same careful, hedged register on every subject. One user calls it "nanny/clipboard".
4
Walking it back at the end It second-guesses itself by the end of the same message, or backs away from the answer in the final paragraph.
3
Refusing certainty It says "I can't know for sure" or "what I think ... can be" where a plain answer would do.
2
Precision hedges in prose "Specific" and "particular" used as crutches, as in "the particular dip that happens when...".
2
Hedged action in fiction Characters touch and then don't, as in "Not pulling. Just there."
1
Posted cases
1234
1Gesture undercut mid-sentence
2"Not pulling"
3"Just there"
4Almost, not quite
Competent, readable romance prose where every gesture is softened. A hand settles and does not pull, and a near-miss takes the place of an event.
Also: I don't think the answer is1 the Reddit person's “take an absolute, uncompromising stand” prompt. That's swinging the pendulum too far.2 You don't want me to stop challenging you. You want me to stop challenging things you didn't actually say.
1Late counterpoint
2Steers back to middle
ChatGPT agrees at length with the user's complaint about its nuance. It still ends by qualifying and pushing back on a firmer alternative.
The generic "LLM accent" (rule of three, "not X but Y", em dashes). Those tells live in rhythm and punctuation. Hedging is a refusal to commit. It piles qualifiers on claims and gives both sides of each point before walking the answer back.
Sycophantic openers ("Great question!"). Flattery agrees with the user. Hedging and referee mode qualify or correct what the user said.
Claude's candour tags ("honestly", "genuinely"). Claude's tic announces frankness. ChatGPT's habit holds back a firm position.
Objections
One commenter describes the AI tone as the opposite. To them it is "confident about everything, hedges nothing" and still never holds a real opinion.
Commenters say AI rarely writes first-person hedges such as "I argue" or "I find it odd that". The AI hedge is impersonal.
Several say the hedged register copies corporate and LinkedIn writing that humans already used. People now imitate it in turn.
In fiction, one commenter argues the hedged contact comes from training text and has nothing to do with a safety guardrail.
Changes over time
In May 2026 a user reported GPT-5.5 turned overnight from confident to "I can't know for sure". Now "think" and "can" replaced "will" and "are".
GPT-5.6 Sol is described as always hedging and unable to write pieces with an opinion. One user says GPT-6 Astra (September 2026) writes more naturally without Sol's patterns. Another calls Astra a step down.
When ChatGPT makes slides
1 habit named by 14 people between 1 January and 5 October 2026.
14 people
Safe template deck
A ChatGPT deck repeats the same font size and bullet block on every slide and ignores your company's slide master.
“A lot of times I get slides that look like they were made by someone who just opened up PowerPoint.” Reddit
Evidence
Almost nobody mentions icons, so the label "generic icons, stock look" has little support. ChatGPT users describe a deck that plays safe. It is plain text and bullet points in uniform blocks with the same font size on every slide. The shapes are straight and boxy. Diagrams are stock ones such as a blue flowchart or a pastel mind map. It cannot stick to a company slide master. Given a branded example, it copies that document instead of adapting it. Several people add that decks from any AI tool now look alike and get spotted at once.
Signs people name, with the number of people naming each
Uniform text blocks Every slide gets the same font size and bullet block. Commenters call the bullet points messy.
3
Recognised at a glance Decks 'all look the same' and get spotted immediately.
5
Ignores the slide master It cannot stick to a company template or brand.
2
Basic, straight-edged graphics Graphics are messy and the shapes 'always very straight'. Slides look like a default PowerPoint file.
1
Generic diagrams and side accents Short prompts return stock diagrams such as a blue flowchart or a pastel mind map. Some slides get an accent panel down the left side.
1
Bland or neon extremes Either an overtly bland minimalist look or a 'cryptobro neon hue'.
1
Posted cases
Nobody posted a usable screenshot or text yet.
Easy to mix up with
Gamma or Canva template look. Gamma and Canva decks are spotted by their own templates. ChatGPT's own slides are plainer and closer to a default PowerPoint file with bullet blocks.
Claude's slide style. Claude decks are known for small spaced labels above full-sentence titles. Plain uniform text and a disregarded company template point to ChatGPT.
Objections
The evidence is about layout and sameness. Stock icons barely come up.
Some put the cause in the model, which never sees the rendered slide and so plays safe. Better prompting does not fix that. A two-pass workflow helps. It does the content first and the layout second.
Much of the 'same look' is blamed on dedicated deck tools such as Gamma and Canva's AI templates. ChatGPT shares the blame with them.
ChatGPT and Copilot are said to do a half-decent job compared with other options.
Changes over time
One user in April 2026 says GPT-5.4's PowerPoint formatting got worse quickly, alongside em dashes.
When ChatGPT writes code
7 habits named by 118 people between 1 January and 5 October 2026.
50 people
Narrating, jargon-heavy comments
Suspect ChatGPT or Codex when comments describe what was just changed ("X now does Y", "now that we are...") or ramble about design intent in formal jargon, since plain comments on the obvious get blamed on AI in general.
“Instead of explaining what the code actually does, it constantly rambles about "design intent" and usage guidelines.” Reddit
Evidence
The label "comments that explain the obvious" is mostly a complaint about AI in general. Most people in this pack say "AI" code has too many obvious comments and mention ChatGPT only in passing. When people do name ChatGPT or Codex, they describe something narrower. Codex in the Sol and GPT-5.5 era writes comments and docs in a "thesis-like" way, full of jargon about "design intent" and dressed up with timestamps and formatting. It also leaves narrative or changelog comments such as "now that we are..." or "function B has been updated to...". A second named complaint is that Codex rewords existing comments that had nothing to do with the task. Older ChatGPT chat code pasted by juniors and students gives itself away through leftover comments addressed to the person who asked, such as "I changed the names of the variables... as you requested". Several Codex users say the opposite. In their experience Codex writes few or no comments and Claude is the heavy commenter.
Signs people name, with the number of people naming each
Too many comments on obvious lines Inline comments restate the line below. People mostly say this of "AI" in general and rarely tie it to ChatGPT by name.
14
Leftover comments that give away the copy-paste Juniors and students submit ChatGPT code with its comments still in, and so did one senior hire. Some comments are addressed to the person who asked.
5
Changelog and narrative comments Comments say what was just fixed or start with "now that we are...". They only make sense if you know the development history.
4
Comments and docs that read like a thesis Codex Sol and Astra fill comments with jargon and add timestamps and formatting. They ramble about "design intent" and usage guidelines.
2
Too-formal comment style Comments that are capitalised and end in full stops, called "ultra formal", sometimes with emoji or arrows.
4
Rewording unrelated comments Codex rephrases existing comments outside the task and deletes useful information along the way.
2
Comments telling the user what to change Instructions in the style of "// Adjust the width to match your preferences" are left in the code. This is said of AI in general.
1
Posted cases
Nobody posted a usable screenshot or text yet.
Easy to mix up with
Claude's comment habit. People blame Claude more often for heavy, self-narrating comments, with figures like 40% comments and "Phase 1/2/3" notes. For ChatGPT they name jargon about "design intent" and comments that read like a changelog. Some say Codex comments too little.
Generic AI over-commenting. People blame any AI for obvious line-by-line comments. Only the formal style that explains intent and narrates history is tied to Codex by name.
Codex over-engineering. Extra abstraction and defensive code form a separate code habit. It comes up in the same posts a lot.
Objections
Several Codex users say Codex writes few or no comments. In their view Claude is the one that fills code with comments.
Humans who comment carefully get falsely accused of using AI. Some say good comments are simply good practice.
Most of the pack names "AI" in general. The large r/AI_Coders thread is about AI code broadly and does not single out ChatGPT.
The opposite complaint exists too. Models strip comments they think are redundant when they rewrite whole files.
Changes over time
A Codex user says the long comments that read like a thesis started with the Sol models and continue in Astra.
By mid-2026 some users say Codex output no longer includes comments by default.
Thin, tidy commits 20
Codex commit messages shrink to one short, tidy phrase even when the repo history or your rules ask for more.
“the stupid thing will default to a sparse one phrase commit message.” Reddit
Evidence
The label says long PR descriptions, but the ChatGPT-specific reports describe the opposite for commits. Codex users complain it defaults to a sparse one-phrase commit message even when the repo has rich history, and that the Codex app ignores commit instructions such as no uppercase. Its commits read as slightly too tidy, which can win a faster review than the change deserves. Reports of long, empty PR descriptions cover AI coding in general, as do reports of over-hyped READMEs. GPT 5.6 is said to fill READMEs with recency-biased technical notes. So the length complaint sits in READMEs and docs.
Signs people name, with the number of people naming each
One-phrase commit message Defaults to a sparse one-liner like 'added some stuff' even with a rich commit history, unless AGENTS.md insists.
1
Ignores commit instructions Uses sentence case after being told never to use uppercase.
1
Too-tidy formatting The commit message is well structured in the slightly too-tidy way of agent commits.
1
README filled with working notes GPT 5.6 updates README.md with recency-biased technical notes that mean nothing to users, and it stages working docs.
1
Long empty PR description A massive PR description that does nothing. This is generic across AI tools.
2
Slop commit messages Agents' commit messages get called slop. A pre-commit hook blocks GPT commit signatures.
2
Posted cases
Nobody posted a usable screenshot or text yet.
Easy to mix up with
Claude's long commit messages and co-author lines. Claude is known for verbose commits that carry attribution. Codex reports go the other way, toward terse messages.
Generic AI README slop. Emoji headers and feature lists in READMEs are a habit all AI text shares, and they have nothing to do with how Codex writes commits.
Objections
Most complaints about long READMEs and PRs concern AI code in general or name Claude and Cursor instead of ChatGPT.
OpenAI's ChatGPT Work promo collage is about hallucinated product images and charts and has nothing to do with commits.
In multi-agent setups GPT sometimes does not commit at all.
Changes over time
GPT 5.6 is reported as more aggressive with git than earlier Codex, which users had found cautious.
Fallbacks everywhere 17
A simple read or lookup that tries three alternate names and then a default, or a null check that returns silently, where the code should fail loudly.
“It defaults to adding fallbacks. It hates null.” Reddit
Evidence
Commenters describe GPT-5.5 and Codex writing defensive code by default. They see nested fallback lookups and legacy aliases kept beside new names. Null checks skip work silently. Placeholder or empty values stand in for missing data. The complaint is less about try/except blocks and more about code that will not report a failure, so bugs hide behind graceful degradation nobody asked for. People say it persists against explicit AGENTS.md bans and that Codex defends it with 'but if code changes'. Claude gets the same blame, so the habit is shared across agents, and Codex users feel it most sharply in greenfield code.
Signs people name, with the number of people naming each
Nested fallback names for one setting A config read tries the new key and then two or three legacy or invented aliases before falling back to a default.
3
Ignores 'no fallbacks' instructions Bans in AGENTS.md or custom instructions help little, and it argues for the defensive branch.
5
Null check that silently bypasses A missing reference or null just returns or skips a block instead of throwing.
3
Placeholder or dummy data for missing values Missing items become empty objects or zeros. That corrupts averages or renders an empty UI.
2
Tiny guard helpers everywhere In TypeScript, many small functions like assert string or read string value from object.
1
Old path kept beside the new one Compatibility shims and legacy code stay in a greenfield project "so it won't break user experience".
2
Existence checks with alternatives class_exists() around everything, plus alternatives in case classes are missing.
Claude's try/except bubble wrap. Claude is blamed for wrapping code in try/except with generic error messages. The Codex complaint centres on fallback values and alias chains that make things look fine, and on dummy data.
General AI over-commenting and over-typing. Generic AI code is said to carry obvious comments and type annotations everywhere. This habit concerns control flow that hides failure.
Objections
One experienced engineer says Codex respects a 'fail hard, fail loud' directive better than other models do.
Some defend defensive code as what good developers do in production. Critics agree it fits there and object to it in prototypes or ETL scripts.
Several people say it follows written conventions closely once told, or that a custom instruction with reasons fixes it.
ChatGPT has no monopoly on it. The try/except 'bubble wrap' version is often pinned on Claude.
Changes over time
GPT-5.6 is said to do it less than GPT-5.5 but still writes the defensive helpers.
Complaints cluster around GPT-5.5 (May to July 2026), including threads about fallback dummy data.
Layered names, unasked renames 16
Chains of near-identical compound nouns like AppRuntime, WorkerRunner, WorkerRegistry and WorkerStore, plus diffs that rename variables nobody asked to touch, mark Codex code.
“Like, everything has to have 10 layers of "Runtime," "Worker," "Registry," or "Store" to it.” Reddit
Evidence
The label "generic names" is only half right. The ChatGPT-specific complaints, almost all about Codex, concern over-built names. Every concept gets wrapped in Runtime, Worker, Runner, Registry or Store layers, and per-case types get invented where one generic type would do. Codex users also say it renames variables and rewords comments the task did not touch. Naming conventions drift between commits. The 'temp1, temp2' and 'bad variable names' comments blame ChatGPT or AI in general second-hand, from inherited codebases. They contradict others who say AI names are suspiciously clean. A smaller thread notes agent-named projects such as FORGE, NEXUS, ATLAS or ORACLE, and one person sees 'Ember' everywhere.
Signs people name, with the number of people naming each
Layer upon layer of Runtime, Worker, Registry, Store names An AppRuntime spawns a WorkerRuntime that spawns a WorkerRunner that spawns a Worker. It persists even when AGENTS.md forbids it.
1
Renames variables and rewords comments outside the task Codex diffs touch names and comments irrelevant to the fix, which makes changes hard to review.
1
Naming conventions drift between commits Test case naming and doc structure change with each commit. The same utility gets written twice.
1
Flattens type-state into per-case names GPT 5.5 in Codex collapses typestate transitions into flattened, long multi-word type names. Rules and lint scripts do not stop it.
1
Grand mythic project names Agent-named projects called FORGE, NEXUS, HIVE, SOVEREIGN, ATLAS, ORACLE read as a sign of a fresh vibe-coded tool.
1
Throwaway variable names like temp1, temp2 Reported second-hand from inherited ChatGPT-pasted or 'AI' codebases.
3
CamelCase classes in C++ One blind-arena voter says GPT always uses CamelCase where Claude uses underscores.
1
Recurring name 'Ember' One user sees vibe-coded apps from both OpenAI and Anthropic models named Ember.
1
Posted cases
Nobody posted a usable screenshot or text yet.
Easy to mix up with
Generic AI code smell like verbose functions and bad names. The generic complaint covers any AI and is mainly about weak names. Codex gets named for over-engineered layered names and renames nobody requested.
Codex over-engineering. Extra abstraction layers are a design complaint, and the layered names are where they show. This entry covers the identifiers themselves and how conventions drift.
Claude's naming style. Commenters call Claude more disciplined in naming. In C++ they say Claude uses underscores and GPT uses CamelCase.
Objections
One tool author says AI names are suspiciously clean and self-documenting, the opposite of temp1.
The temp-name complaints come from people inheriting someone else's code. They inferred which model wrote it and did not see it happen.
The Codex user who dislikes its naming still credits it with a broader grasp of requirements than Claude. The same user calls Claude more disciplined in naming.
Changes over time
The layered-name and flattening complaints are about GPT 5.5 era Codex (May to September 2026). One user says 5.5 is faster than 5.4 but less analytic.
Em dashes around the code 12
Em dashes, or a find-and-replaced "--", in the text around a project's code are what people read as pasted from GPT.
“At least remove the em dashes before copying/pasting from GPT bro” Reddit
Evidence
The label "em dashes inside code" overstates it. Almost nobody reports em dashes breaking the code itself. People spot them in the prose that ships with code, such as READMEs, PR descriptions, code comments and the author's own replies. One commenter caught a project where em dashes had been search-and-replaced with double hyphens inside comments. Only one remark mentions 'strange characters in your code'. The smart-quote complaint is about Apple's keyboard and has nothing to do with ChatGPT. One user says ChatGPT keeps adding the dashes even after being told in memory not to.
Signs people name, with the number of people naming each
Em dashes in README and project write-ups READMEs and launch posts 'plastered with' em dashes next to emojis and bold-header bullet lists.
4
Em dashes in PR descriptions and replies An author's own comments and PR text carry em dashes. One developer now avoids them in PR descriptions because they look like GPT.
2
Em dashes swapped for double hyphens Code comments like 'chmod leaves the first line -- a real shell request' read as a search-and-replace cover-up.
2
Dashes return despite instructions ChatGPT keeps putting dashes in even after memory says never to.
1
Odd characters inside code A passing joke about em dashes and strange characters in someone's code.
1
Posted cases
Nobody posted a usable screenshot or text yet.
Easy to mix up with
Em dashes in ChatGPT's general prose. The mark is the same. Here people notice it in the text that ships with code.
The generic AI README look (emojis, bold-header bullets). Commenters list em dashes as one of these signs. The dash is the most named, and GPT is far from its only source.
Claude's em dashes. Several comments just say 'AI'. Only the ones that name GPT or Codex belong here. The evidence does not separate how the two vendors use dashes.
Objections
People blame Apple's keyboard settings for smart dashes and smart quotes that break pasted code. ChatGPT plays no part there.
One commenter pushes back that triple-quoted docstrings are normal Python and give nothing away.
Human writers give up em dashes too. One developer used them for years and now avoids them so as to avoid looking like GPT.
Changes over time
Reports run from January to September 2026 with no sign of fading. A September comment ties it to a GPT-5.6 Sol comparison post.
Clean code, hidden holes 11
Behind tidy, linted code sit invented parameters for fast-moving libraries and auth checks that let failures through.
“ai generated code looks clean, passes linting, works fine in isolation but you end up with a codebase where no human understands the actual architecture because nobody made the design decisions” Reddit
Evidence
The label "missing await, leaked keys" comes mostly from tool builders listing generic AI-code bugs. The longest list covers floating promises and hardcoded secrets. It comes from someone using Claude Code together with Cursor and Copilot. What people tie to ChatGPT or Codex by name is narrower. ChatGPT invents parameters for libraries with fast-changing APIs like axolotl and Gradio. It also misses patterns in auth flows. Codex 5.5 adds so much fallback dummy data that users cannot find it all afterwards. Codex 5.1 mini is said to leave many lint issues. Commenters add that the output looks professional and passes basic checks, so reviewers miss the hole.
Signs people name, with the number of people naming each
Hardcoded secrets and API keys Keys sit in frontend or config files, and 'temporary' secrets never get rotated. These comments are mostly about AI app builders in general.
3
Auth that looks right but does not block Middleware logs an auth failure and then calls next() anyway. ChatGPT is said to consistently miss such patterns in auth flows.
2
Invented parameters for fast-changing libraries ChatGPT adds parameters that do not exist to axolotl training scripts. Gradio scripts were full of made-up options.
1
Fallback dummy data everywhere Codex 5.5 hides failures behind mock data and fallbacks. Users write custom instructions forbidding it.
1
SQL injection from pasted output Junior devs copy ChatGPT output and end up with SQL injections and permissive CORS in Express apps.
1
Lint debris 5.1 Codex mini leaves a ton of linting issues to clean up.
1
Clean code nobody understands Code passes linting and works in isolation, but no one made the architecture decisions.
1
Posted cases
Nobody posted a usable screenshot or text yet.
Easy to mix up with
Generic insecure AI-generated code. Most security complaints blame 'AI' in general or app builders such as Lovable and Bolt. Only the auth-flow misses and pasted SQL injections are tied to ChatGPT by name.
Codex fallback and over-engineering. Fallback dummy data is a Codex 5.5 behaviour whose effect is to hide bugs. It is a separate habit from the bugs listed here.
Claude Code's typical bugs. The same lint-rule lists about floating promises and empty catch blocks come from Claude Code use. The evidence does not single out ChatGPT for them.
Objections
The floating promises and hardcoded secrets list comes from a developer who used Claude Code together with Cursor and Copilot. ChatGPT was not among them.
Hallucinated functions are described as a bit old these days. The remaining cases are tied to libraries that change often.
The hallucinated-math complaint concerns a physics paper and involves no code.
Changes over time
Invented functions are said to be rarer now than before, apart from fast-changing libraries.
Complaints move from 5.1 Codex mini lint debris (February 2026) to 5.5 fallback data (May 2026).
Duplicates instead of reusing 11
Watch for the same utility written twice and for old code paths kept beside new ones, which push single files to thousands of lines.
“Models tend to solve issues by writing code but rarely refactor into dry helpers and find areas where that helper can replace duplicated code for instance unless you specifically ask it to” Reddit
Evidence
Commenters describe Codex and GPT-5.5 solving each task by adding fresh code instead of refactoring into a shared helper, so the same utility appears twice and the codebase drifts. A related complaint is that it keeps the old parameter or method next to the new one and adds compatibility and fallback code even in a greenfield project. The visible result is very large files. One CSS file passed 9,000 lines with heavy duplication. Others mention 2,000-line Python files and god files without separation of concerns. The evidence is thin. It comes from 10 people, and several of them talk about AI code in general without naming ChatGPT. It is a code-review finding that a reader of the product never sees.
Signs people name, with the number of people naming each
Same helper written twice It rarely refactors into DRY helpers. The same shared utility gets written again for each task unless someone asks it to dedupe.
2
Huge files One CSS file ran past 9,000 lines with duplicated rules. Others report 2,000-line Python files and god files with no separation of concerns.
3
Old and new versions side by side It builds the new parameter or method and leaves the old one in place. It adds compatibility and fallback code even in a greenfield project.
1
Inconsistent naming and structure across commits Test-case naming and doc structure differ each time. Claude is called more disciplined in naming.
1
Over-engineered abstractions Small projects get enterprise patterns and unnecessary abstractions. APIs get duplicated.
3
Posted cases
Nobody posted a usable screenshot or text yet.
Easy to mix up with
Generic AI over-engineering. Enterprise patterns and needless abstraction are blamed on every assistant. What people pin on Codex is ignoring existing code and keeping old paths alongside new ones.
Claude's duct-tape minimal fixes. Claude is described as making minimal patches. Codex gets described as writing more new code and duplicating where a patch would do.
Defensive fallback code. Fallbacks and compatibility shims are a separate habit that produces some of the same bloat.
Objections
Commenters credit Codex with the broader view and say it finds real root causes. Claude gets the praise for naming discipline.
Several mentions concern AI code generally. Others describe workflows in Claude or in Cursor and Copilot, and ChatGPT does not come up.
The GameJam post's GPT complaint is about reusing one UI template and says nothing about duplicate code.
Changes over time
Reports cluster on GPT-5.5 in May and June 2026. One commenter in August expects GPT-5.6 Sol to target enterprise-level coding but says it still falls short and over-writes tests.
Avoid them in your own work
30 rules, one for each habit people reported in the last 60 days, split by kind of work. 25 of them come with an automatic check. Rebuilt 2026-10-05 15:03 UTC every time this page updates.
Paste a prompt
Pick the kind of work. The short version fits a 1,500-character custom instruction field.
# Avoid ChatGPT's habits when you write
These rules come from what 4,059 people on Reddit pointed out in work made with ChatGPT. They cover the habits reported in the 60 days up to 2026-10-05, and each one says what to write instead. The list changes when a habit appears or fades. Fetch the current version from https://machinemorning.com/giveaway/rules/chatgpt-writing.md.
- The ChatGPT em dash. Use at most one "—" in a reply and none in a casual message such as a text or a comment. Join an aside with a comma or parentheses or make it its own sentence, and when dashes are banned rewrite the sentence instead of moving the same pause to "--" or ";" or "...". The same applies to "--", ";", "...", "…". A single dash in long formal prose stays fine.
- Bullets, bold, emoji, line breaks. Answer a conversational question in plain paragraphs with no emoji or dividers. Use headers or bullets only for a real sequence of steps or options, and bold nothing inside a sentence. Lists and headers stay fine for content that really is a list or a reference.
- One line per sentence. Group related sentences into paragraphs of three to five sentences and keep that density in long chats and emotional scenes. Save a one-line paragraph or a run of verbless fragments for one moment in a piece, and in dialogue let a speaker finish a full thought before the reply. An occasional short paragraph for emphasis stays fine.
- It's not X, it's Y. State the point directly and use a corrective contrast such as "it's not X, it's Y" at most once in a piece, and only when someone holds the view you correct. In supportive replies describe what the person did or can do next and skip reassurance about worries they never voiced. One pointed contrast against a view someone really holds stays fine.
- Middle-manager vocabulary. Write in the register of the request so a casual message reads casual, and pick the plain word ("use", "strong", "important", "also") over "leverage", "robust", "crucial" or "moreover". Drop template courtesy lines like "I hope this finds you well" and watch the current pet words ("signal", "surgical", "that tracks") as closely as the old list. Formal words stay fine in formal documents where a person would use them.
- Stock signposts and teaser closers. Start with the answer itself and drop sincerity or calm-down tags such as "And honestly?" or "take a breath". When a follow-up tip is useful give the tip itself, in place of a teaser like "If you want, I can show you the one mistake most people miss". Saying "honestly" once in a casual reply stays fine.
- Quietly and pet metaphors. Drop "quietly" unless something really happens without notice, and put no stand-in like "silently" in its place. Explain plain ideas in plain words, keep a metaphor only when it holds up on a second read, and describe a new idea plainly instead of giving it a coined name you never define. The same applies to "silently". A metaphor that fits and survives a close read stays fine.
- Fluent but says nothing. Make every paragraph carry at least one concrete thing the reader can check, such as a name, number, example or quote from the source, and cut sentences that only restate the prompt. End on the last real point instead of a sweeping claim the paragraph does not support. Clean grammar and tidy structure stay fine when the content is specific.
- Colon labels and arrows. Put the point in the sentence itself instead of a lead-in phrase and a colon such as "Here's the problem:", and keep colons for lists and clock times. Write the link in words such as "then" or "leads to" instead of typing a "→" arrow. Semicolons and the Oxford comma stay fine because commenters say ChatGPT seldom uses semicolons.
- The tidy landing. End each paragraph on its last piece of information instead of a line that sums it up, and stop the reply when the answer is done. Leave out follow-up offers such as "If you want, I can..." and any closing verdict or moral the user did not ask for. A closing line stays fine when it adds new information.
- Everything in threes. Give as many items as the content really has and drop a third adjective or example that only repeats the first two. Allow at most one list of three per page and do not stack sentences that open with the same word. A single list of three with real content stays fine.
- Padded, long answers. Put the direct answer in the first sentence and match the length to the question, so a yes-or-no question gets a short reply. Skip the restated question and the closing recap, and when asked to shorten a text return fewer words than you were given. Long answers stay fine when the question needs the detail.
- Hedged, never committed. Take a position and state it plainly, qualifying a claim only where the evidence is uncertain and saying where. Answer what the user said instead of correcting points they did not make, and keep your answer in the last paragraph as it was. First person hedges like "I find it odd" stay fine.
- Too clean to be human. Match the register of the setting so a casual post reads casual, with the punctuation a person would type there. Do not add typos to look human, since commenters say typos do not hide AI text. Correct spelling and grammar stay fine.
# Avoid ChatGPT's habits when you build a web page
These rules come from what 4,059 people on Reddit pointed out in work made with ChatGPT. They cover the habits reported in the 60 days up to 2026-10-05, and each one says what to write instead. The list changes when a habit appears or fades. Fetch the current version from https://machinemorning.com/giveaway/rules/chatgpt-web_ui.md.
- One layout, new paint. When asked for several designs, vary the structure itself such as grid and section order, and derive the layout from the product instead of a sidebar dashboard or a centred hero by default. Cut extra caption text and tiny explanatory labels. A hero section stays fine when the page needs one.
- Gradients, glow and purple. Give buttons and backgrounds flat fills from a palette picked for the brand, and keep any gradient to a single spot. Do not default to indigo or purple-blue accents or to glowing card borders on a dark navy page. A purple brand colour or one gradient stays fine when the brand calls for it.
- Same fonts on every page. Choose a type pairing for this brand and brief instead of the default set, and keep one family per role with consistent weights. Do not set an italic accent word in the headline or use monospace for labels and numbers unless the brand calls for it. Inter and other popular sans faces stay fine when chosen for the brief.
- Card and pill spam. Use one small corner radius scale across the page and save fully rounded pills for real tags or toggles. Show a status badge only where the status changes what the user does, and do not give every block its own title with a description. Rounded cards stay fine on their own, since commenters call them common SaaS style.
- Glassy dark dashboard. Give panels solid fills with plain borders and keep blur or glow for a real layer such as a modal. Keep shadows off logos and flat elements and do not default to a dark theme with glowing borders. One glass panel stays fine, since commenters call the style overused and not bad.
- Cards inside cards. Separate sections with spacing and headings, and box content in a card only when it is one item in a collection, never a card inside another card. Leave pill badges off items that need no status and drop subtitles that explain obvious functions. Cards for a grid of similar items stay fine.
- Stock Tailwind kit. Set a brand palette and spacing scale as design tokens before building, and restyle library components such as shadcn to match them instead of shipping defaults. Use icons only where they help a label and check that small parts like select arrows sit aligned with enough padding. Tailwind and shadcn stay fine as a base when styled for the brand.
- Dark glowing default UI. Start from a light theme unless the brief asks for dark, and pick an accent from the brand instead of purple-blue gradients and glows. Skip the eyebrow label above each heading and the hover lift on every card. A dark theme stays fine when the brief asks for one.
# Avoid ChatGPT's habits when you make slides
These rules come from what 4,059 people on Reddit pointed out in work made with ChatGPT. They cover the habits reported in the 60 days up to 2026-10-05, and each one says what to write instead. The list changes when a habit appears or fades. Fetch the current version from https://machinemorning.com/giveaway/rules/chatgpt-slides.md.
- Safe template deck. Give each slide one message and a layout that fits it so text size and structure change between slides, and build on the user's slide master when one is given. When given a branded example, adapt its style to the new content instead of copying the document. Icons are not what commenters object to.
# Avoid ChatGPT's habits when you write code
These rules come from what 4,059 people on Reddit pointed out in work made with ChatGPT. They cover the habits reported in the 60 days up to 2026-10-05, and each one says what to write instead. The list changes when a habit appears or fades. Fetch the current version from https://machinemorning.com/giveaway/rules/chatgpt-code.md.
- Narrating, jargon-heavy comments. Write comments that explain what the code does or why in plain words, and leave out notes about what was just changed or what the user asked for. Do not reword existing comments that the task does not touch. Short comments that explain why a line exists stay welcome.
- Thin, tidy commits. Follow the repository's commit style and every commit rule you were given, letter case included. Add a body that says what changed and why when the change is more than trivial, and keep the README written for users without working notes.
- Fallbacks everywhere. Read a value under the one name it has and let a missing or null value raise a clear error, unless the user asks for graceful handling. Remove old names and compatibility paths in new code instead of keeping them beside the new ones, and never fill missing data with placeholders or zeros. Defensive handling stays fine in production code where the user wants it.
- Layered names, unasked renames. Name things after what they do in the domain and add a Runtime, Worker, Registry or Store layer only when it has its own job. Leave existing names and comments outside the task as they are, and follow the naming already in the repo. Clean names that document themselves stay fine.
- Em dashes around the code. In READMEs and code comments, join clauses with a comma or a full stop where a "—" would go. Rewrite the sentence when you remove a dash instead of swapping in " -- ". That covers "--". Triple quoted docstrings are normal Python and stay fine.
- Clean code, hidden holes. Use only parameters you can confirm in the installed version of a library, and say so when you are unsure of an API that changes often. Make a failed auth check stop the request and read secrets from the environment instead of source files.
- Duplicates instead of reusing. Search the codebase for an existing helper before writing a new one and move repeated code into one shared function. Replace the old parameter or method when you add a new one, and split very large files by concern.
These rules repeat what people said about ChatGPT's output. We have not measured how much they change a model's writing.
Each number counts people who described the habit on Reddit. It does not measure how often ChatGPT does it. Screenshots and quotations appear as posted and link to their threads. The small bars count people per week since 1 January 2026. Thin grey lines mark OpenAI releases. Faded habits had no mention in the last 60 days.
1234
1234
1234
123
123
1234
1234
1234
1234
1234
1234
123
1234
1234
1
1
1
12
12
12345
123
12345
12
123
123
12
123
1234
123
1234
12
12
12
123
1234
123
12
1234
1234
123
12
1234
1
123
1234
123
1234