Jakob Nielsen called it:

By the end of 2027 , AI will complete tasks that take a human two months, doing so in perhaps an hour while consuming roughly $100 worth of compute.

We find out by Dec 31, 2027. 491 days to go

Open

Jakob Nielsen: “By the end of 2027 , AI will complete tasks that take a human two months, doing so in perhaps an hour while consuming roughly $100 worth of compute.

🔒 The test · locked Aug 28, 2026

MET if A published time-horizon evaluation (METR or equivalent methodology) reports a frontier AI model autonomously completing tasks that require at least two months (measured in months of human work time) of human effort at any point, before 2027-12-31 23:59 (UTC).

Settles by documented review of public evidence against these locked criteria; the reviewer is named and the reasoning published.

Test details
Settled byevidence
Window2026-01-13 2027-12-31
TimezoneUTC
Data vintagelatest_revision
Min source tier2
Contract hash0xaa9e39c1…fe4d54
Full resolution criteria

Settled true if, on or before 2027-12-31, a published time-horizon evaluation (METR or equivalent) reports a frontier AI model autonomously completing tasks requiring at least two months of human work time. The 'one hour' and '$100 of compute' details are not part of the test.

Quote verified against the source

Jakob NielsenJakob Nielsen on UX (Substack)Said Jan 13, 2026Added to Thonest Aug 28, 2026Anchored Aug 28, 2026

Added by Thonest from a public source. The person quoted did not submit, approve, or endorse this record; the wording is verified against the source itself.

Read the original on Substack

Reactions are about the record being worth keeping — never about whether the person was right. They are never counted for or against anyone, and never used to rank anything.

Discussion

Loading…

Prediction 1 of Nielsen's 18 predictions for 2026, extending the METR task-horizon doubling trend beyond 2026.

History — append-only

2026-08-28
Recorded · Recorded and locked from the original source

Proof

Evidence hash0x0c8cf6b1…3d2166
Source snapshot
Record fingerprint0x0c8cf6b1a67ad4720693cdd3e8faf426f4347f84384d936657ec88fd873d2166
Proof path
2 hashes from this record to the anchored root
  1. 0x573f0025e6e46aa1efb978a6aeadacfa13061678b786972de4916089c9524962
  2. 0x211d35888d1b2c43a5059b9e3094c0b97e7495b928a1d9603623ba7e63e4396b
Merkle root0x6c45dea111c3dffe94be3b7dc87f416b9b0c5339e5ffc455293baa1dc61a0d01
batch #92 manifest · 4 entries
Registry0x3d74d9e2f0f4c741fc49b34cc119b6db0cef47c0 · entry #96
the contract refuses any batch that doesn’t follow the previous one, and has no function to edit or delete one — including for us
Anchored onchainbase-mainnet · Aug 28, 2026
0xc2efb242…838aba on block explorer
Quote checkThe quote appears verbatim in the response the platform returned.
Platform capture0xc1315072c994af9825d1f72d7ffee4c3022ad6ad19e233d3f52861da6e8b838e
view the canonical capture · the page as served to us, kept verbatim and covered by the evidence hash

✓ The anchored proof cannot be rewritten, and the published record is append-only by default. Everything that happened afterward is in the history above — corrections are appended, never silently edited in.

Verify this record yourself

The check runs in your browser and reads the anchored root straight from a public Base node — not from Thonest. How this works.

Disputes

No disputes have been filed. If something here is wrong — a misquote, a wrong date, a misattributed source — say so and it gets answered on the record. How disputes work.

Related

METRAI task-duration horizon