Skip to main content

vllm-iquest-q1

A vLLM plugin for IQuest-Q1, with recursive MTP, reasoning parsing, and tool calling.

Installation

Install the published package, which pins vLLM 0.30.0:

uv pip install vllm-iquest-q1==0.1.1

For development, install from this repository:

uv pip install .

The CUDA 13.0 image includes the same release wheel and vLLM 0.30.0:

docker pull iquestlabworkspace/vllm-iquest-q1:0.1.1-cu130
# The cu130 tag follows the current CUDA 13.0 release.
docker pull iquestlabworkspace/vllm-iquest-q1:cu130

vLLM loads the plugin automatically. Install it in every worker environment.

Serving

MODEL_ROOT="$(hf download IQuestLab/IQuest-Q1 --quiet)" && \
vllm serve "$MODEL_ROOT" \
  --served-model-name IQuest-Q1 \
  --tensor-parallel-size 8 \
  --reasoning-parser iquest_q1 \
  --enable-auto-tool-choice \
  --tool-call-parser iquest_q1

To enable recursive MTP, use:

MODEL_ROOT="$(hf download IQuestLab/IQuest-Q1 --quiet)" && \
vllm serve "$MODEL_ROOT" \
  --served-model-name IQuest-Q1 \
  --tensor-parallel-size 8 \
  --reasoning-parser iquest_q1 \
  --enable-auto-tool-choice \
  --tool-call-parser iquest_q1 \
  --enable-prefix-caching \
  --speculative-config '{
    "method": "eagle",
    "model": "'"$MODEL_ROOT"'/mtp",
    "num_speculative_tokens": 5,
    "draft_sample_method": "probabilistic",
    "rejection_sample_method": "standard",
    "enforce_eager": false
  }'

For an FP8 KV cache, add --kv-cache-dtype fp8 (or fp8_e4m3). This requires a device and FlashAttention version that support FP8 KV caching in vLLM, such as Hopper with FlashAttention 3 and the default BF16 model dtype. The supported vLLM version uses unit scales when the checkpoint does not provide calibrated scales; it does not accept --calculate-kv-scales. Validate generation quality with your checkpoint and workload. The learned sink key stays in the model dtype, and its attention score uses the dequantized query. Both per-tensor and per-KV-head quantization scales are supported.

Development

.venv/bin/python -m pytest tests -q
uv build --wheel --out-dir dist

Publishing

Build the wheel from a clean release commit, install that wheel in the validation environment, and run the tests and real-model checks before publishing. Attach the tested wheel and its SHA256SUMS file to a GitHub release whose tag matches the package version (v0.1.1). Publishing the release triggers the existing PyPI trusted publisher; the workflow verifies and uploads the attached wheel without rebuilding it.

The Dockerfile reuses the previous CUDA 13.0 runtime by immutable digest. Stage the tested plugin wheel, the upstream vLLM 0.30.0 Linux x86-64 wheel, and its required humming-kernels==0.1.12 x86-64 wheel in dist/. The build verifies their hashes and installs these exact files without downloading or changing the base image's other dependencies. Supply the plugin wheel's SHA-256 and the source commit:

docker buildx build --platform linux/amd64 \
  --provenance=false --sbom=false \
  --build-arg IQUEST_WHEEL_SHA256="$(sha256sum dist/vllm_iquest_q1-0.1.1-py3-none-any.whl | cut -d ' ' -f 1)" \
  --build-arg IQUEST_PLUGIN_COMMIT="$(git rev-parse HEAD)" \
  -t iquestlabworkspace/vllm-iquest-q1:0.1.1-cu130 --push .

Verify the published manifest digest before promoting the release to cu130.

Metadata

Release files for vllm-iquest-q1 0.1.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for vllm-iquest-q1 0.1.1
File Interpreter ABI Platform Actions
vllm_iquest_q1-0.1.1-py3-none-any.whl Python 3 none any Details for vllm_iquest_q1-0.1.1-py3-none-any.whl

Release files / vllm_iquest_q1-0.1.1-py3-none-any.whl

Download URL vllm_iquest_q1-0.1.1-py3-none-any.whl
Size 28.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
142b36b3331915cd1689baa762d78eec518e7eba6dc30ceb6c6199946ca8e159
BLAKE2b-256 checksum
How to use checksums
e568e4c343e42f28f8b4c9e00dd7bd5d33ad8e523ce1a39063eb8219439852de
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.

Transparency log

Security for vllm-iquest-q1 0.1.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 1 file in this release has been uploaded with provenance metadata.

Attestation for vllm_iquest_q1-0.1.1-py3-none-any.whl

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.1.1 This release

1 release file Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page