ouroboros/devtools
Anton Razzhigaev 2e253c4e16 feat(bench/tb): forward OUROBOROS_CONTEXT_MODE into task containers
The installed-agent adapter assembles the in-container env from an explicit
whitelist; OUROBOROS_CONTEXT_MODE was not on it, so context-ablation runs
(context_mode=low) silently ran at the default "max". Forward the key
(env-first, host settings fallback) like the other model/effort slots.
No behavior change when the variable is unset.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-19 03:32:28 +00:00
..
benchmarks feat(bench/tb): forward OUROBOROS_CONTEXT_MODE into task containers 2026-07-19 03:32:28 +00:00
__init__.py feat(devtools-benchmarks): add official benchmark harnesses and workspace executor 2026-06-06 12:03:30 +03:00
README.md feat(devtools-benchmarks): add official benchmark harnesses and workspace executor 2026-06-06 12:03:30 +03:00

Ouroboros Devtools

devtools/ contains operator-side and benchmark support code that should be versioned with Ouroboros without becoming part of the runtime core.

Rules:

  • Generated logs, datasets, run outputs, Docker layers, and secrets do not live here.
  • Default benchmark outputs go under /Users/anton/Ouroboros/bench_runs/.
  • Runtime modules must not import devtools.
  • This is not an immune-system bypass: touched files are reviewed normally.
  • Promote code out of devtools only through a separate reviewed runtime plan.