Instructions to use anilsuthar2004/qwen-bot with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Notebooks
- Google Colab
- Kaggle
- Local Apps Settings
- llama.cpp
How to use anilsuthar2004/qwen-bot with llama.cpp:
Install (macOS, Linux)
curl -LsSf https://llama.app/install.sh | sh # Start a local OpenAI-compatible server with a web UI: llama serve -hf anilsuthar2004/qwen-bot # Run inference directly in the terminal: llama cli -hf anilsuthar2004/qwen-bot
Install from WinGet (Windows)
winget install llama.cpp # Start a local OpenAI-compatible server with a web UI: llama serve -hf anilsuthar2004/qwen-bot # Run inference directly in the terminal: llama cli -hf anilsuthar2004/qwen-bot
Build from source code
git clone https://github.com/ggml-org/llama.cpp.git cd llama.cpp cmake -B build cmake --build build -j --target llama-app # Start a local OpenAI-compatible server with a web UI: ./build/bin/llama serve -hf anilsuthar2004/qwen-bot # Run inference directly in the terminal: ./build/bin/llama cli -hf anilsuthar2004/qwen-bot
Use Docker
docker model run hf.co/anilsuthar2004/qwen-bot
- Llama new
- LM Studio
- Jan
- Ollama
How to use anilsuthar2004/qwen-bot with Ollama:
ollama run hf.co/anilsuthar2004/qwen-bot
- Unsloth Desktop
- Docker Model Runner
How to use anilsuthar2004/qwen-bot with Docker Model Runner:
docker model run hf.co/anilsuthar2004/qwen-bot
- Lemonade
How to use anilsuthar2004/qwen-bot with Lemonade:
Pull the model
# Download Lemonade from https://lemonade-server.ai/ lemonade pull anilsuthar2004/qwen-bot
Run and chat with the model
lemonade run user.qwen-bot-{{QUANT_TAG}}List all available models
lemonade list
- Atomic Chat
File size: 1,888 Bytes
572ef52 | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 | Take a look at the changelog between the current version and the previous version - use the `./scripts/make-release-desc.sh [current-version]` to obtain it. Write a summary of the change log in a few sections: ``` ## Overview [a single paragraph overview of all changes] ### Highlights (if applicable) [go through all Pull Requests and write short summaries of those that have the "highlight" label] ### API changes (if applicable) [summarize any API changes to `/include/*`, `/tools/mtmd/mtmd.h` and `/tools/server`] ### New models (if applicable) [summarize new models added to the `src/models/` directory] ### Core changes (if applicable) [summarize the changes to `/src/*` ### Multi-modality changes (if applicable) [summarize the changes to `/tools/mtmd/`] ### Server changes (if applicable) [summarize the changes to `/tools/server/`] ### UI changes (if applicable) [summarize the changes to `/tools/ui/`] ### ggml changes (if applicable) [if the version has been updated, link to the respective `ggml` releases on Github, f.ex `https://github.com/ggml-org/ggml/releases/tag/v0.22.0`. for each version bump, lookup the release description and copy the summary here] ``` Guidelines: - All bullet point in the summary should be concise and rarely exceed a single line of 120 characters (excluding PR links) - Avoid repeating `ggml`-specific changes - these should already be covered by the `ggml` release links - Provide PR link for each bullet point where possible - Don't add bullet point to state that there are no API changes in some module - Combine related topics (a full list of commits will be appended independently at end of the summary) - Skip minor-impact notes (e.g. "fix compile warnings", "refactored code", ...) Output just the summary in a markdown block, without any extra text. Save it to a local text file called `release-notes-vX.Y.Z.txt`. |