70/100

Moderate evidence

ProblemPublished recordHealthProblem Space

Problematic engagement with generative AI measurement drivers contexts and outcomes

Truvace record
TRV-2026-2507raw data (JSON)
Version
v1Published
First published
Evidence type
Systematic review or meta-analysis
Sources
1 sourcePeer-reviewed
sha256
1b668d492edd…check it

Generative AI tools and conversational chatbots are increasingly embedded in education, work, and daily life, raising concerns about engagement that becomes difficult to self-regulate. This review synthesizes emerging research on problematic generative AI use, treating addiction-like language as part of a broader problematic-use construct rather than a clinical diagnosis. Following PRISMA 2020 reporting, a Scopus search executed identified 188 records. Included studies were characterised by research design and e…

The problem

A review of 188 records found that compulsive or dependent generative AI use is associated with technostress, psychological distress and lower wellbeing, though the studies are almost all cross-sectional and self-reported.

What this doesn’t fix

The studies reviewed are almost entirely cross-sectional and self-reported, so the relationships are associations rather than causal effects.

Sources

1 on file
  1. Social Sciences & Humanities Opendoi:10.1016/j.ssaho.2026.103890
    Peer-reviewed2026-10-20

Cite this record

v1

Truvace Impact Record TRV-2026-2507, v1: “Problematic engagement with generative AI measurement drivers contexts and outcomes.” Truvace, 2026-11-12. /record/TRV-2026-2507 (accessed on the day you copy it). sha256 1b668d492edd5c47…

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. Publishedv11b668d492edd…

    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-2507 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.