Setup & example run¶
Build the binary/image, then run context-guru as the eval-containers gateway for a real SWE-bench task driven by Claude Code.
Prerequisites¶
- Go 1.26. A C toolchain is needed only for the
cg_skeletontag used below (tree-sitter), and formake test's race detector — not for the binary itself, which is pure Go and statically linked. bifrost's tokenizer does not use cgo: o200k_base is embedded (internal/tokens/tokens.go). CI asserts the pure-Go build on every PR — natively, for linux/amd64 — in thepuregojob (.github/workflows/ci.yaml), which builds withCGO_ENABLED=0, checks the artifact is statically linked, starts it and probes/healthz. The release workflow asserts it again before publishing, deliberately: a release must not depend on a PR check having run.
Cross-compilation to the other three release targets (linux/arm64, darwin/amd64, darwin/arm64) is
covered by the release build, not by that per-PR job.
- If you do not need skeleton, skip the build entirely and use a
release binary.
- Docker (for the gateway image / eval-containers), and the eval-containers repo.
Build¶
Local binary (from the repo root):
Gateway image:
The image entrypoint is deploy/eval-containers/start, which reads EVAL_MODEL, targets the
upstream, injects the real key, and selects the pipeline. It exposes :4000 with
/openai/v1/chat/completions, /anthropic/v1/messages, /healthz, /stats, /expand.
Quick local smoke test¶
./bin/context-guru-proxy --preset general
# then, from an agent or curl, against http://localhost:4000/anthropic/v1/messages
curl -s localhost:4000/stats | jq # token-weighted savings rollup
Example: SWE-bench + Claude Code through the gateway¶
This uses the committed compose override
deploy/eval-containers/compose.contextguru.yaml,
which swaps the eval-containers gateway for context-guru:local and wires it to an
Anthropic-native upstream (IBM litellm). Model: aws/claude-sonnet-5.
flowchart LR
R[SWE-bench runner<br/>claude-code agent] -->|sk-proxy| G[context-guru:local gateway<br/>:4000 /anthropic]
G -->|real token| U[litellm upstream<br/>claude-sonnet-5]
G -->|/stats| CSV[sweep-results.csv]
G -->|CONTEXT_GURU_DUMP| V[(output volume)]
1. Set env and run one task¶
cd .../eval-containers/containers/benchmarks/swe-bench
export EVAL_TASK_ID=django__django-11820
export EVAL_MODEL=aws/claude-sonnet-5
export EVAL_AGENT=claude-code
export ANTHROPIC_API_BASE=<IBM litellm base URL>
export ANTHROPIC_API_KEY=<litellm token>
export OPENAI_API_KEY=unused OPENAI_API_BASE=http://unused.invalid/v1 # base service marks them required
export CONTEXT_GURU_PRESET=balanced # or `off` for the passthrough baseline
docker compose \
-f compose.yaml \
-f .../lab-context-engineering/deploy/eval-containers/compose.contextguru.yaml \
up --abort-on-container-exit
EVAL_MODEL=<provider>/<model>: the model pins every call (FORCE_MODEL), the provider selects the upstream.- The agent is handed a placeholder
sk-proxy; the gateway injectsANTHROPIC_API_KEYon forward. - Pipeline selection:
CONTEXT_GURU_PIPELINE(comma-separated names) wins if non-empty, elseCONTEXT_GURU_PRESET. UseCONTEXT_GURU_PRESET=offfor the baseline (empty pipeline = passthrough). - Optional:
CONTEXT_GURU_DUMP=/output/cg-dump.jsonlwrites a before→after record per rewritten message to the shared output volume;CG_LOG_LEVEL=debuglogs every component's decision and the gate that declined it.
2. Where results land¶
- Task reward / pass — the runner writes
task/result.json(andagent/result.json) to the composeoutputvolume. - Token savings — the gateway's
/stats: Reportstokens_before/after,saved_tokens,savings_pct(token-weighted), pluswasted_tokens/bouncesand per-component rollups.
3. Sweep many task × config cells¶
deploy/eval-containers/sweep.py automates the matrix
(baseline vs each component alone vs the balanced preset vs competitors) over a task list. It
runs each cell, waits for the runner to exit, and appends reward + wall-clock + /stats savings
to deploy/eval-containers/sweep-results.csv. It is resumable — cells already in the CSV are
skipped.
python3 deploy/eval-containers/sweep.py # built-in 10 tasks × all configs
python3 deploy/eval-containers/sweep.py --only baseline cg-dedup
python3 deploy/eval-containers/sweep.py --one-task django__django-11820
The config selector grammar (CSV config column): cg:off (passthrough), cg:<a,b,c> (pin a
pipeline), cg:preset=<name>, or a competitor label like headroom.
Measuring the effect of one component¶
Run the same task twice — once with the component in the pipeline, once with
CONTEXT_GURU_PRESET=off — and compare reward + /stats. Or per-request, have the agent send
x-context-guru-bypass: true to skip the pipeline for that call.
Credentials note:
sweep.pyreads the litellm base + token from~/.claude/settings.json(env.ANTHROPIC_BASE_URL/env.ANTHROPIC_AUTH_TOKEN).
Troubleshooting
The proxy exits with components: unknown component "skeleton". Build with the
cg_skeleton tag, as in the build command above — make build does not pass it.
The base service refuses to start over missing OpenAI credentials. It marks them required
even on an Anthropic-only run; set OPENAI_API_KEY=unused and
OPENAI_API_BASE=http://unused.invalid/v1.
Every task fails with a connection error. Inside a task container 127.0.0.1 is the
container, not the gateway. Check the address the runner was given.
/stats shows requests but no savings. Either the pipeline is off, or the outputs are
below the components' min_tokens gates. Check components.<name>.gates to see which guard
declined — Measure savings explains the histogram.
A sweep re-runs cells I already have. It resumes from sweep-results.csv; a cell is
skipped only when its row is already there.