Text Generation
Transformers
Safetensors
PEFT
English
Chinese
qwen3_5
image-text-to-text
veriloop
veriloop-coder
code
coding-agent
software-engineering
repository-understanding
tool-use
lora
harness-engineering
evidence-binding
rollback
uncertainty-calibration
long-context
open-weights
conversational
Instructions to use veriloop-lab/veriloop-coder-e1 with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Libraries
- Transformers
How to use veriloop-lab/veriloop-coder-e1 with Transformers:
# Use a pipeline as a high-level helper from transformers import pipeline pipe = pipeline("text-generation", model="veriloop-lab/veriloop-coder-e1") messages = [ { "role": "user", "content": [ {"type": "image", "url": "https://huggingface.co/datasets/huggingface/documentation-images/resolve/main/p-blog/candy.JPG"}, {"type": "text", "text": "What animal is on the candy?"} ] }, ] pipe(text=messages)# Load model directly from transformers import AutoProcessor, AutoModelForImageTextToText processor = AutoProcessor.from_pretrained("veriloop-lab/veriloop-coder-e1") model = AutoModelForImageTextToText.from_pretrained("veriloop-lab/veriloop-coder-e1") messages = [ { "role": "user", "content": [ {"type": "image", "url": "https://huggingface.co/datasets/huggingface/documentation-images/resolve/main/p-blog/candy.JPG"}, {"type": "text", "text": "What animal is on the candy?"} ] }, ] inputs = processor.apply_chat_template( messages, add_generation_prompt=True, tokenize=True, return_dict=True, return_tensors="pt", ).to(model.device) outputs = model.generate(**inputs, max_new_tokens=40) print(processor.decode(outputs[0][inputs["input_ids"].shape[-1]:])) - PEFT
How to use veriloop-lab/veriloop-coder-e1 with PEFT:
Task type is invalid.
- Notebooks
- Google Colab
- Kaggle
- Local Apps
- vLLM
How to use veriloop-lab/veriloop-coder-e1 with vLLM:
Install from pip and serve model
# Install vLLM from pip: pip install vllm # Start the vLLM server: vllm serve "veriloop-lab/veriloop-coder-e1" # Call the server using curl (OpenAI-compatible API): curl -X POST "http://localhost:8000/v1/chat/completions" \ -H "Content-Type: application/json" \ --data '{ "model": "veriloop-lab/veriloop-coder-e1", "messages": [ { "role": "user", "content": "What is the capital of France?" } ] }'Use Docker
docker model run hf.co/veriloop-lab/veriloop-coder-e1
- SGLang
How to use veriloop-lab/veriloop-coder-e1 with SGLang:
Install from pip and serve model
# Install SGLang from pip: pip install sglang # Start the SGLang server: python3 -m sglang.launch_server \ --model-path "veriloop-lab/veriloop-coder-e1" \ --host 0.0.0.0 \ --port 30000 # Call the server using curl (OpenAI-compatible API): curl -X POST "http://localhost:30000/v1/chat/completions" \ -H "Content-Type: application/json" \ --data '{ "model": "veriloop-lab/veriloop-coder-e1", "messages": [ { "role": "user", "content": "What is the capital of France?" } ] }'Use Docker images
docker run --gpus all \ --shm-size 32g \ -p 30000:30000 \ -v ~/.cache/huggingface:/root/.cache/huggingface \ --env "HF_TOKEN=<secret>" \ --ipc=host \ lmsysorg/sglang:latest \ python3 -m sglang.launch_server \ --model-path "veriloop-lab/veriloop-coder-e1" \ --host 0.0.0.0 \ --port 30000 # Call the server using curl (OpenAI-compatible API): curl -X POST "http://localhost:30000/v1/chat/completions" \ -H "Content-Type: application/json" \ --data '{ "model": "veriloop-lab/veriloop-coder-e1", "messages": [ { "role": "user", "content": "What is the capital of France?" } ] }' - Docker Model Runner
How to use veriloop-lab/veriloop-coder-e1 with Docker Model Runner:
docker model run hf.co/veriloop-lab/veriloop-coder-e1
Upload README.md
Browse files
README.md
CHANGED
|
@@ -312,3 +312,12 @@ A concise positioning line for public-facing surfaces can be:
|
|
| 312 |
- Product capability is expected to strengthen as stronger open-weight backbones appear.
|
| 313 |
- Public-facing documentation focuses on capabilities and use cases, not internal implementation details.
|
| 314 |
- Users should evaluate the specific released checkpoint and runtime configuration for their deployment needs.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 312 |
- Product capability is expected to strengthen as stronger open-weight backbones appear.
|
| 313 |
- Public-facing documentation focuses on capabilities and use cases, not internal implementation details.
|
| 314 |
- Users should evaluate the specific released checkpoint and runtime configuration for their deployment needs.
|
| 315 |
+
|
| 316 |
+
## Base Weight Notice
|
| 317 |
+
|
| 318 |
+
This release currently uses **Qwen/Qwen3-Coder-Next** as its underlying open-weight backbone. The upstream Qwen/Qwen3-Coder-Next release is published under the **Apache 2.0** license.
|
| 319 |
+
|
| 320 |
+
VeriLoop Coder E1 should not be understood as a claim over the underlying base weights themselves. Its distinguishing product direction lies in the surrounding **Harness Engineering** layer, including the way the coding system is organized, steered, and delivered for practical software engineering use.
|
| 321 |
+
|
| 322 |
+
As stronger open-weight coding backbones become available, VeriLoop Coder E1 is intended to update its underlying weights accordingly while preserving the same product identity and system direction. The intended outcome is that backbone upgrades, when combined with the VeriLoop harness, can deliver a stronger practical coding system than the raw base model alone.
|
| 323 |
+
|