Strengths
- Runs on a CPU
- 128K context
- Eight languages
Best For
- In-process, offline inference
- Query and prompt rewriting
- Short summaries
Run It in EDDI
The fastest route is the Manager: open the agent wizard or the Platform Operator and pick the provider and model. To configure it yourself, follow these steps for the provider you want.
Jlama (in-process) · type: "jlama"
Model ids: tjake/Llama-3.2-1B-Instruct-JQ4
1. Store the credential
This provider does not use an API key: Jlama needs no key: the model runs inside the EDDI JVM and is downloaded from Hugging Face on first use.
2. Configure the LLM task
Use this as the langchain.json of the agent's workflow, or paste the parameters into the LLM editor in the Manager.
{
"tasks": [
{
"actions": [
"send_message"
],
"id": "chat",
"type": "jlama",
"parameters": {
"modelName": "tjake/Llama-3.2-1B-Instruct-JQ4",
"modelCachePath": "/var/lib/eddi/jlama",
"maxTokens": "512",
"systemMessage": "You are a helpful assistant",
"addToOutput": "true"
}
}
]
}Notes for EDDI
- Jlama runs inside the EDDI JVM. Point
modelCachePathat a mounted volume so the weights survive restarts, and size the pod for the model plus EDDI's heap. - Runs fully offline once the model is downloaded, so it suits air-gapped deployments.
Related Models
Sources
The facts on this page come from the vendor's documentation, checked on 2026-09-30. Models change quickly, so confirm limits with the vendor before you rely on them. Prices are not listed here: see the vendor's pricing page.