Instructions to use WeiboAI/VibeThinker-1.5B with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Libraries
- Transformers
How to use WeiboAI/VibeThinker-1.5B with Transformers:
# Use a pipeline as a high-level helper from transformers import pipeline pipe = pipeline("text-generation", model="WeiboAI/VibeThinker-1.5B") messages = [ {"role": "user", "content": "Who are you?"}, ] pipe(messages)# pip install -U transformers accelerate # Load model directly from transformers import AutoTokenizer, AutoModelForCausalLM tokenizer = AutoTokenizer.from_pretrained("WeiboAI/VibeThinker-1.5B") model = AutoModelForCausalLM.from_pretrained("WeiboAI/VibeThinker-1.5B", device_map="auto") messages = [ {"role": "user", "content": "Who are you?"}, ] inputs = tokenizer.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=256) print(tokenizer.decode(outputs[0][inputs["input_ids"].shape[-1]:])) - Inference
- Notebooks
- Google Colab
- Kaggle
- Local Apps Settings
- vLLM
How to use WeiboAI/VibeThinker-1.5B with vLLM:
Install from pip and serve model
# Install vLLM from pip: pip install vllm # Start the vLLM server: vllm serve "WeiboAI/VibeThinker-1.5B" # Call the server using curl (OpenAI-compatible API): curl -X POST "http://localhost:8000/v1/chat/completions" \ -H "Content-Type: application/json" \ --data '{ "model": "WeiboAI/VibeThinker-1.5B", "messages": [ { "role": "user", "content": "What is the capital of France?" } ] }'Use Docker
docker model run hf.co/WeiboAI/VibeThinker-1.5B
- SGLang
How to use WeiboAI/VibeThinker-1.5B 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 "WeiboAI/VibeThinker-1.5B" \ --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": "WeiboAI/VibeThinker-1.5B", "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 "WeiboAI/VibeThinker-1.5B" \ --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": "WeiboAI/VibeThinker-1.5B", "messages": [ { "role": "user", "content": "What is the capital of France?" } ] }' - Docker Model Runner
How to use WeiboAI/VibeThinker-1.5B with Docker Model Runner:
docker model run hf.co/WeiboAI/VibeThinker-1.5B
VibeThinker 1.5B: proposal for bounded local-serving and reasoning-output documentation
Proposing a community Mac-serving note for VibeThinker-1.5B that makes output budgeting and reasoning completion explicit.
Rapid-MLX has a VibeThinker family route and reasoning handling, but your card recommends allowing a substantial output budget. A short successful load or arithmetic response is not sufficient evidence for that configuration. The example should record the actual budget, distinguish a complete final answer from truncation, and test streamed reasoning separation.
The 3B catalog entry is a separate checkpoint and should not inherit a 1.5B test result. Function/XML behavior also needs verification against the selected artifact rather than assuming a generic Qwen parser. The linked implementation and protocol tests provide a starting point for a narrowly scoped community deployment example.
Concrete catalog entry: vibethinker-1.5b-4bit β mlx-community/VibeThinker-1.5B-mlx-4bit@2c092d732009cb3a2dd4871456c0f1c4e3c0ccec. This is a conversion/distribution artifact; it is not presented as an official upstream release.
Source references (fixed Rapid commit): catalog, family configuration, function/XML tests.
Verification status: this proposal is based on reading the catalog, implementation and the linked documentation/tests. No fresh model inference or test-suite run was performed for this submission; source tests are not an end-to-end qualification. It requests a community documentation scope, not an official endorsement or a performance listing.
Disclosure: I maintain Rapid-MLX. Prepared with AI assistance under my direction. Anonymous usage-metadata telemetry is enabled by default; DO_NOT_TRACK=1 disables it. The original model and conversion terms continue to apply.