Contact
Email us when a number looks wrong, a page breaks, or a source has changed. Each kind of report below lists what helps us check it.
One address for everything:
Do not include secrets
Do not send API keys, access tokens, passwords or personal account details. Do not attach log files; paste only the lines that matter, with anything private removed.
What to report
These are the reports we can act on.
- An estimate or calculation error: the result does not match the checkpoint, quantization, context, or device you used.
- A correction to model or GPU data: a value on the site disagrees with the official source.
- A deployment recipe or runtime problem: a documented setup fails, or it records the wrong runtime facts.
- A website or accessibility issue: a page is broken, unclear, or hard to use with a keyboard or screen reader.
What to include
Pick the list that matches your report.
Estimate or calculation error
- Model or checkpoint, and its revision
- Exact quant and artifact
- Context length and concurrency
- Exact GPU model, count, and VRAM, or unified memory
- Host RAM
- Operating system
- Framework or runtime, and its version
- Steps to reproduce
- Expected result and observed result
- Links to the relevant sources
Model or GPU data correction
- The precise field and the value to change
- A primary source URL, and the revision or date of that source
Deployment recipe or runtime problem
- Model and weight revision
- Quant and weight files
- Hardware topology and memory
- Operating system, driver, and runtime versions
- Context length and concurrency
- Steps to reproduce
- Expected result and observed result
- Links to the sources for the recipe
Website or accessibility issue
- Page URL
- Browser and device
- Steps
- Expected behavior and observed behavior