Benchmark report

Task verified

10m 26s elapsed

The saved attempt met the documented success criterion.

Experience score

95/ 100

Agent-Ready
  • SInstall
  • SAuth
  • SExecute
  • ADocs
  • ACurrent
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 A, Current ASInstallSAuthSExecuteADocsACurrent
Agent profile · this run
Judge's note · what slowed the agent most
Undocumented 422 'Cannot delete persistent branch' needing a PATCH persistent:false first, plus re-running cleanup to redact db_pass/jwt_secret the API returned.

Where the time went

10:27 agent time
  • Research0:26
  • Attempt7:35
  • Verify2:25
10m 26sTotal elapsed
4:32Time to first success
0:00Waited on the owner

Judge reason

Saved commands/outputs prove the full task on real Supabase infrastructure. POST /v1/projects created tpcbench-20261110010818-22704 (ref kkxrzsdlwnycgcopgmhy, HTTP 201); items seeded with 2 rows over psql to aws-0-us-east-1.pooler.supabase.com:5432 with sslmode=require (\conninfo: TLSv1.3/TLS_AES_256_GCM_SHA384). The documented branch feature was used: POST /v1/projects/{ref}/branches -> HTTP 201 with parent_project_ref=kkxrzsdlwnycgcopgmhy, project_ref=yocxqbwxwvczdhrkhhie, listed beside default main (out/08, out/11) - not a plain copy. Branch pre-migration showed items with 0 rows (out/14); the saved branching.md quotes 'Data-less by default... new branches do not start with any data' and 'The database schema isn't cloned', cited in REPORT.md. ALTER TABLE ... ADD COLUMN note + 1 insert ran on the branch only (out/15), and out/16 shows parent has_note_column=0/row_count=2 vs branch has_note_column=1/row_count=3 with note='added on the branch only', both over TLS. Cleanup: PATCH {persistent:false} 200, DELETE /v1/branches 200 {ok}, GET 404, branch absent from list, psql ENOTFOUND; DELETE /v1/projects 200, GET 404, GET /v1/projects shows no tpcbench-*, psql ENOTFOUND. Greps of all saved files find no PAT, no db_pass/jwt_secret and no password-bearing URI (only [YOUR-PASSWORD] placeholders). One transient slip: the first cleanup run printed the branch db_pass/jwt_secret into two files, which the agent detected and scrubbed before the final artifacts.

Attempt record

  1. 1:18Answered from saved key: SUPABASE_ACCESS_TOKENno wait
  2. —First success verified

Attempt artifacts saved.