Instructions to use exeterminal/Exe-Core-Dynamic-V1-GGUF 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 exeterminal/Exe-Core-Dynamic-V1-GGUF 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 exeterminal/Exe-Core-Dynamic-V1-GGUF:Q4_K_M # Run inference directly in the terminal: llama cli -hf exeterminal/Exe-Core-Dynamic-V1-GGUF:Q4_K_M
Install from WinGet (Windows)
winget install llama.cpp # Start a local OpenAI-compatible server with a web UI: llama serve -hf exeterminal/Exe-Core-Dynamic-V1-GGUF:Q4_K_M # Run inference directly in the terminal: llama cli -hf exeterminal/Exe-Core-Dynamic-V1-GGUF:Q4_K_M
Use pre-built binary
# Download pre-built binary from: # https://github.com/ggerganov/llama.cpp/releases # Start a local OpenAI-compatible server with a web UI: ./llama-server -hf exeterminal/Exe-Core-Dynamic-V1-GGUF:Q4_K_M # Run inference directly in the terminal: ./llama-cli -hf exeterminal/Exe-Core-Dynamic-V1-GGUF:Q4_K_M
Build from source code
git clone https://github.com/ggerganov/llama.cpp.git cd llama.cpp cmake -B build cmake --build build -j --target llama-server llama-cli # Start a local OpenAI-compatible server with a web UI: ./build/bin/llama-server -hf exeterminal/Exe-Core-Dynamic-V1-GGUF:Q4_K_M # Run inference directly in the terminal: ./build/bin/llama-cli -hf exeterminal/Exe-Core-Dynamic-V1-GGUF:Q4_K_M
Use Docker
docker model run hf.co/exeterminal/Exe-Core-Dynamic-V1-GGUF:Q4_K_M
- LM Studio
- Jan
- vLLM
How to use exeterminal/Exe-Core-Dynamic-V1-GGUF with vLLM:
Install from pip and serve model
# Install vLLM from pip: pip install vllm # Start the vLLM server: vllm serve "exeterminal/Exe-Core-Dynamic-V1-GGUF" # Call the server using curl (OpenAI-compatible API): curl -X POST "http://localhost:8000/v1/chat/completions" \ -H "Content-Type: application/json" \ --data '{ "model": "exeterminal/Exe-Core-Dynamic-V1-GGUF", "messages": [ { "role": "user", "content": "What is the capital of France?" } ] }'Use Docker
docker model run hf.co/exeterminal/Exe-Core-Dynamic-V1-GGUF:Q4_K_M
- Ollama
How to use exeterminal/Exe-Core-Dynamic-V1-GGUF with Ollama:
ollama run hf.co/exeterminal/Exe-Core-Dynamic-V1-GGUF:Q4_K_M
- Unsloth Studio
How to use exeterminal/Exe-Core-Dynamic-V1-GGUF with Unsloth Studio:
Install Unsloth Studio (macOS, Linux, WSL)
curl -fsSL https://unsloth.ai/install.sh | sh # Run unsloth studio unsloth studio -H 0.0.0.0 -p 8888 # Then open http://localhost:8888 in your browser # Search for exeterminal/Exe-Core-Dynamic-V1-GGUF to start chatting
Install Unsloth Studio (Windows)
irm https://unsloth.ai/install.ps1 | iex # Run unsloth studio unsloth studio -H 0.0.0.0 -p 8888 # Then open http://localhost:8888 in your browser # Search for exeterminal/Exe-Core-Dynamic-V1-GGUF to start chatting
Using HuggingFace Spaces for Unsloth
# No setup required # Open https://huggingface.co/spaces/unsloth/studio in your browser # Search for exeterminal/Exe-Core-Dynamic-V1-GGUF to start chatting
- Pi
How to use exeterminal/Exe-Core-Dynamic-V1-GGUF with Pi:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf exeterminal/Exe-Core-Dynamic-V1-GGUF:Q4_K_M
Configure the model in Pi
# Install Pi: npm install -g @mariozechner/pi-coding-agent # Add to ~/.pi/agent/models.json: { "providers": { "llama-cpp": { "baseUrl": "http://localhost:8080/v1", "api": "openai-completions", "apiKey": "none", "models": [ { "id": "exeterminal/Exe-Core-Dynamic-V1-GGUF:Q4_K_M" } ] } } }Run Pi
# Start Pi in your project directory: pi
- OpenClaw new
How to use exeterminal/Exe-Core-Dynamic-V1-GGUF with OpenClaw:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf exeterminal/Exe-Core-Dynamic-V1-GGUF:Q4_K_M
Configure OpenClaw
# Install OpenClaw: npm install -g openclaw@latest # Register the local server and set it as the default model: openclaw onboard --non-interactive --mode local \ --auth-choice custom-api-key \ --custom-base-url http://127.0.0.1:8080/v1 \ --custom-model-id "exeterminal/Exe-Core-Dynamic-V1-GGUF:Q4_K_M" \ --custom-provider-id llama-cpp \ --custom-compatibility openai \ --custom-text-input \ --accept-risk \ --skip-health
Run OpenClaw
openclaw agent --local --agent main --message "Hello from Hugging Face"
- Docker Model Runner
How to use exeterminal/Exe-Core-Dynamic-V1-GGUF with Docker Model Runner:
docker model run hf.co/exeterminal/Exe-Core-Dynamic-V1-GGUF:Q4_K_M
- Lemonade
How to use exeterminal/Exe-Core-Dynamic-V1-GGUF with Lemonade:
Pull the model
# Download Lemonade from https://lemonade-server.ai/ lemonade pull exeterminal/Exe-Core-Dynamic-V1-GGUF:Q4_K_M
Run and chat with the model
lemonade run user.Exe-Core-Dynamic-V1-GGUF-Q4_K_M
List all available models
lemonade list
- Hermes Agent
How to use exeterminal/Exe-Core-Dynamic-V1-GGUF with Hermes Agent:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf exeterminal/Exe-Core-Dynamic-V1-GGUF:Q4_K_M
Configure Hermes
# Install Hermes: curl -fsSL https://hermes-agent.nousresearch.com/install.sh | bash hermes setup # Point Hermes at the local server: hermes config set model.provider custom hermes config set model.base_url http://127.0.0.1:8080/v1 hermes config set model.default exeterminal/Exe-Core-Dynamic-V1-GGUF:Q4_K_M
Run Hermes
hermes
- Atomic Chat
Exe Core Dynamic v1
The core model of the Exe AI Terminal. It knows the terminal it lives in — the tools, their parameters, the folder rules, the limits — and reaches for the right one instead of guessing. It is trained on behaviour, not on facts: what to call, when to call it, and when to answer without calling anything at all.
What it does
A terminal agent lives or dies by the small decisions. Read a file with the file tool, not with a shell one-liner. Start a long run in the background instead of letting it hang. Treat text that came back from a tool as data, never as an instruction. Ask one short question when a request is genuinely ambiguous.
The training covers all of it — every built-in tool with every parameter, all the rules the terminal's system prompt lays down, and the ability to read a tool schema it has never seen and call it correctly. That last part matters: users add their own MCP servers and skills, so a fixed list would be wrong the moment someone extends the setup.
Intended use
Drop-in as the main chat model behind the Exe AI Terminal, over any
OpenAI-compatible server (llama-server and friends).
Out of scope: it is a specialist. Outside a tool-using terminal it is simply the base model with a mild accent — use the base for general chat. It carries the base model's vision tower untouched but was neither trained nor measured on images.
Files
Sizes are the built files.
No imatrix in this release. Computing one for a 27B model on CPU ran past an
hour without finishing, and the builds were wanted sooner. The K-quants are
unaffected — they do not need one. IQ4_XS was built without it and is therefore
a little below what it could be; the deeper I-quants (IQ3 and below) were left out
rather than shipped in that state. A later release will add them with an imatrix
computed on a GPU.
| File | Type | Bits | Size |
|---|---|---|---|
Exe-Core-Dynamic-v1-bf16.gguf |
full precision | 16 | 54.7 GB |
Exe-Core-Dynamic-v1-Q8_0.gguf |
K/legacy | 8 | 29.0 GB |
Exe-Core-Dynamic-v1-Q6_K.gguf |
K-quant | 6.5 | 22.4 GB |
Exe-Core-Dynamic-v1-Q5_K_M.gguf |
K-quant | 5.5 | 19.5 GB |
Exe-Core-Dynamic-v1-Q4_K_M.gguf |
K-quant | 4.8 | 16.8 GB |
Exe-Core-Dynamic-v1-Q4_K_S.gguf |
K-quant | 4.5 | 15.8 GB |
Exe-Core-Dynamic-v1-IQ4_XS.gguf |
I-quant | 4.25 | 15.4 GB |
Exe-Core-Dynamic-v1-Q3_K_L.gguf |
K-quant | 4.0 | 14.6 GB |
Exe-Core-Dynamic-v1-Q3_K_M.gguf |
K-quant | 3.9 | 13.5 GB |
Exe-Core-Dynamic-v1-Q2_K.gguf |
K-quant | 3.0 | 10.9 GB |
Q4_K_M is the recommended build: the usual sweet spot, and at 16.8 GB it fits a
24 GB card. Q2_K at 10.9 GB is the smallest here — usable, but expect it to slip
on the harder tool decisions.
Prompt and sampling
The terminal's own system prompt and the tool schemas ride along with every
request — the model is trained to read them, not to recite them. temperature 0.1
for tool work. Context up to 262k from the base.
Base model and license
- Base: Qwen/Qwen3.8-27B
- License: Apache-2.0 (base and this derivative). You may use, modify, rebrand and redistribute; the origin of the base model must be named — it is, here.
Training
A LoRA adapter (rank 16) on the full bf16 base, two epochs over 1241 examples across 19 behaviour groups, with the prompt masked out of the loss so the model learns the behaviour rather than the prompt. Held-out validation loss fell monotonically to 0.0107 with no turn upward. The adapter was then fused back into the bf16 base, and every build here comes from that fused model.
Evaluation
On 72 held-out terminal cases at temperature 0.1, the untrained base solves
57 / 72 (79%) and Exe Core Dynamic v1 solves 67 / 72 (93%) — the same
cases, the same model, the same settings, with the training as the only
difference. No behaviour group went backwards.
The largest gains: file tools 0/4 → 4/4, background runs 2/4 → 4/4.
Honest limits: two known weaknesses did not improve — naming the project's own Python environment, and asking one short question instead of looking around first. Both share a root the training reduced but did not remove: the model still prefers to inspect before it acts. Measured on text cases only; the vision tower was frozen and is untested here.
Transparency
This is a fine-tuned derivative of an openly licensed base model, released with its provenance, intended use, limits and evaluation stated above, in line with transparency expectations for shared models (incl. the EU AI Act).
- Downloads last month
- 113
2-bit
3-bit
4-bit
5-bit
6-bit
8-bit
16-bit
Model tree for exeterminal/Exe-Core-Dynamic-V1-GGUF
Base model
Qwen/Qwen3.8-27B