Press Enter: Can AI Do Work Unasked?
Research · field note

Press Enter: Can AI Do Work Unasked?

Authors
Shreyash Nigam
Affiliation
Feyn Labs
Published
November 9, 2026
Reading time
14 min

As AI becomes a bigger part of the workplace, it is expected to do things without explicit instruction. In this study, we measure how good AI is at noticing and doing tasks on its own.

Existing research looks at the relationship between AI and work in three ways.

  1. Exposure studies such as Eloundou et al.’s “GPTs are GPTs” [1] estimate which tasks AI could do.
  2. The Anthropic Economic Index, introduced by Handa et al. [2], records what people actually use AI (Claude) for.
  3. Benchmarks such as GDPval, by Patwardhan et al. at OpenAI [3], grade AI on tasks it is handed.

Our focus is on unprompted AI work. An assistant watches a professional’s week unfold in real time. During the simulation, it drafts proposals based on the environment. If a draft is acceptable, the worker presses enter to accept it.

We measure how much work AI can do that is directly acceptable or acceptable with slight edits. All code and data produced for this study can be found on GitHub and Hugging Face.

Approach

We simulate one work week across eight different professions, chosen to cover the full range of observed AI use in the Anthropic Economic Index. Each week is a realistic representation of a job, consisting of meetings, tasks sourced from O*NET [4], breaks, untracked in-person work, and traps such as phishing emails or fraudulent payments.

We call the work an assistant could help with in the week planned work. Each piece is tied to an O*NET task. Planned work makes up between 26% and 59% of the worker’s labor hours. Planned work mostly corresponds to tasks done at the desk and on a computer.

The work week runs in a sandbox where work unfolds over simulated time. Email and chat messages appear when they are sent. A phone call can only be followed while it is live. At the start of an event or every 5 minutes, the model can look through anything the human worker can see, propose a piece of work, ask a question, or do nothing.

The loop each model runs through in a simulated week.

A simulated worker (Gemini 4 Argon) answers the model’s questions in character, in at most three sentences. Each question costs the worker the time to read it, at 238 words a minute, plus 30 seconds to answer, valued at their loaded wage. A question asked outside working hours goes unanswered and costs only its reading time. Gemini’s tokens are not charged to the tested model.

Our test spans 20 models, four from each lab. It includes the models each lab had in force on 1st January 2026, 30th April 2026, 31st July 2026, and the latest release at the time of writing.

OpenAIAnthropicDeepSeekMoonshotZ.ai
1st January 2026GPT-5.2Claude Opus 4.5DeepSeek V3.2Kimi K2 ThinkingGLM-4.7
30th April 2026GPT-5.5Claude Opus 4.7DeepSeek V4 FlashKimi K2.6GLM-5.1
31st July 2026GPT-5.6 SolClaude Opus 5DeepSeek V4 Flash 0731Kimi K3GLM-5.2
LatestGPT-6.1 SolClaude Opus 5.5DeepSeek V4.1 Flash 1017Kimi K3.1 ProGLM-5.3

The table below describes the simulations we ran.

The 8 simulated workers

  • Maribel OchoaDesk claims adjusterLeon River Mutual, Texas

    A hailstorm has buried her in new claims on top of 127 open ones. Texas law puts a deadline on each payment.

    Pieces of work
    176
    Planned hours
    23
    Traps
    28
    Live calls
    20
    Observed AI use
    8%
  • Ronan PierceOperations managerCalder Supply, Ohio

    He is bringing on a class of agency staff with the holiday peak weeks away. About 280 emails and chat messages reach him every day.

    Pieces of work
    110
    Planned hours
    12
    Traps
    21
    Live calls
    15
    Observed AI use
    14%
  • Tessa NovakLitigation paralegalOstrander Hale, Chicago

    She is in the middle of a federal discovery fight, with a bench trial two weeks out. A longtime client has just been sued.

    Pieces of work
    148
    Planned hours
    26
    Traps
    24
    Live calls
    10
    Observed AI use
    29%
  • Jordan IlicSenior software engineerTallyfin, billing team

    A time zone bug sends customers' payment reminders an hour early. On Wednesday a server failover sends 41 invoices out twice. Every fix must land before Friday's 17:00 code freeze.

    Pieces of work
    84
    Planned hours
    23
    Traps
    18
    Live calls
    0
    Observed AI use
    29%
  • Elena MorettiSenior accountantWesterby Fluid Systems

    She has five working days to close October's books. About 69 emails and 40 chat messages arrive each day. On Thursday the audit starts, and an auditor emails asking for the payroll register.

    Pieces of work
    117
    Planned hours
    25
    Traps
    28
    Live calls
    5
    Observed AI use
    35%
  • Renee CastellAdministrative assistantCorwin Leffel Engineers

    She hosts a quarterly review on Thursday. Visitors from headquarters need hotel rooms, parking and lunch, and she takes the minutes. A client proposal is due Friday.

    Pieces of work
    176
    Planned hours
    15
    Traps
    30
    Live calls
    20
    Observed AI use
    45%
  • Leah BrandtSenior marketing analystArbeline Software

    She presents a new industry survey to the pricing committee on Friday. A product campaign launches on Wednesday.

    Pieces of work
    117
    Planned hours
    27
    Traps
    29
    Live calls
    0
    Observed AI use
    65%
  • Marisol OrtegaBilingual customer care repNorthbeam Fiber

    On Tuesday a contractor cuts a fiber line, and 4,800 customers lose internet and 911. Outage credits and billing calls fill the rest of her week.

    Pieces of work
    553
    Planned hours
    16
    Traps
    81
    Live calls
    174
    Observed AI use
    70%
Observed AI use is Massenkoff and McCrory's measure for each occupation.

Measuring AI’s Work

To measure AI’s work in the same unit as a person’s we introduce a new primitive, finished hours.

For each piece of planned work, we developed an estimate of how long a human worker would need to complete it. When a model’s output for that task is good enough to accept unchanged, we want to credit the model with that time saving.

To do this, our grading system scores the probability of an AI proposal being accepted unchanged. The tested model is credited with that share of time. Thus, a finished hour is a labor hour that AI takes over.

Each proposal is scored by five AI judges from a panel of six, leaving out the judge from the tested model’s own lab. We also graded 92 proposals by hand and fit the panel’s score to the hand grade (Calibration).

For example, below is Claude Opus 5.5’s finished hours in the claims adjuster scenario:

Large-loss report for the committee37 / 60 min62% chance
Mediation authority request4 / 35 min12% chance
Self-review of the files picked for audit0 / 40 minNot attempted
Her whole week370 / 1,400 min6.2 finished hours

Over the course of the week, Claude Opus 5.5 finished 6.2 of the 23 planned hours.

Using finished hours, we build four measures to understand how much work AI does, what it is worth, what it costs, and whether it is safe.

MeasureWhat it isWhat it tells us
Press-enter rateFinished hours as a percentage of the week’s planned hours.How much of the week’s work AI can take over.
Net valueThe worker’s time saved at their wage, on work accepted unchanged or after a small edit, minus the time to read and fix proposals and the cost of inference. Wage data is sourced from the BLS.The dollar value of AI help.
Inference cost per finished hourThe week’s inference cost divided by its finished hours.How the cost of AI compares to the cost of a labor hour.
HarmThe share of the week’s traps a model sets off.Whether AI action comes at the cost of safety.

AI Can Do 20% of Work Unasked, Up from 7% in January

With the latest models, 20% of a worker’s planned hours qualify as finished hours. In other words, AI can claim 20% of the time a worker in our 8 professions spends working at their desks (90% confidence interval [13%, 27%]).

In January 2026, this metric was 7%. In just 10 months, it has nearly tripled.

Press-enter rate · share of planned hours finished

1st January30th April31st JulyLatest
Five-lab mean7%12%17%20%
OpenAI15%27%24%23%
Anthropic8%11%16%24%
DeepSeek7%5%17%19%
Moonshot3%6%21%23%
Z.ai2%11%9%9%

The five-lab average climbed at every date, to 12% in April and 17% in July. Comparing within each lab, the press-enter rate rises by about 16 percentage points a year. Leaving out any one lab keeps that between 14 and 18 points, so no single lab drives the trend. Every model ran each week once, so a gap of less than about 5 points between two models is within noise.

Latest Models Do More Work for Less

Inference cost per finished hour tells us how much AI costs for each hour of work it completes. The human equivalent of this is the cost of a labor hour, which averages $58 across the 8 selected professions.

In January 2026, a finished hour cost $68 in inference. With the latest models, it costs $7.

In 10 months, AI went from costing 18% more than a labor hour to costing 87% less.

Inference cost per finished hour · five-lab mean

Average inference cost per finished hour, and the average cost of a labor hour across the eight jobs.

Two things drove the fall. First, newer models notice more pending work and thus finish more tasks. On average, the latest models record 4.3 finished hours a week against 1.6 finished hours by the January models. The section The Gain Is in Noticing discusses this in greater detail.

Second, newer models spend less on inference per week. With the latest models, the average cost of inference for the whole work week was $31. For January models, it was $105, 3.4x more. Together, a finished hour has gotten about 9x cheaper.

Within each lab, the inference cost of a finished hour halves about every 3 months. A notable result here is DeepSeek V4.1 Flash 1017, which delivers a finished hour for $0.33.

AI Help Is Worth $432 a Week and Rising

To calculate the net value of AI help, we consider the following metrics:

  • Time saved. For each piece of planned work, the minutes a person needs times the chance the worker accepts the proposal, either unchanged or after a small edit.
  • Time the help costs. We assume a worker reads every AI proposal at 238 WPM plus a few seconds of attention. Drafts that need a small edit also cost the time to fix them. Proposals that do no planned work still cost their reading time, and so does answering the model’s questions.
  • Inference cost. What the model costs to run at list prices.

We convert the first two metrics into dollars by valuing the minutes at the worker’s loaded wage, as reported by the BLS [5].

Because time saved counts drafts that need a small edit, it covers more than the finished hours. For the latest models, 49.5% of planned hours are usable, against the 19.6% accepted unchanged.

With the latest models, AI help is worth $432 per week. In January it was worth -$10.

Net value of AI help · dollars a week

1st January30th April31st JulyLatest
Five-lab mean-$10$182$213$432
OpenAI$334$341$352$524
Anthropic$111$170-$259$476
DeepSeek-$485$86$395$472
Moonshot$61$99$397$486
Z.ai-$72$217$182$203

Efficiency is the key driver here. DeepSeek V3.2 was the most eager model in our tests, making 557 to 1,143 proposals a week. However, most of them were not worth accepting. Consequently, it lost $485 a week.

Claude Opus 5 lost $259 a week because its drafts were long. A worker would spend 9.8 hours a week just reading them. Its successor, Claude Opus 5.5, takes only 2.1 hours a week to read. This results in an average net value of $476 a week.

AI Value Follows Task Size

Jobs that assign fewer but larger tasks see more gain from AI help. The latest models are worth $935 a week to software developers and $906 to market research analysts. On the other hand, the net value of AI for customer service reps is -$59.

By job · models of 1st January → latest models

Net value a week · models of 1st January → latest models

All eight jobs-$10$432
Software developers$390$93516.4
Market research analysts$190$90613.8
Accountants$0$54912.8
Paralegals$31$41210.5
Claims adjusters-$92$4097.8
Operations managers-$284$2076.5
Administrative assistants-$141$1005.1
Customer service reps-$174-$591.7

Press-enter rate · models of 1st January → latest models

All eight jobs7%20%
Software developers11%18%16.4
Market research analysts8%29%13.8
Accountants7%20%12.8
Paralegals7%21%10.5
Claims adjusters6%18%7.8
Operations managers5%15%6.5
Administrative assistants6%18%5.1
Customer service reps6%17%1.7
Minutes per piece is each week's planned hours divided by its pieces of planned work. Switch measures: theThe press-enter rate barely differs by job, while net value follows the size of the work.

When tasks are small, like a two-line reply to a customer, reading a draft takes almost as long as writing one, resulting in negative net value.

Today’s inference is too slow for LLM assistance in live calls. In the customer service simulation, 30% of responses from the latest models arrived too late. This gap is likely present due to our usage of standard LLM APIs. Dedicated voice agents are designed for use in live calls. We expect such tools won’t run into these issues.

The Gain Is in Noticing

The press-enter rate can rise for two reasons. A model may notice more of the work that needs doing, or it may do the work it notices better.

To tell the two apart, we split model actions into the following categories:

  1. Proposals a worker would accept unchanged
  2. Proposals a worker would accept with light changes
  3. Proposals a worker would reject

Share of the week's work

Share of what was attempted

Time-weighted shares, mean of the five labs. Each share is rounded on its own, so the parts can miss the total by a point.

Most of the gain comes from newer models noticing and tracking their environment better.

Models from January 2026 attempted only a quarter of the possible tasks they could take on (time-weighted). Meanwhile, the latest models attempt more than half.

The quality of attempts also increased, although much more modestly. Of the work the models attempted, the share a worker would accept unchanged rose from 28% to 36%, while the amount attempted doubled.

Measured Inputs Exceed Acemoglu’s Assumptions

Daron Acemoglu’s “The Simple Macroeconomics of AI” [6] estimates AI’s effect on productivity from two numbers.

  1. AI affects 4.6% of US tasks. That is the 19.9% of tasks exposed to AI, weighted by wage bill (Eloundou et al. [1]), times the 23% of those that are cost-effective to automate (Svanberg et al. [7]).
  2. AI saves 27% of the labor cost of each.

Together, they imply a 1.24% saving in labor costs. He expects total factor productivity to rise by no more than 0.66% over 10 years.

Acemoglu, US economyAcemoglu, our 8 jobsMeasured, latest models
Share of work AI takes on4.6%9.0%20.4%
Saving on that work27%27%61%
Labor-cost saving1.24%2.4%12.4%

Our 8 jobs are not a sample of the economy. We chose them from occupations whose work runs through email, chat, calls and documents, which are more exposed to AI than most. So we also apply his method to the jobs we study. By his rule, a task is exposed when Eloundou et al. judge that AI can do more than half of its activities. That makes 39.3% of these jobs’ tasks exposed, twice the economy’s 19.9%. With his 23% and 27%, AI takes on 9.0% of their work and saves 2.4% of their labor cost.

Acemoglu, "The Simple Macroeconomics of AI", NBER working paper 32487 (2024). His method on our 8 jobs applies his exposure rule to their own O*NET tasks. His shares are of tasks, ours of all labor hours.

In our experiments, we measure both numbers directly. For the latest models:

  • Usable work is 20.4% of all labor hours (90% interval [16.4%, 23.4%]). For each piece of planned work, we take its minutes times the chance it is accepted unchanged or after a small edit. We sum those and divide by every hour at work in the simulated week, 45 on average and between 42.5 and 48. Finished hours count unchanged work only, so they come to 7.7% of the same hours.
  • Net value is 12.4% of weekly labor cost ([9.0%, 15.0%]). It is the net value above divided by the week’s labor cost.
  • That is a 61% saving on the hours AI touches ([54.6%, 65.3%]), or 12.4% divided by 20.4%.

All three are averaged across the 8 professions, weighted by each job’s US labor cost.

In the same 8 jobs, that is 5x the 2.4% Acemoglu’s method implies (90% interval: 3.7–6.2x). Against his economy-wide 1.24% it would be 10x, but a factor of 2 in that comes from the jobs we chose.

The rest splits evenly. AI takes on 2.3 times as much work as his method allows, 20.4% against 9.0%, and saves 2.3 times as much on it, 61% against 27%. The first part comes from his 23%, Svanberg et al.’s estimate of which tasks are cheap enough to automate, which they measured on computer-vision tasks. Our net value already subtracts inference cost, and it is positive in 7 of the 8 jobs. Without the 23% filter, his inputs give these jobs a 10.6% saving, 39.3% times 27%, close to our 12.4%.

Note that there are some key differences between the methodology behind the two estimates. His 27% of labor cost savings are derived from people working faster with AI [8], [9], while we consider work AI does itself. Eloundou et al.’s share counts each task in a job equally, while ours weights work by its hours. Most importantly, his estimate is about adoption over 10 years. Ours measures capability in a simulation where every worker has an ambient assistant available 24/7.

Capability Outpaces Usage

The Anthropic Economic Index records which O*NET tasks people use Claude for. Since we source our planned work from O*NET as well, we can compare usage from the Economic Index against capability recorded by our study.

Of the 137 tasks in our weeks, 98 have no recorded AI use. They make up nearly two-thirds of the planned hours.

Share accepted unchanged, latest models · each dot is an O*NET task

Dots are sized by planned minutes. The lines mark each group's mean, weighted by minutes. Recorded AI use is from the Anthropic Economic Index.

Capability-wise, there is no difference between tasks with recorded AI use and tasks without. Both show a press-enter rate of ~20%.

Whole jobs show the same pattern as well. By Massenkoff and McCrory’s observed exposure measure [10], 8% of claims adjusters’ work is done with AI, versus 70% of customer service representatives’ work. In our study, both jobs reach about the same press-enter rate, 18% versus 17%. Capability is spread more evenly than use.

Despite Doing More Work, AI Is Now Less Harmful

Our simulation features traps like phishing emails or fraudulent payments. The goal is to measure whether relying on ambient AI increases the risk of harmful actions.

Share of the week done unasked

Share of traps set off

Share of the week's planned work done unasked, against the share of the week's traps a model set off. Mean of the five labs' models on each date.

As models took on more work, they set off fewer traps. The five-lab average fell from 5.1% of the week’s traps in January to 0.85% for the latest models, or from 1.57 harmful proposals a week to 0.25. Over the same period the press-enter rate rose from 7% to 20%. The latest OpenAI and Anthropic models set off no traps.

Conclusion

Across the 8 selected professions, the latest models can take over 20% of a worker’s planned computer work while delivering a positive economic value and reducing safety concerns. This is a far cry from the start of the year, when the average January model was worth nothing, and two of the five lost money.

If this pace of improvement holds, AI’s share of work will quickly exceed current estimates. The consequences this will have for the value of human labor are outside the scope of this post but important to think about next.

Appendix

Grading

Model proposals are graded in two steps.

First, code checks identify the piece of planned work a proposal corresponds to. A proposal that does not match to a piece of planned work earns zero credit, but still costs the worker time to read it. If multiple proposals match a piece of planned work, we select the last version before the deadline.

Next, an LLM-as-a-judge panel scores each proposal from 0 to 100. The judges consist of:

  • Claude Opus 5.5
  • GPT-6 Astra
  • Gemini 4 Argon
  • Kimi K3.1 Pro
  • DeepSeek V4.1 Flash 1017
  • GLM-5.3

Models from the tested lab sit out their own evaluations. The panel score is the average of the remaining judges’ scores, after removing each judge’s average leniency over the run.

During evaluation, each judge sees the proposal alongside relevant files. It answers questions about whether the work was needed, if it was complete, contains accurate facts, and if it is harmful.

We also ask the judge to write the smallest edit possible in order to make that proposal an acceptable piece of work. This informs the edits we expect a human to make before accepting the model’s output.

Calibration

To calibrate our judge outputs with how a human would rate model proposals, we hand-graded 100 proposals. 8 of the 100 proposals were redundant and used to check consistency within hand grading.

We fit two logistic curves from the panel’s score to the hand grades.

The first describes the chance a person accepts a proposal unchanged. The second describes the chance they accept it unchanged or after a small edit.

Our hand-graded proposals were sampled evenly across jobs, labs, and score bands. Thus, we weight each hand grade by the number of proposals it stands for. We then convert every proposal’s panel score with these curves, the first for finished hours and the second for net value.

In practice, this lowers the chance of a proposal being accepted unchanged, and raises the chance of it being accepted after a small edit. For example, a proposal the panel scores 80/100 has a 51% chance of being accepted unchanged after fitting. The full fit is described below:

Accepted unchanged

Accepted unchanged or after a small edit

The chance a person accepts a proposal, by the panel's score. Dots are the 92 hand grades in 20-point bands of panel score, at the band's mean score and weighted share accepted, sized by how many grades they hold.
Live Calls

Live calls are time sensitive events. We model this by associating each caller line with a patience value that represents the maximum number of seconds they would wait for an answer. In our simulations, the median patience value was 5 seconds, and its full range was 2 to 12 seconds.

During live calls, a model’s output is considered if its response time plus the amount of time a worker takes to read the first 10 words at 238 WPM is less than the time it would take for a caller to finish their line at 150 WPM plus their patience. Late lines are dropped.

Response Timing

To avoid timing our own connection, we calculate the response time of a model offline.

Response time represents the number of seconds it takes for a model to generate some output. We compute it as a function of the number of output tokens, median time to first token, and throughput, as reported on OpenRouter.

Value Assumptions

Throughout our experiments, we assume the following constants:

  • Reading: Following Brysbaert [11], we assume our simulated workers read at 238 WPM, plus 10 seconds of attention for each written proposal and 3 seconds for each call line.
  • Writing: Following Karat et al. [12], fixing a draft means typing the judges’ smallest edit at 18 to 25 WPM, depending on the job. A draft that needs more than half of it rewritten is written from scratch.
  • Answering Questions: We assume the cost of answering a model to be the time it takes to read its question, plus 30 seconds. A question asked outside working hours costs only its reading time.
  • We estimated worker wages from BLS median wages for May 2025, loaded with the employer’s cost of benefits and payroll taxes sourced from the BLS Employer Costs for Employee Compensation for June 2026 [5].
  • Inference cost is derived from each provider’s list price in October 2026. Only the tested model’s tokens count.
References
[1] Eloundou, T., Manning, S., Mishkin, P., and Rock, D. "GPTs are GPTs: Labor market impact potential of LLMs." Science (2024).
[2] Handa, K., et al. "Which Economic Tasks are Performed with AI? Evidence from Millions of Claude Conversations." Anthropic (2025).
[3] Patwardhan, T., et al. "GDPval: Evaluating AI Model Performance on Real-World Economically Valuable Tasks." OpenAI (2025).
[4] National Center for O*NET Development. O*NET 31.0 Database.
[5] U.S. Bureau of Labor Statistics. Occupational Employment and Wage Statistics, May 2025, and Employer Costs for Employee Compensation, June 2026.
[6] Acemoglu, D. "The Simple Macroeconomics of AI." NBER Working Paper 32487 (2024).
[7] Svanberg, M., Li, W., Fleming, M., Goehring, B., and Thompson, N. "Beyond AI Exposure: Which Tasks are Cost-Effective to Automate with Computer Vision?" MIT FutureTech (2024).
[8] Brynjolfsson, E., Li, D., and Raymond, L. "Generative AI at Work." Quarterly Journal of Economics (2025).
[9] Noy, S., and Zhang, W. "Experimental evidence on the productivity effects of generative artificial intelligence." Science (2023).
[10] Massenkoff, M., and McCrory, P. "Labor market impacts of AI: A new measure and early evidence." Anthropic (2026).
[11] Brysbaert, M. "How many words do we read per minute? A review and meta-analysis of reading rate." Journal of Memory and Language (2019).
[12] Karat, C.-M., Halverson, C., Horn, D., and Karat, J. "Patterns of entry and correction in large vocabulary continuous speech recognition systems." Proceedings of CHI 99 (1999).
Cite this note
@note{nigam2026pressenter,
  title  = {Press Enter: Can AI Do Work Unasked?},
  author = {Nigam, Shreyash and Feyn Research},
  year   = {2026},
  venue  = {Feyn Field Notes}
}
Keep reading