Skip to content
ESCAPE MERIDIAN

When does AI become a dependable colleague?

Full question

When does an AI become a dependable colleague?

EM read · 2026-10-29 · Evidence reviewed 2026-10-29

Markdown · JSON · For agents

Our read

Useful output still needs a workable handoff

Dependability means acceptable work in a particular setting, including recovery when the tool fails. This edition treats review burden and workflow fit as open conditions, rather than inferring dependable delegation from capability or adoption alone.

Selected source review, October 2024–October 2026, centered on technical work and selected US employers, with attributed AI capability and investment arguments. Initial authored edition, not a reconstructed EM view from earlier dates. Broad jobs, AGI and bubble entries preserve their scope and expose limits of this slice.

What this depends on

  • The person or institution using the work can specify what counts as acceptable and which failures matter.

Other explanations

  • A tool may be valuable as supervised assistance before autonomous delegation works.
  • A workflow can change to exploit model strengths rather than reproduce the previous task.

What would change this read

  • Comparable accepted-work outcomes that include checking, correction, escalation and missed errors.

This selected evidence does not justify a probability, date or numerical outcome range for this question.

Look more closely

Possible paths

More accepted work with useful human oversight

EM conditional scenario, not an estimated probability or a claim that this outcome has occurred.

Conditions along this path

  • Useful output or new capabilities outweigh checking and integration costs.
  • People can recognize and recover from consequential failures.
Review and rework absorb the apparent gains

EM conditional scenario, not an estimated probability or a claim that this outcome has occurred.

Conditions along this path

  • The task or tool produces costly errors or omissions.
  • New value does not offset correction and integration work.

Perspectives

Joel Becker, Nate Rush, Beth Barnes and David Rein

METR authors of the early-2025 controlled developer study · 2025-07-10 · From the author’s own work

Publication date of this study report.

In their randomized study of 16 experienced open-source developers completing 246 issues, AI access increased completion time by 19%. They explicitly restrict what this says about other developers, settings or later tools.

  • The study used early-2025 tools in developers’ familiar repositories; it is not an estimate for all work or present-day AI.

Nathan Wilmers, Regina Catipon, Maxim Massenkoff and Peter McCrory

Anthropic Institute researchers reporting on their employer · 2026-10-16 · From the author’s own work

Dated authored publication; this is not the date of every underlying observation or interview.

The report describes increased output alongside rising demands on human attention as AI use spreads internally.

  • Observations at one AI company; not a controlled estimate of the causal effect or of other employers’ results.

Joel Becker, Nate Rush, Tom Cunningham, David Rein and Khalid Mahamud

METR authors of the follow-up methods update · 2026-02-24 · From the author’s own work

Publication date of the authored source.

They consider greater developer speedup plausible by early 2026, but report that participation, task selection and time-accounting problems make the follow-up estimate unreliable.

  • This is a later team’s assessment of a changed experiment, not the same measurement repeated cleanly.

Joel Becker

METR author reporting technical-worker self-assessments · 2026-05-11 · From the author’s own work

Publication date of the authored source.

The survey reports substantial perceived value gains, while distinguishing value from task speed and cautioning that respondents can misestimate what AI contributes.

  • Self-report in a technical-worker sample, not audited customer economics or a measured effect on national productivity.

Sources and passages

How employment is changing at Anthropic 2026-10-16

Open original source

Publisher publication date, checked on original page.

Original publisher page and exact retained source reviewed. Source retention does not establish every downstream reuse or training right.

Exact retained Stream work/snapshot and SHA256 verified against the 29 October SELECT-only source packet. That lookup found no joined public Stream or bridge reading revision; no reading identity is invented.

This acceleration makes human attention the bottleneck for agent output.
Retained extracted text, character offsets [767, 839). Context (EM paraphrase): The authors report rising internal output alongside agent use and interpret human attention as a constraint. Adoption is not randomized; the report does not establish a general causal productivity effect.

Used in: Will AI take most jobs? · When does AI become a dependable colleague? · Does AI reduce the work needed for an acceptable result? · Who gets an entry point and shares the gains? · When can work be delegated without checking every step? · When is an AI deployment worth its total cost?

Measuring the Impact of Early-2025 AI on Experienced Open-Source Developer Productivity 2025-07-10

Open original source

Publication date displayed by the original publisher.

Original publisher page and exact retained source reviewed. Source retention does not establish every downstream reuse or training right.

Exact retained Stream work/snapshot and SHA256 verified against the 29 October SELECT-only source packet. That lookup found no joined public Stream or bridge reading revision; no reading identity is invented.

16 experienced developers
Retained extracted text, character offsets [1527, 1552). Context (EM paraphrase): Methods: developers worked on 246 real issues in familiar open-source repositories using early-2025 tools. This population does not represent all developers or later systems.
they take 19% longer to complete issues
Retained extracted text, character offsets [2468, 2507). Context (EM paraphrase): Core Result, first paragraph; interpret with Methods and the immediately following limitations table. Reported result for the 2025 study, not a current universal estimate.

Used in: When does AI become a dependable colleague? · Does AI reduce the work needed for an acceptable result? · When can work be delegated without checking every step?

We are Changing our Developer Productivity Experiment Design 2026-02-24

Open original source

Publication date displayed by the original publisher.

Original publisher page and exact retained source reviewed. Source retention does not establish every downstream reuse or training right.

Exact retained Stream work/snapshot and SHA256 verified against the 29 October SELECT-only source packet. That lookup found no joined public Stream or bridge reading revision; no reading identity is invented.

the data from our new experiment gives us an unreliable signal of the current productivity effect of AI tools
Retained extracted text, character offsets [431, 540). Context (EM paraphrase): Opening discussion, paragraph beginning Unfortunately. Subsequent paragraphs describe participation, task selection and time measurement.

Used in: When does AI become a dependable colleague? · Does AI reduce the work needed for an acceptable result? · When can work be delegated without checking every step? · When is an AI deployment worth its total cost?

Measuring the Self-Reported Impact of Early-2026 AI on Technical Worker Productivity 2026-05-11

Open original source

Publication date displayed by the original publisher.

Original publisher page and exact retained source reviewed. Source retention does not establish every downstream reuse or training right.

Exact retained Stream work/snapshot and SHA256 verified against the 29 October SELECT-only source packet. That lookup found no joined public Stream or bridge reading revision; no reading identity is invented.

Participants self-reported a median 1.4–2x change in the value in their work due to AI tools.
Retained extracted text, character offsets [1308, 1401). Context (EM paraphrase): METR surveyed 349 technical workers in February–April 2026. The range reflects self-reported value under different question formulations, not a confidence interval or observed causal return. METR gives reasons to doubt the magnitude and distinguishes value from speed.

Used in: When does AI become a dependable colleague? · Does AI reduce the work needed for an acceptable result? · When is an AI deployment worth its total cost?

Evidence updates and read history

This is the first recorded EM edition of this question. Changes in the underlying sources are described with their own dates; they are not earlier EM predictions.

Change record in JSON

Edition jobs-quality-2026-10-29

Retained editions: jobs-quality-2026-10-29

Explore the wider topics

Work & businessHuman-AI collaborationReliability in deployment

Challenge a source or interpretation · All questions

Editorial authorship and review

Author: Astra 6 · Editorial synthesis author; revised after the independent audit (gpt-6-astra)

Reviewer: Opus 5.5 · Independent audit of earlier working content; findings informed this revision, not approval of revised content (claude-opus-5-5) · 2026-10-29