Key points
- Core idea — cognitive offloading: Harness-1 frees search agents from doing both "semantic decisions" and "state management." The environment-side harness (a structured state machine) manages the candidate pool, curated set, evidence graph, verification records, full-text store, search history, and token budget; the 20B policy model only decides what to search, what to keep/discard, what to verify, and when to stop.
- Key mechanism — the Curated Set: The model maintains an explicit curated set of up to 30 documents with four importance levels (very high / high / fair / low), replacing implicit top-k truncation with explicit curation. Removing importance labels costs 4.1% recall.
- Other harness components: an evidence graph (entity–document mapping for multi-hop bridging; removing it costs 2.6%), a verify tool with recorded verification outcomes (removing it costs 3.1%), Sentence-BM25 compression + MinHash dedup of candidates, and a token-budget marker (
[Token usage: 14,203/32,768]) that makes the model budget-aware. - Training recipe: 1. SFT on 899 high-quality filtered trajectories (distilled from Kimi K2.5), teaching behavioral priors (parallel tool calls, query decomposition, pruning) rather than answers. 2. On-policy CISPO RL from the SFT checkpoint: 128 queries × 8 rollouts per step, 80 steps (~82K rollouts), with a multi-objective reward combining curated-set quality, trajectory coverage, answer evidence, answer discovery, tool diversity (w_div = 0.15 — without it the policy collapses into search-only mode, dropping curated recall from ~0.60 to ~0.53), an answer-omission penalty, and a turn penalty.
- Results:
- Striking transfer result: RL training used only one benchmark (SEC financial reports), yet gains on 4 zero-shot transfer benchmarks (+17.0 pts over Context-1) are 2.2x the in-domain gains (+7.9 pts). The authors' interpretation: "the policy is learning operations over a domain-general search state" — explicit search state generalizes better than implicit dialogue history.
- Ablations (BrowseComp+): importance labels −4.1%, evidence graph −2.6%, verify tool −3.1%, disabling everything −12.2% — mechanisms work synergistically, not as independent add-ons.
- Data efficiency: only 899 SFT trajectories + ~4,352 unique RL queries, versus 8K (Search-R1) and 221K (Qwen3) for competitors. The trick: behavioral priors are moved into the interface, so RL optimizes only semantic decisions.
- Scoped to evidence retrieval (needle-in-haystack / multi-hop), not open-ended report generation.
- The evidence graph uses lightweight regex entity extraction — no entity disambiguation (e.g., aliases of the same person are not linked).
- The LLM-based verifier can err, potentially giving false confidence on wrong evidence.
- Sentence compression (top-4 sentences) can drop discourse-dependent context; full text is available via
read_documentbut the token budget remains. - No built-in access controls for sensitive/copyrighted/biased content; filtering must happen at the application layer.
- Paper: https://arxiv.org/abs/2606.02373
- Code & weights: https://github.com/pat-jj/harness-1
- Chroma Context-1 report: https://www.trychroma.com/research/context-1
- Chroma Context-1 blog commentary: https://atalupadhyay.wordpress.com/2026/03/27/chroma-context-1-the-self-editing-search-agent-that-changes-how-we-build-rag-systems/
- Related paper, "Storage Is Not Memory": https://arxiv.org/html/2605.04897v1
| Model | Size | Avg. Recall | Type | |---|---|---|---| | Opus-4.6 | — | 79.4% | Closed frontier | | Harness-1 | 20B | 73.0% | Open, small | | GPT-5.4 | — | 70.9% | Closed frontier | | Sonnet-4.6 | — | 68.8% | Closed frontier | | Kimi-K2.5 | — | 64.7% | Closed frontier | | Context-1 | 20B | 61.6% | Open baseline | | Tongyi DR 30B | 30B | 60.3% | Open | | GPT-OSS-120B | 120B | 59.0% | Open | | Search-R1 32B | 32B | 28.9% | Open | | Qwen3 32B | 32B | 21.6% | Open |
Acknowledged limitations
Takeaway
"The interface itself is part of the method." Rather than scaling model size, Harness-1 redesigns the agent's interaction surface so that everything that can be delegated to the environment is delegated. The same philosophy could apply to code agents (environment maintains AST/symbol tables), data-analysis agents (environment maintains schemas/statistics), or clinical agents (environment maintains patient timelines). Retrieval capability, the results suggest, is a function of interface design more than of parameter count.