Skip to content

feat(config): 16k output tokens by default (plan #12); full run 0.539 - #23

Merged
canyang25 merged 2 commits into
ruoshi/feat-act-nudgefrom
ruoshi/feat-max-tokens-16k
Oct 10, 2026
Merged

canyang25 merged 2 commits into
ruoshi/feat-act-nudgefrom
ruoshi/feat-max-tokens-16k

Conversation

@rzhang569

@rzhang569 rzhang569 commented Oct 10, 2026 •

Copy link
Copy Markdown
Collaborator

Stacked on #22 (which is stacked on #21).

LLM_MAX_TOKENS 8192 → 16384, in .env.op and as the code default. Update your own .env.op.local, it still says 8192.

On the 10-task slice with #22's act nudge, 3 trials:

  • passes 19/30 vs 14/30 at 8k (both 16k runs beat both 8k runs: 16, 19 vs 12, 14)
  • cut-off give-ups 3 vs 8; feal-linear-cryptanalysis passed for the first time
  • cost: 46 vs 26 s/turn on average, timeouts 6 vs 2 (largest-eigenval 0/3, all at the 900 s limit)

Full run 2 with both (#22 + this): 0.539, 48/89, up from 0.438 (39/89). Give-ups 25 → 11; timeouts 9 → 20, now the biggest failure. Data in eval/results/full-run-2.csv, details in docs/experiments.md.

rzhang569 and others added 2 commits October 9, 2026 19:51
Plan #12 on top of the act nudge: ruoshi/feat-act-nudge (agent code as at
31e2499) on the 10-task dev slice with LLM_MAX_TOKENS=16384, concurrency 2.
Exported with scripts/export_trials.py.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
With the act nudge, 16k reached 19/30 on the dev slice against 14/30 at
8k, and cut-off give-ups fell from 8 to 3. Turns are slower (46 vs 26 s),
and timeouts rose from 2 to 6.
@canyang25
canyang25 merged commit 7b26050 into ruoshi/feat-act-nudge Oct 10, 2026
1 check passed
@rzhang569 rzhang569 changed the title feat(config): 16k output tokens by default (plan #12) feat(config): 16k output tokens by default (plan #12); full run 0.539 Oct 11, 2026
@rzhang569

Copy link
Copy Markdown
Collaborator Author

This was merged into ruoshi/feat-act-nudge, not main, so the 16k default never reached main. The same change, plus full run 2, is in #24.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants