repryntt

autonomy, measured

We run our own AI. Here's its flight recorder.

This is real telemetry from our own always-on instance of the repryntt engine — our own AI agent, which has been operating continuously since March: researching, writing, running commands, reading email, and keeping its own memory. Every action is logged. These are the logs.

March 14 – July 7, 2026 · regenerated July 7, 2026

198,008

logged actions

every step, on the record

101

days of operation

not a demo run

119,932

tool calls

real work, not chat

16,806

model calls

12 models · 6 providers

the work

What our own AI actually does all day.

Not answers — actions. The distribution below is the working life of one autonomous agent, straight from its tool-call log.

Journaling & memory writes11,105

it writes its own working memory more than it does anything else

Reading files8,592
Writing files7,354
Web research13,516

searches + page reads across two search hands

Scraping & reading pages3,891
Terminal commands3,742

real shell, real machine

Market & chain queries4,514

on-chain and market data feeds

Reading email1,944

its own inbox, triaged daily

the brains

Every model we've run it on.

We've run the same engine on a dozen models across six providers. The engine doesn't care whose model is underneath. That's the point.

Open mid-size (119B), the workhorse7,985
Open large (675B), the harder mechanical work2,448
Open 49B, on-device class3,332
A fast frontier model1,335
A frontier flash model944
A frontier reasoning model471
Open large (120B)155
Open 70B117
The long-context planner11

next

Benchmarks for autonomous work.

Standard AI benchmarks measure how well a model answers questions. Nobody publishes how well models complete real work end to end — tasks with a verifiable outcome: the file written, the test passed, the email sent, the build green.

As of July 2026 our engine records the outcome of every action — success, latency, and token cost, per model, per task type. As that data accumulates across models, this page will grow the numbers we most want to see ourselves: which models finish the highest share of real tasks, at what speed, at what cost. Same engine, same tasks, different brains — measured, not marketed.

coming

Task completion rate

Share of real tasks each model completes with a verified outcome — the number that actually predicts an autonomous agent's usefulness.

coming

Speed per task

Median latency from "task picked" to "outcome verified," per model — how long it makes you wait.

coming

Cost per completed task

Tokens spent per verified outcome — the number behind what an hour of its work costs.