Truace
Subscribe
60/100

Moderate evidence

ProblemPublished recordHealthProblem Space

Full story
More
Export record JSONEmailLinkedInX

Generative artificial intelligence addiction is prospectively associated with psychotic-like experiences: Evidence from a two-wave longitudinal mediation and network study

Truvace record
TRV-2026-2544raw data (JSON)
Version
v1Published
First published
Evidence type
Observational study
Sources
1 sourcePeer-reviewed
sha256
ae1171bb4a4a…check it

Objectives With the rapid adoption of generative artificial intelligence (GAI) in learning, work, and daily life, concerns have grown about its mental health implications. Evidence beyond affective outcomes is limited. This study examined whether GAI addiction is prospectively associated with psychotic-like experiences and assessed indirect associations involving information overload and rumination. Methods A two-wave longitudinal design was used with 582 adolescents and young adults. GAI addiction, information…

The problem

In a two-wave study of 582 adolescents and young adults, those with higher generative AI addiction at baseline reported more psychotic-like experiences one month later (β = 0.19), partly through rumination.

What this doesn’t fix

Follow-up lasted only 1 month, and the authors describe the findings as prospective associations and potential correlates, not proof that generative AI addiction causes psychotic-like experiences.

Sources

1 on file
  1. Computers in Human Behavior Reportsdoi:10.1016/j.chbr.2026.101301
    Peer-reviewed2026-09-09

Cite this record

v1

Truvace Impact Record TRV-2026-2544, v1: “Generative artificial intelligence addiction is prospectively associated with psychotic-like experiences: Evidence from a two-wave longitudinal mediation and network study.” Truvace, 2026-11-12. /record/TRV-2026-2544 (accessed on the day you copy it). sha256 ae1171bb4a4a61fe…

Change history

1 version

Every change made to this record since it was first published, and why. Nothing has changed since it went up.

  1. Publishedv1ae1171bb4a4a…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-2544 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.