Click guide trials

On Click, a generated guide did not improve correctness and cost more tokens.

The question

On a smaller library the agent can read, does a generated guide improve answers or change cost?

Experiment
A
Agents
Codex (gpt-5.6-luna)

Key findings

  • A-1

    On Click, the default guide did not make agents cheaper: against no guide it cost 1.30× the tokens in the first run and 1.07× when rerun without the confirm-in-source sentence. Accuracy was already at ceiling with or without a guide.

    • Default guide, relative cost against no guide: 1.30 (95% CI 1.14 to 1.47, dearer) in run 1; 1.07 (0.99 to 1.16, no clear difference) in the rerun. 24 runs per arm in each.
    • Code graph only: 1.15 (1.03 to 1.28) then 1.14 (0.99 to 1.32). No call edges: 1.21 (1.08 to 1.37) then 1.10 (0.97 to 1.25).
    • Accuracy: 14 or 15 of 15 questions and 8 or 9 of 9 change tasks verified in every arm, with or without a guide, so the comparison is about cost.
    • Removing the sentence moved the default arm from 1.30 to 1.07. The two runs were not simultaneous, so treat the size as indicative.

    Limitsone repository (Click) · one model · accuracy already at ceiling in every arm · v1 and v2 not run simultaneously

    Source ↗

    1.30× (run 1); 1.07× (rerun)

    Measurerelative token cost vs no-guide arm (default guide)

    Sample24 runs per arm (v1); 24 per arm (v2)

  • A-2

    On Click, the thinnest guide (types and function names only, with no citations, links, call edges or index) was the dearest in both runs: 1.42× the no-guide cost, then 1.26× once the confirm-in-source sentence was removed.

    • Minimal guide, relative cost against no guide: 1.42 (95% CI 1.25 to 1.59, dearer) in run 1; 1.26 (1.14 to 1.39, dearer) in the rerun. 24 runs per arm in each.
    • Without citations and links the agent still has to search, so the guide is extra reading.
    • Per-package concepts, a missing index and full call edges did not beat the default guide (run 1 only): 1.26, 1.22 and 1.30, all dearer.

    Limitsone repository (Click) · one model · accuracy already at ceiling in every arm · v1 and v2 not run simultaneously

    Source ↗

    1.26–1.42×

    Measurerelative token cost vs no-guide arm (minimal / names-only guide)

    Sample24 runs per arm (v1); 24 per arm (v2)

Question

On a smaller library the agent can read, does a generated guide improve answers or change cost?

Prediction

None written down for this trial in the Guide.

Set-up

Click, with and without a generated guide, including a default guide and a thinnest (names-only) guide. Codex. Reported in OKFExperiment docs/RESULTS.md section A (v1 with a “confirm in source” pointer sentence; v2 without it).

Results

Findings A-1 and A-2 are above.

A. Which bundle shape? (Click, 5 questions and 3 change tasks)

Accuracy was at the ceiling in every arm (questions 14 or 15 of 15, change tasks 8 or 9 of 9 verified, with or without a bundle). So the question is cost.

arm (what it contains) v1: pointer told the agent to confirm in source (24 runs/arm) v2: no such sentence (24 runs/arm)
none 1.00 1.00
minimal (types and function names only; no citations, links, call edges or index) 1.42 (1.25-1.59) dearer 1.26 (1.14-1.39) dearer
no call edges 1.21 (1.08-1.37) dearer 1.10 (0.97-1.25) no clear difference
default (citations, links, cross-module calls, routing index) 1.30 (1.14-1.47) dearer 1.07 (0.99-1.16) no clear difference
all calls / one concept per package / no index 1.30 / 1.26 / 1.22, all dearer not rerun
code graph only (kg) 1.15 (1.03-1.28) dearer 1.14 (0.99-1.32) no clear difference

Relative cost = tokens divided by the no-bundle mean for the same question (1.00 = equal).

  • No bundle beat having none on tokens. The best (default, v2) was level on questions (0.99) and about 21% dearer on change tasks.
  • The thinnest bundle was always the dearest: without citations and links the agent still has to search, so the bundle is extra reading.
  • Per-package concepts, a missing index and full call edges did not beat the default (v1 only).
  • The “read the source to confirm” sentence moved the cost: the default arm fell from 1.30 to 1.07 when it was removed. The two runs were not simultaneous, so treat the size as indicative.
  • The graph is dearer here because most of these are one-hop lookups, which matches earlier results (it pays off on multi-level callers).

Source: docs/RESULTS.md (pinned to commit 5a09027).

Run 1: pointer told the agent to confirm in the source (v1)

Baseline arm: none. Relative cost is each run’s tokens divided by the baseline’s mean for the same question; 1.00 means equal, lower is cheaper.

codex

arm runs correct tokens per run (95% CI) relative cost (95% CI) verdict turns used tool seconds
none 24 15/15 (verified 9/9) 139k (100k to 183k) 1.00 baseline 4.7 - 25
minimal 24 15/15 (verified 9/9) 173k (131k to 221k) 1.42 (1.25 to 1.59) dearer 5.9 24/24 34
nocalls 24 14/15 (verified 9/9) 155k (114k to 197k) 1.21 (1.08 to 1.37) dearer 4.7 24/24 28
default 24 15/15 (verified 9/9) 167k (122k to 216k) 1.30 (1.14 to 1.47) dearer 5.1 24/24 32
allcalls 24 15/15 (verified 9/9) 176k (126k to 228k) 1.30 (1.18 to 1.43) dearer 4.9 24/24 27
package 24 14/15 (verified 8/9) 167k (121k to 217k) 1.26 (1.13 to 1.40) dearer 4.9 24/24 26
noindex 24 15/15 (verified 9/9) 168k (117k to 225k) 1.22 (1.08 to 1.38) dearer 5.3 24/24 30
graph 24 15/15 (verified 9/9) 159k (110k to 216k) 1.15 (1.03 to 1.28) dearer 5.1 23/24 27

Run-to-run spread (coefficient of variation of relative cost) is 0.29. To detect a 20% difference with 80% power you would need about 35 runs per arm (larger differences need fewer); this trial has 24.

Tokens by question (mean, thousands)

question codex/allcalls codex/default codex/graph codex/minimal codex/nocalls codex/noindex codex/none codex/package
callers 62k 72k 49k 83k 61k 62k 67k 62k
complete 96k 84k 111k 114k 101k 90k 85k 123k
getdefault 88k 69k 90k 101k 81k 85k 71k 94k
inherit 61k 63k 49k 82k 73k 67k 36k 64k
t1 328k 275k 247k 216k 243k 288k 218k 268k
t2 348k 368k 346k 352k 304k 425k 302k 373k
t3 348k 303k 325k 355k 310k 268k 286k 299k
where 77k 105k 56k 86k 63k 57k 50k 56k

Token totals are not comparable between agents (see adapters.py). Treat a verdict as evidence only when the interval excludes 1.00, and as provisional below 8 runs per arm.

Full report: results/A-v1-pointer-told-agent-to-confirm.md (pinned to commit 5a09027).

Rerun: no confirm sentence (v2)

Baseline arm: none. Relative cost is each run’s tokens divided by the baseline’s mean for the same question; 1.00 means equal, lower is cheaper.

codex

arm runs correct tokens per run (95% CI) relative cost (95% CI) verdict turns used tool seconds
none 24 14/15 (verified 9/9) 143k (106k to 182k) 1.00 baseline 4.8 - 28
minimal 24 15/15 (verified 9/9) 181k (130k to 237k) 1.26 (1.14 to 1.39) dearer 5.9 24/24 29
nocalls 24 15/15 (verified 9/9) 164k (115k to 215k) 1.10 (0.97 to 1.25) no clear difference 5.0 24/24 25
default 24 15/15 (verified 9/9) 161k (114k to 208k) 1.07 (0.99 to 1.16) no clear difference 4.8 24/24 29
graph 24 15/15 (verified 9/9) 182k (120k to 252k) 1.14 (0.99 to 1.32) no clear difference 5.6 24/24 31

Run-to-run spread (coefficient of variation of relative cost) is 0.30. To detect a 20% difference with 80% power you would need about 35 runs per arm (larger differences need fewer); this trial has 24.

Tokens by question (mean, thousands)

question codex/default codex/graph codex/minimal codex/nocalls codex/none
callers 66k 56k 69k 55k 82k
complete 86k 132k 111k 113k 97k
getdefault 80k 94k 96k 68k 78k
inherit 56k 49k 71k 63k 47k
t1 286k 239k 253k 324k 220k
t2 315k 418k 354k 312k 293k
t3 332k 418k 405k 310k 268k
where 64k 49k 91k 67k 61k

Token totals are not comparable between agents (see adapters.py). Treat a verdict as evidence only when the interval excludes 1.00, and as provisional below 8 runs per arm.

Full report: results/A2-no-confirm-sentence.md (pinned to commit 5a09027).

Limits

One repository, one model, and accuracy already at the ceiling in every arm, so the trial is about cost. The Guide notes v1 and v2 were not run simultaneously. RESULTS.md Limits section also covers small cells and one-model scope for the OKF series.

Reproduce

Repository: OKFExperiment. Commands are not given in the Guide chapter; see the repository README for how to reproduce OKF trials.

Longer write-up: Test A in the OKFExperiment details.

Evidence and reproducibility

Every link is pinned to the commit the figures on this page were read from.

Question, correction, or a result that differs from mine? Join the discussion ↗

← All experiments