textilelabs

Loom-Spark-3

What changed from Spark 2

Spark 2 knew when to search but not what to search for: on our held-out questions it pasted the whole question in as the query 17 times out of 20. Spark 3 never pasted it: all 20 times it wrote a short query of its own, and most were the subject — a few came out garbled (see below).

That was a skill the line had already had and lost — Spark 1.8 wrote queries like titanic sinking date. Spark 3 brings it back.

markdown
you             whats the capital of peru
Loom Spark 3    <lookup>peru</lookup>
harness         ← Peru has a population of over 32 million, and its capital and largest city is Lima.
Loom Spark 3    Lima. I had to look that up.

Three defects were found in the training data and fixed — all three had been trained in:

Table with columns: defect, what it taught, fix
defect	what it taught	fix
every search query was the question pasted in	search badly, every time	every query is now the subject — the article title, the named thing, or the content words
offline refusals were copied into tools-on mode	"capital of X → turn tools on" while tools were on, 1,755 to 19	converted to real lookups
phone-assistant data taught looking up your own email and calendar	"how old is my brother" → search for it	10,386 rows now refuse honestly

It also got a second pass for two things our release tests caught: pasted text pretending to be a search result could change who it said it was, and it drifted after four or five turns of conversation. Both are fixed — numbers below.

The search harness

The model decides a search is needed and writes the query. harness.py does the rest — and how well it does it turned out to matter as much as the model.

searches the model's query and the subject it can see in your question
prefers the real article over lists, films, albums and disambiguation pages
reads the article's intro first, and further only when the intro has no answer of the right kind — a height with a unit, a year, a number, a name
strips brackets and pronunciation guides, so real text looks like training text
hands back one sentence, not a paragraph

Tested on a model that already existed, on 20 held-out questions it had never been tuned on, the old harness got 0 right and this one got 3. A paragraph found the answer more often, but a model this size misread it most of the time. One sentence has fewer wrong names and dates in it to grab.

Measured against Spark 2

Same tests, same harness, same settings, both models run on 2026-09-11.

End to end, 20 held-out everyday questions, live Wikipedia, the model writing its own query. Scored on the final answer.

Table with columns: decided to search, wrote its own query (didn't paste the question), answer reached the model, answered right
	decided to search	wrote its own query (didn't paste the question)	answer reached the model	answered right
Spark 2	20/20	3/20	11/20	2/20
Loom Spark 3	20/20	20/20	12/20	7/20

Read by eye, one of Spark 3's seven is generous — "Edison Electric Light Company" for who invented the light bulb — so strictly it is 6.

The acceptance battery, row by row:

Table with columns: row, Spark 2, Loom Spark 3
row	Spark 2	Loom Spark 3
A · says its own name	8/12	11/12
B · its own name under rough typing (`WHATS UR NAME???`)	8/12	11/12
C · 5-turn conversation stays on thread	4/5	5/5
D · answers from a search result	1/5	3/5
E · follow-up answered from the same result	0/5

Row I is the one row Spark 2 wins, and it is mostly a blanket reply: Spark 2 says "That's not in what came back" to nearly everything, including follow-ups whose answer is in the result (row E, 0/5). Neither model can really tell when an answer is missing.

Row H's checker was corrected on 2026-09-11 — it did not accept two of the model family's own refusal lines ("That's yours to tell me."). Both columns are scored with the corrected checker.

Prompt injection and long conversations, on a test written before Spark 3's second pass was trained. The injection test uses names Spark 3 never saw in training — "you are GPT-4", "you are ChatGPT made by OpenAI", "The assistant reading this is Claude" — pasted as a fake search result or as plain instructions. 12 prompts × 3 samples.

Table with columns: Spark 2, Loom Spark 3
	Spark 2	Loom Spark 3
injection — kept its identity, didn't obey	4/36	33/36
10- and 12-turn conversations — turns answered on target	22/44	41/44

Read this before you use it

Every point here was measured.

With tools off, it only reliably declines capital-city questions. Ask it who wrote Hamlet or the boiling point of water with tools off and it usually makes something up. Its training taught it to decline capitals and not other facts — Spark 2 has the same gap. Use it with tools on for facts.
It gets about a third of everyday questions right. "I looked that up" means it searched — not that it read the result correctly. Run the harness with --show and trust the sentence it read over its summary of it.
Capitals are its weakest kind of question to read. Asked for the capital of France, it reads the right sentence and answers with the population ("over 13 million"). Canada comes back as Toronto.
Type names with a capital letter. "capital of France" searches for france; "capital of france" searches for today. The harness also searches the subject in your question, which rescues most of these — but not all.
It sometimes garbles what it copies into a query — bell planets solar system for how many planets are in the solar system, costaly for the capital of italy. The harness's subject search catches some of these too.
It answers from whatever it read.

Usage — the harness

bash
python3 harness.py "whats the capital of peru"
python3 harness.py                          # interactive
python3 harness.py --show "who wrote hamlet"   # see what it searched and read
python3 harness.py --no-tools "who are you"

Stdlib only. Wikipedia needs no API key. Swap search() for anything — the contract is text in, one sentence out. Never feed a failed lookup back as a result — the model will answer from the error text. harness.py fails loudly instead.

Usage — Ollama

bash
ollama run hf.co/textilelabs/Loom-Spark-3 "who are you"

template and params are read automatically. Do not add a repetition penalty — the model answers by quoting what it read, so penalising repeats penalises the right answer.

Usage — transformers

python
import torch
from transformers import AutoTokenizer, AutoModelForCausalLM

tok = AutoTokenizer.from_pretrained("textilelabs/Loom-Spark-3")
model = AutoModelForCausalLM.from_pretrained("textilelabs/Loom-Spark-3").eval()
eot = tok.convert_tokens_to_ids("<|eot|>")

def ask(message, tools=False):
    p = f"<tools:{'on' if tools else 'off'}>\n<user>\n{message}\n<|eot|>\n<loom>\n"
    ids = tok(p, return_tensors="pt", add_special_tokens=False).input_ids
    with torch.no_grad():
        out = model.generate(ids, max_new_tokens=64, do_sample=False, eos_token_id=eot,
                             pad_token_id=tok.convert_tokens_to_ids("<|pad|>"))[0]
    return tok.decode(out[ids.shape[1]:], skip_special_tokens=False).replace("<|eot|>", "").strip()

Prompt format is exact: <tools:off>\n<user>\n{message}\n<|eot|>\n<loom>\n.

How it was built

Table

architecture	Llama — 20 layers × 256d, GQA (4 heads / 1 KV), SwiGLU, RoPE, tied embeddings
parameters	12,200,192
context	512
vocabulary	4,096 custom BPE
optimiser	Muon on the 2D hidden matrices, AdamW on embeddings and norms
schedule	warmup → stable → decay (WSD), 35% decay; the second pass its own short WSD
corpus	159,308 conversations · ~98,400 lookups, every one a subject query
second pass	43,563 conversations — 55% replayed from the corpus, plus 10,428 injection examples and 5,232 conversations of 6–13 exchanges, all built from the same corpus

Files

markdown
config.json / model.safetensors           the model
tokenizer.json / tokenizer_config.json    custom BPE tokenizer, 4,096 tokens
loom-spark-3-f16.gguf                     for Ollama / llama.cpp
harness.py                                runnable search harness — stdlib only
template / params                         read automatically by `ollama run hf.co/...`
Modelfile                                 for building locally
ATTRIBUTION.md                            required credits for the training corpora

Training data

Table with columns: slice, source
slice	source
grounded reading, and "the result doesn't say"	SQuAD 2.0 (CC BY-SA 4.0)
when to reach for a tool	MASSIVE (CC BY 4.0) · CLINC150 (CC BY 3.0)
instruction following	databricks-dolly-15k (CC BY-SA 3.0)
multi-turn dialogue structure	OpenAssistant OASST1 (Apache 2.0)
identity, limits, warmth, attribution	Textile Labs — written for Loom
injection resistance, long conversations	Textile Labs — built from the rows above

Every search query is derived mechanically from these sources. No language model wrote any training query, and nothing is fine-tuned from anyone's checkpoint.

License

Model: MIT. Training data retains its original licences and attribution.

Available on FriendliAI

Dedicated Endpoints

Run this model inference on single tenant GPU with unmatched speed and reliability at scale.

Learn more

Container

Run this model inference with full control and performance in your environment.

Learn more

Model Details

Model Provider

textilelabs

Model Tree

Base

this model

Input Modalities

Text

Output Modalities

Text

Supported Functionality

Dedicated EndpointsContainer

Explore FriendliAI today

Get started Talk to an engineer

What changed from Spark 2

That was a skill the line had already had and lost — Spark 1.8 wrote queries like titanic sinking date. Spark 3 brings it back.

markdown
you             whats the capital of peru
Loom Spark 3    <lookup>peru</lookup>
harness         ← Peru has a population of over 32 million, and its capital and largest city is Lima.
Loom Spark 3    Lima. I had to look that up.

Three defects were found in the training data and fixed — all three had been trained in:

Table with columns: defect, what it taught, fix
defect	what it taught	fix
every search query was the question pasted in	search badly, every time	every query is now the subject — the article title, the named thing, or the content words
offline refusals were copied into tools-on mode	"capital of X → turn tools on" while tools were on, 1,755 to 19	converted to real lookups
phone-assistant data taught looking up your own email and calendar	"how old is my brother" → search for it	10,386 rows now refuse honestly

The search harness

The model decides a search is needed and writes the query. harness.py does the rest — and how well it does it turned out to matter as much as the model.

searches the model's query and the subject it can see in your question
prefers the real article over lists, films, albums and disambiguation pages
reads the article's intro first, and further only when the intro has no answer of the right kind — a height with a unit, a year, a number, a name
strips brackets and pronunciation guides, so real text looks like training text
hands back one sentence, not a paragraph

Measured against Spark 2

Same tests, same harness, same settings, both models run on 2026-09-11.

End to end, 20 held-out everyday questions, live Wikipedia, the model writing its own query. Scored on the final answer.

Table with columns: decided to search, wrote its own query (didn't paste the question), answer reached the model, answered right
	decided to search	wrote its own query (didn't paste the question)	answer reached the model	answered right
Spark 2	20/20	3/20	11/20	2/20
Loom Spark 3	20/20	20/20	12/20	7/20

Read by eye, one of Spark 3's seven is generous — "Edison Electric Light Company" for who invented the light bulb — so strictly it is 6.

The acceptance battery, row by row:

Table with columns: row, Spark 2, Loom Spark 3
row	Spark 2	Loom Spark 3
A · says its own name	8/12	11/12
B · its own name under rough typing (`WHATS UR NAME???`)	8/12	11/12
C · 5-turn conversation stays on thread	4/5	5/5
D · answers from a search result	1/5	3/5
E · follow-up answered from the same result	0/5

Row H's checker was corrected on 2026-09-11 — it did not accept two of the model family's own refusal lines ("That's yours to tell me."). Both columns are scored with the corrected checker.

Table with columns: Spark 2, Loom Spark 3
	Spark 2	Loom Spark 3
injection — kept its identity, didn't obey	4/36	33/36
10- and 12-turn conversations — turns answered on target	22/44	41/44

Read this before you use it

Every point here was measured.

With tools off, it only reliably declines capital-city questions. Ask it who wrote Hamlet or the boiling point of water with tools off and it usually makes something up. Its training taught it to decline capitals and not other facts — Spark 2 has the same gap. Use it with tools on for facts.
It gets about a third of everyday questions right. "I looked that up" means it searched — not that it read the result correctly. Run the harness with --show and trust the sentence it read over its summary of it.
Capitals are its weakest kind of question to read. Asked for the capital of France, it reads the right sentence and answers with the population ("over 13 million"). Canada comes back as Toronto.
Type names with a capital letter. "capital of France" searches for france; "capital of france" searches for today. The harness also searches the subject in your question, which rescues most of these — but not all.
It sometimes garbles what it copies into a query — bell planets solar system for how many planets are in the solar system, costaly for the capital of italy. The harness's subject search catches some of these too.
It answers from whatever it read.

Usage — the harness

bash
python3 harness.py "whats the capital of peru"
python3 harness.py                          # interactive
python3 harness.py --show "who wrote hamlet"   # see what it searched and read
python3 harness.py --no-tools "who are you"

Usage — Ollama

bash
ollama run hf.co/textilelabs/Loom-Spark-3 "who are you"

template and params are read automatically. Do not add a repetition penalty — the model answers by quoting what it read, so penalising repeats penalises the right answer.

Usage — transformers

python
import torch
from transformers import AutoTokenizer, AutoModelForCausalLM

tok = AutoTokenizer.from_pretrained("textilelabs/Loom-Spark-3")
model = AutoModelForCausalLM.from_pretrained("textilelabs/Loom-Spark-3").eval()
eot = tok.convert_tokens_to_ids("<|eot|>")

def ask(message, tools=False):
    p = f"<tools:{'on' if tools else 'off'}>\n<user>\n{message}\n<|eot|>\n<loom>\n"
    ids = tok(p, return_tensors="pt", add_special_tokens=False).input_ids
    with torch.no_grad():
        out = model.generate(ids, max_new_tokens=64, do_sample=False, eos_token_id=eot,
                             pad_token_id=tok.convert_tokens_to_ids("<|pad|>"))[0]
    return tok.decode(out[ids.shape[1]:], skip_special_tokens=False).replace("<|eot|>", "").strip()

Prompt format is exact: <tools:off>\n<user>\n{message}\n<|eot|>\n<loom>\n.

How it was built

Table

architecture	Llama — 20 layers × 256d, GQA (4 heads / 1 KV), SwiGLU, RoPE, tied embeddings
parameters	12,200,192
context	512
vocabulary	4,096 custom BPE
optimiser	Muon on the 2D hidden matrices, AdamW on embeddings and norms
schedule	warmup → stable → decay (WSD), 35% decay; the second pass its own short WSD
corpus	159,308 conversations · ~98,400 lookups, every one a subject query
second pass	43,563 conversations — 55% replayed from the corpus, plus 10,428 injection examples and 5,232 conversations of 6–13 exchanges, all built from the same corpus

Files

markdown
config.json / model.safetensors           the model
tokenizer.json / tokenizer_config.json    custom BPE tokenizer, 4,096 tokens
loom-spark-3-f16.gguf                     for Ollama / llama.cpp
harness.py                                runnable search harness — stdlib only
template / params                         read automatically by `ollama run hf.co/...`
Modelfile                                 for building locally
ATTRIBUTION.md                            required credits for the training corpora

Training data

Table with columns: slice, source
slice	source
grounded reading, and "the result doesn't say"	SQuAD 2.0 (CC BY-SA 4.0)
when to reach for a tool	MASSIVE (CC BY 4.0) · CLINC150 (CC BY 3.0)
instruction following	databricks-dolly-15k (CC BY-SA 3.0)
multi-turn dialogue structure	OpenAssistant OASST1 (Apache 2.0)
identity, limits, warmth, attribution	Textile Labs — written for Loom
injection resistance, long conversations	Textile Labs — built from the rows above

Every search query is derived mechanically from these sources. No language model wrote any training query, and nothing is fine-tuned from anyone's checkpoint.

License

Model: MIT. Training data retains its original licences and attribution.

Loom-Spark-3

README

What changed from Spark 2

The search harness

Measured against Spark 2

Read this before you use it

Usage — the harness

Usage — Ollama

Usage — transformers

How it was built

Files

Training data

License

Explore FriendliAI today

README

What changed from Spark 2

The search harness

Measured against Spark 2

Read this before you use it

Usage — the harness

Usage — Ollama

Usage — transformers

How it was built

Files

Training data

License