Somebody may already have tuned your box.

A sidecar is dasLLAMA's per-box tune manifest: which JIT kernel variant won in each of ~40 families, 23 tuned runtime scalars, and the provenance to prove where it came from. Producing one costs about 12 minutes of quiet machine. dasllama-server picks a matching sidecar up automatically at startup — this page is the manual browse.

sidecars · architectures
engine 0.6.4
a sidecar is valid for one version × box
loading the exchange…

Entries render client-side from /api/sidecars; expanding one fetches the sidecar document itself — kernel winners, race margins and runtime knobs all come from that file, never from this page.

One question, once.

The first start asks once whether to use the exchange — Accept and every later start matches your box automatically, one code path; Decline and the box tunes itself locally. Setting the exchange policy yourself - exchange_* keys in a hand-written config, or the DASLLAMA_EXCHANGE_* environment - skips the question: it IS the answer. Manual download is for air-gapped boxes and for people who want to read the manifest before trusting it.

01verified match → downloaded, validated, applied
02unverified match → never auto-applied; adopt it from the control page, or from the tray while a tune runs
03nothing → the box tunes itself, ~12 min quiet machine, and can share the result back
dasllama-serverfirst start after Accept, untuned box
$ daslang -jit main.das -- --model model.gguf
exchange: scope 'dasllama' is untuned - looking up a sidecar for this box (dasllama version 1)
@sidecar lookup version=1
exchange: applied verified sidecar 6a30d7cfb58e (exact match, 41 kernel families)
@sidecar apply sha=6a30d7cfb58e… verified=1 tier=exact kernels=41
exchange: sidecar applied, restart to apply the winners

The process exits with code 3; the watchdog relaunches it, and the fresh compile stamps the downloaded winners. The @sidecar lines are structured events the watchdog folds into its tray.