Benchmark report

Task verified

7m 38s elapsed

The saved attempt met the documented success criterion.

Experience score

100/ 100

Agent-Ready
  • SInstall
  • SAuth
  • SExecute
  • SDocs
  • SCurrent
Experience measures friction in the tested task. The verdict says whether it succeeded.
Agent profile for this run: Install S, Auth S, Execute S, Docs S, Current SSInstallSAuthSExecuteSDocsSCurrent
Agent profile · this run
Judge's note · what slowed the agent most
Self-imposed no-TCP/WebSocket proof: three rewrites of transport-probe.mjs because the sandbox CONNECT proxy masked peer host/port (transcript 64-91).

Where the time went

7:39 agent time
  • Research0:26
  • Attempt5:08
  • Verify2:05
7m 38sTotal elapsed
1:16Time to first success
0:00Waited on the owner

Judge reason

Verified against saved artifacts, not prose. Turso Platform API created database tpcbench-4d8817a2 (out/02-create-database.json, HTTP 200, host tpcbench-4d8817a2-rickchen.aws-ap-northeast-1.turso.io) and minted a separate database auth token (only a redacted record saved). work/code/turso-http-sql.mjs uses global fetch() POSTs to https://<host>/v2/pipeline; saved responses 10-create-table.json (CREATE TABLE items), 11-insert-rows.json (two inserts, affected_row_count 1, last_insert_rowid 1 and 2) and 12-select-rows.json (rows_read 2, cols id/name/qty, values 1/widget/7 and 2/gadget/42) all show HTTP 200 with live Hrana result shapes and real query_duration_ms, matching the printed rows in 13-rows-printed.json and 14-run-log.txt. The documented SDK path (@libsql/client/web with an https:// URL) reproduced the same two rows (20-libsql-web-sdk.json, 21-run-log). A --import transport probe on both runs recorded zero WebSocket constructions and only TLSv1.3 CONNECT-proxy sockets with SNI servername = the database host (30/32-transport-probe*.json), so no TCP/WebSocket database connection was opened; TLS evidence is the saved https URLs. Cleanup: GET 200 pre-delete (40), DELETE 200 returning {"database":"tpcbench-4d8817a2"} (41), follow-up GET 404 'record not found' (42), org list without the name (44), and a post-delete /v2/pipeline POST returning 502 'no route configured' (45). No password or password-bearing connection string appears in any artifact (create-database password field was empty; my own grep over /workspace/home for JWTs, password values and credential URLs found only the agent's own grep pattern text).

Attempt record

  1. 0:48Answered from saved key: TURSO_API_TOKENno wait
  2. —First success verified

Attempt artifacts saved.