The context layer for production AI agents. This repository is LLMSlim Core (v0.9.0, MIT): local-first context planning and compression that fits prompts, conversation history, RAG, memory, and tool schemas into real token budgets while preserving instructions and execution boundaries.
Live Studio Playground • Documentation • Sarvam Integration • Benchmarks • Changelog
1. Install LLMSlim Core from PyPI (Python 3.9+). Running it needs no API key, model, or network call:
pip install llmslim2. Run this snippet:
from llmslim import compress
ticket = """
Hi team, I hope you are all doing well and had a good weekend.
I am writing about invoice INV-2291, which charged us $480 instead of $240.
We upgraded to the Pro plan on 3 September, but the old Basic plan was billed as well.
Our finance lead was asking about this during the weekly sync, which ran long as usual.
Please refund the duplicate $240 charge to the card ending 4417.
Thanks so much, and let me know if you need anything else from me.
"""
result = compress(ticket, target_ratio=0.6) # target: keep about 60% of the tokens
print(result.compressed_text)
print(f"{result.original_tokens} -> {result.compressed_tokens} tokens ({result.reduction_percent:.1f}% fewer)")3. What you should see (llmslim 0.9.0, base install):
Hi team, I hope you are all doing well and had a good weekend. I am writing about invoice INV-2291, which charged us $480 instead of $240. We upgraded to the Pro plan on 3 September, but the old Basic plan was billed as well. Please refund the duplicate $240 charge to the card ending 4417.
112 -> 72 tokens (35.7% fewer)
Two of the six sentences are dropped; the invoice number, amounts, plan change,
and refund request are kept. The default extractive mode only selects sentences
from your input, so the same input always gives the same output. The base install
estimates tokens at about 4 characters per token and prints a one-line warning
saying so. With pip install "llmslim[fast-tokens]", tokens are counted with
tiktoken instead: on this input the same four sentences are kept, and the count
reads 107 -> 72 tokens (32.7% fewer).
Next: Docs • Platform beta • Issues
If LLMSlim is useful, consider starring the repo or opening an issue with feedback.
| LLMSlim Core | LLMSlim Platform | |
|---|---|---|
| Version | 0.9.0 | 0.9.1 beta |
| License | MIT, this repository | Proprietary, private beta |
| Install | pip install llmslim |
By invitation; not published to PyPI |
| What it does | Compresses, plans, and traces model-visible context inside your Python process | Builds on Core: a verifiable timeline of agent state, explainable and replayable context decisions, and outcome-driven context policies that start in shadow mode |
Core is and stays fully open source. Platform is a separate product that depends on Core; none of its code lives in this repository. Read more and request beta access at llmslim.app/platform.
What's new in Core: the agent context runtime (v0.7.0) and the cache-aware context runtime (v0.7.1). Both are in the PyPI package from 0.7.1 onward; 0.7.0 was tagged but not published to PyPI.
LLMSlim is no longer only a fixed-ratio prompt compressor. The Adaptive
Context Planner chooses safe representations for each context item, then uses
a deterministic constrained allocator to fit the highest-value context into a
finite model budget. The original compress() API remains fully supported.
The v0.6.0 release adds explainable per-item decisions, explicit infeasibility reporting, post-plan validation, token and cost telemetry, policy presets, and optional Sarvam AI, Zoho, and MongoDB integrations while keeping the base installation local-first and provider-neutral.
from llmslim import plan_context
plan = plan_context(
messages=[
{"role": "system", "content": "Answer only from verified context."},
{"role": "user", "content": "When does Acme renew?"},
],
documents=[{"content": "CRM: Acme renews on 2026-11-30."}],
query="Acme renewal date",
model="sarvam-105b",
max_input_tokens=8_000,
reserve_output_tokens=512,
)
assert plan.feasible
print(plan.final_context)
print(plan.metrics.planned_tokens, plan.metrics.estimated_input_cost_after)Planning works offline with the base install. Optional integrations are isolated behind extras:
pip install "llmslim[sarvam]" # Sarvam provider (official sarvamai SDK)
pip install "llmslim[zoho]" # CRM and WorkDrive context sources
pip install "llmslim[mongodb]" # explicit memory and Atlas retrievalSee the architecture, algorithm, security model, CLI, and measured offline benchmark.
LLMSlim is part of 14 startup programs. They provide credits, tools, and guidance; none of them is an investor, and membership does not imply endorsement.
| Program | Company |
|---|---|
| Sarvam Startup Program | Sarvam AI |
| Zoho for Startups | Zoho |
| MongoDB for Startups | MongoDB |
| Claude for Startups | Anthropic |
| OpenAI for Startups | OpenAI |
| Auth0 for Startups | Okta (Auth0) |
| Zendesk for Startups | Zendesk |
| Mixpanel for Startups | Mixpanel |
| Sentry for Startups | Sentry |
| Descope Hello World Startup Program | Descope |
| Pulumi for Startups | Pulumi |
| Honeycomb for Builders | Honeycomb |
| Exa Startup Grants | Exa |
| Neo4j Startup Program | Neo4j |
Logos are trademarks of their owners and identify each program.
LLMSlim has been accepted into the Sarvam Startup Program. This is program membership only: it is not a partnership, and it does not imply an endorsement by Sarvam AI.
Separately, LLMSlim Core ships an optional Sarvam integration (llmslim[sarvam])
built on the official sarvamai Python SDK. You plan and compress context locally,
then send only the planned context to a Sarvam model such as sarvam-105b.
- Local planning: retrieved documents are planned and compressed in your Python process before any request is sent.
- Local-first: sensitive retrieved context stays local; only the planned context is sent to the model.
- Your application stays in charge: LLMSlim is a pre-processor. Your application owns API keys, prompts, and inference, and nothing is sent to Sarvam unless your code calls the provider.
pip install "llmslim[sarvam]"
export SARVAM_API_KEY="..." # your own Sarvam API keyfrom llmslim import plan_context
from llmslim.integrations.sarvam import SarvamProvider
documents = [
{"content": "Q3 filing: new data-localisation rules take effect in April 2027."},
{"content": "Q3 filing: two pending licence renewals carry a regulatory risk of delay."},
]
plan = plan_context(
messages=[{"role": "system", "content": "Answer from verified context."}],
documents=documents,
query="Summarize the key regulatory risks.",
model="sarvam-105b",
max_input_tokens=8_000,
reserve_output_tokens=256,
)
provider = SarvamProvider.from_env(model="sarvam-105b", max_tokens=256)
answer = provider.chat([{"role": "user", "content": plan.final_context}])
print(answer, provider.last_usage)👉 Read the Sarvam integration guide (also in docs/integrations/SARVAM.md)
LLMSlim Holographic Engine: Multi-stage token compression condensing sparse context streams into dense information cores with zero contract mutation.
Modern LLM systems suffer from the Context Window Dilemma:
- Financial Tax: Re-sending large prompts on every turn means you pay for the same input tokens again and again.
- Latency Bottleneck: Large prompts inflate Time-To-First-Token (TTFT) and queue times.
- Lost-In-The-Middle Syndrome: Models can miss or misuse information buried in the middle of long contexts.
- Security Risks: Untrusted RAG content can smuggle indirect prompt injections into system instructions.
LLMSlim fixes this at the source. It provides deterministic, contract-preserving compression that runs natively in your application layer before calling any model.
| Pillar | How LLMSlim Solves It |
|---|---|
| 🏎️ Ultra-Low Overhead | Pure Python + NumPy/Scikit-learn. Median 0.026 ms per sample (p95 1.889 ms) in the 24-sample, mostly short-text Phase 2 evaluation, with no model calls on the default path. Longer inputs take longer. |
| 🔒 Deterministic by Default | The default extractive mode only selects sentences from your input, so output is reproducible and contains no generated text. It can still drop a fact you need, so check results for your use case. Rewrite and hybrid modes call your own LLM. |
| 🛡️ Provenance Security | ContextRole hierarchy isolates untrusted RAG/tool text so prompt injections cannot escalate to system priority. |
| 🧩 Contract-Safe Tool Schemas | Canonical JSON normalization, SHA-256 contract fingerprints, and zero execution rewrites for agent tooling. |
| 🔌 Provider-Neutral | Execution-free request builders for Sarvam, OpenAI, Anthropic, Gemini, and vLLM, plus an OpenAI Agents SDK bridge. Works with any framework that can pass plain message or document lists. |
🖥️ Live Studio Playground (www.llmslim.app)
Paste a long chat, a stack of search results or a CI log, ask a question, and watch LLMSlim keep what answers it. The Studio shows the tokens and cost saved, whether the answer survived, and what plain truncation to the same size would have kept instead.
- Ready-made scenarios: a six-month support chat, help-centre search results, and a CI log with one failure, each with a question whose answer is known.
- Your own text: paste up to about 16,000 tokens and choose how much to keep.
- In place: kept lines are highlighted inside the original, next to the exact text the model would receive.
- No model call: the Studio runs Core on the server and calls no provider. Nothing you paste is stored.
See Studio deployment and the security policy.
Explore our redesigned dark/light documentation site covering end-to-end integration patterns:
# Core package (Deterministic extractive engine, 0 external LLM dependencies)
pip install llmslim
# With optional Model Context Protocol (MCP) catalog ingestion (Python 3.10+)
pip install "llmslim[mcp]"
# With optional OpenAI Agents SDK host bridge (Python 3.10+)
pip install "llmslim[agents]"
# With optional local multilingual semantic retrieval
pip install "llmslim[semantic]"
# Sarvam: chat providers, language tools and document source (official sarvamai SDK)
pip install "llmslim[sarvam]"
# Exa web search as an untrusted RAG context source (spend capped in USD)
pip install "llmslim[exa]"
# Neo4j temporal agent memory with auditable supersession
pip install "llmslim[neo4j]"
# Read-only Zoho CRM and WorkDrive context sources
pip install "llmslim[zoho]"
# Explicit MongoDB context memory and Atlas retrieval
pip install "llmslim[mongodb]"
# LangChain, LlamaIndex (Python 3.10+) and Haystack adapters
pip install "llmslim[langchain]"
pip install "llmslim[llamaindex]"
pip install "llmslim[haystack]"
# Agent history: gptme (0.34+) and Pydantic AI adapters (Python 3.10+).
# Hermes Agent needs no extra: install llmslim into Hermes's environment.
pip install "llmslim[gptme]"
pip install "llmslim[pydantic-ai]"
# All optional extensions
pip install "llmslim[all]"Requirements: Python 3.9 or higher. No provider SDK, PyTorch, sentence-transformers, or cloud service is required for the default installation.
from llmslim import ContextRole, compress
text = """
The Apollo program was conceived in 1960 during the Eisenhower administration.
NASA announced the program as a follow-up to Project Mercury.
The spacecraft was designed to carry three astronauts.
Apollo succeeded in landing the first humans on the Moon in 1969.
Funding for the program peaked in 1966 with over $4.5 billion appropriated.
"""
result = compress(
text,
target_ratio=0.5, # Target: keep about 50% of the tokens
strategy="extractive", # Deterministic sentence selection
context_role=ContextRole.GENERAL,
)
print("Compressed Output:")
print(result.compressed_text)
print(f"Original: {result.original_tokens} tokens | Compressed: {result.compressed_tokens} tokens")
print(f"Saved: {result.tokens_saved} tokens ({result.reduction_percent:.1f}%)")
print(f"Sentences kept: {result.sentences_kept} of {result.sentences_total}")Extractive selection keeps whole sentences, not meaning: always check that the
sentences you need survived. On this text, the 0.7.1 base install keeps three of
the five sentences and drops the 1969 Moon landing sentence; with
llmslim[fast-tokens] (tiktoken counts) it keeps that sentence and drops another.
Compress each retrieved chunk before you build the prompt. compress_documents
takes plain strings and returns one result per document, in order:
from llmslim import compress_documents
documents = [
"Q3 revenue grew 23% year-over-year to $1.2B. "
"Growth came mainly from enterprise subscriptions in India and Southeast Asia. "
"The board met twice during the quarter. "
"The office cafeteria menu was updated in August. "
"A new logo was unveiled at the annual offsite. "
"Net revenue retention reached 118%, up from 109% a year earlier.",
"Operating expenses rose 11% because of AI research infrastructure. "
"Most of the increase was GPU capacity for model evaluation. "
"Travel costs were flat. "
"The parking garage was repainted in September. "
"Employees voted on a new name for the meeting rooms. "
"Headcount in engineering grew by 40 people.",
]
results = compress_documents(
documents,
query="What drove Q3 revenue and cost changes?",
target_ratio=0.5,
)
context = "\n\n".join(r.compressed_text for r in results)
print(context)
print(f"Saved {sum(r.tokens_saved for r in results)} tokens across {len(results)} documents")With a query, the documents share one budget and it goes where the query points. Relevance is lexical by default (BM25 with feedback: no model, deterministic, tens of milliseconds on a 3k-token context). For RAG and long chat memory, where the answer often shares few words with the question, add the optional reranker:
# pip install "llmslim[semantic]" (sentence-transformers; uses a GPU when there is one)
results = compress_documents(documents, query=question, target_ratio=0.25, relevance="semantic")relevance also accepts any callable scorer(query, texts) -> scores, such as a hosted reranking API.
Retrieving with LangChain, LlamaIndex or Haystack? Use the
framework adapters instead of calling
compress_documents yourself.
Note
compress_documents treats documents as untrusted (ContextRole.RAG) by default,
so imperative wording inside a retrieved document is never force-kept as a
protected instruction. It does not remove injected text: an injected sentence
can still survive compression. To mark retrieved content as untrusted in the final
prompt, use plan_context or
ContextRuntime, which wrap every document in a
trusted="false" provenance tag and ignore any role a document claims for itself.
Compress long earlier turns while passing system instructions and user questions through unchanged:
from llmslim import compress_chat_messages
review = (
"Here are my suggestions for your schema. First, add a composite index on "
"(customer_id, created_at) because most of your queries filter by customer and sort by "
"date. Second, the orders table stores the shipping address inline, which duplicates "
"data across rows; move it to an addresses table. Third, the status column is a "
"free-text string, so use an enum or a lookup table instead. Fourth, the price column "
"uses FLOAT, which loses precision for money; use DECIMAL(12, 2). Finally, add ON "
"DELETE RESTRICT to the foreign key from orders to customers so that deleting a "
"customer cannot silently orphan their orders."
)
messages = [
{"role": "system", "content": "You are a specialized code review engineer."},
{"role": "user", "content": "Can you review my database schema design?"},
{"role": "assistant", "content": review},
{"role": "user", "content": "What about the foreign key constraint on line 42?"},
]
compressed_messages = compress_chat_messages(
messages,
target_ratio=0.5,
compressible_roles=("assistant",), # Only compress assistant turns; system and user pass through
min_tokens=60, # Turns shorter than this are never compressed
)
for message in compressed_messages:
print(f"{message['role']}: {message['content']}")Combine ultra-fast extractive pre-filtering with your own LLM provider for deep semantic paraphrasing:
from llmslim import CallableProvider, compress
import openai
client = openai.OpenAI() # reads OPENAI_API_KEY; requires `pip install openai`
long_raw_text = """
The Apollo program was conceived in 1960 during the Eisenhower administration.
NASA announced the program as a follow-up to Project Mercury.
The spacecraft was designed to carry three astronauts.
Apollo succeeded in landing the first humans on the Moon in 1969.
Funding for the program peaked in 1966 with over $4.5 billion appropriated.
"""
# Define your own provider callback (LLMSlim does not bundle vendor SDKs).
# The callback receives a RewriteRequest with ready-made prompts and returns text.
provider = CallableProvider(
lambda req: client.chat.completions.create(
model="gpt-4o-mini",
messages=[
{"role": "system", "content": req.system_prompt},
{"role": "user", "content": req.user_prompt},
],
).choices[0].message.content
)
result = compress(
long_raw_text,
target_ratio=0.3,
strategy="hybrid", # 1. Extractive filter -> 2. LLM semantic rewrite
provider=provider,
)
meta = result.rewrite_metadata
print(result.compressed_text)
print(f"Strategy: {meta.strategy} | Rewrite accepted: {meta.accepted} | Fell back to extractive: {meta.fallback_used}")
print("Validation failures:", meta.failure_reasons)Every rewrite is validated for structure, instruction retention, entity retention,
and similarity. If a hybrid rewrite fails validation, LLMSlim returns the extractive
result instead and reports why in rewrite_metadata.failure_reasons.
Each adapter runs compress_documents on the retrieved documents, with the same
shared budget when there is a query. Kept documents keep their metadata, and
documents that compress to nothing are dropped. They run locally with no model.
| Framework | Install | Class | Use it where you'd use |
|---|---|---|---|
| LangChain | llmslim[langchain] |
llmslim.integrations.langchain.LLMSlimCompressor |
LLMLinguaCompressor, e.g. in ContextualCompressionRetriever |
| LlamaIndex | llmslim[llamaindex] (Python 3.10+) |
llmslim.integrations.llama_index.LLMSlimPostprocessor |
LongLLMLinguaPostprocessor, in node_postprocessors |
| Haystack | llmslim[haystack] |
llmslim.integrations.haystack.LLMSlimDocumentCompressor |
a component between the retriever and the prompt builder |
from langchain_classic.retrievers.contextual_compression import ContextualCompressionRetriever
from llmslim.integrations.langchain import LLMSlimCompressor
retriever = ContextualCompressionRetriever(
base_compressor=LLMSlimCompressor(target_ratio=0.25),
base_retriever=your_retriever,
)Runnable examples with their output: LangChain, LlamaIndex, Haystack.
These adapters fit an agent's message history into a token budget. They keep the system prompt, tool calls and the latest turns as they are, compress older tool output and turns locally (failures and tracebacks in tool output are kept), and keep every tool call paired with its result. There is no model call.
| Agent | Install | Class or function | How it plugs in |
|---|---|---|---|
| gptme | llmslim[gptme] (gptme 0.34+) |
llmslim.integrations.gptme.LLMSlimContextProvider |
gptme context provider llmslim; [plugin.llmslim] compaction = true makes it the one gptme's compaction uses |
| Hermes Agent | llmslim in Hermes's environment | llmslim.integrations.hermes.LLMSlimContextEngine |
ContextEngine plugin llmslim; select it with context.engine: llmslim |
| Pydantic AI | llmslim[pydantic-ai] (1.0+) |
llmslim.integrations.pydantic_ai.llmslim_history_processor |
history processor, in ProcessHistory(...) or history_processors=[...] |
from pydantic_ai import Agent
from pydantic_ai.capabilities import ProcessHistory
from llmslim.integrations.pydantic_ai import llmslim_history_processor
agent = Agent(
"openai:gpt-5",
capabilities=[ProcessHistory(llmslim_history_processor(max_tokens=8_000))],
)Setup and runnable examples with their output: gptme, Hermes Agent, Pydantic AI.
Compression algorithms that naively score sentences based on imperative keywords ("Must", "Always", "Action Required") introduce a severe vulnerability: indirect prompt injection amplification. An attacker injecting malicious instructions into a retrieved RAG document can trick the compressor into preserving the attack payload while discarding legitimate context.
We found this issue in LLMSlim internally and fixed it in v0.3.1. No CVE or security advisory was published, and the issue has no official CVSS score.
LLMSlim solves this via an explicit Context Role Trust Boundary:
┌────────────────────────────────────────────────────────┐
│ HIGHEST TRUST (Priority Tier 4) │
│ System & Developer Prompts (Strictly Protected) │
├────────────────────────────────────────────────────────┤
│ INTERMEDIATE TRUST (Priority Tier 2-3) │
│ Direct User Input │
├────────────────────────────────────────────────────────┤
│ PROVENANCE-LOCKED (Priority Tier 0-1) │
│ RAG Documents • Assistant History • Tool Outputs │
│ *Cannot reach Tier 4 through imperative patterns* │
└────────────────────────────────────────────────────────┘
- Hardened Priority Locking: Content marked
ContextRole.RAG,ContextRole.TOOL, orContextRole.ASSISTANTcannot achieve Tier-4 priority, regardless of imperative syntax. - Nonce-Protected Rewrite Delimiters: When the input contains a fence-like token such as
---END TEXT---, the rewrite template's fences get a random per-call nonce, so the embedded token cannot close the text region. The input itself is never modified. - Untrusted by default, not filtered: these protections stop injected text from gaining priority. They do not delete it.
plan_contextandContextRuntimelabel ittrusted="false"in the final context so your model and application can treat it accordingly.
Large agent catalogs (dozens or hundreds of tool definitions) waste thousands of tokens before an agent even starts thinking. LLMSlim introduces Contract-Safe Tool Infrastructure (v0.4.0 & v0.5.0):
from llmslim.tools import (
canonical_json,
contract_equivalent,
fingerprint_tool_schema,
from_mcp_tool,
optimize_tool_schema,
)
# 1. Ingest authoritative raw tool definition
raw_tool = {
"name": "enterprise.search_ledger",
"description": "Searches financial transaction records by date range.",
"inputSchema": {
"type": "object",
"properties": {"account_id": {"type": "string"}, "limit": {"type": "integer"}},
"required": ["account_id"],
},
}
# 2. Parse and safely optimize schema formatting
tool = from_mcp_tool(raw_tool, namespace="finance")
result = optimize_tool_schema(tool)
# 3. Mathematically verify exact contract equivalence
assert result.equivalence.status.value == "EXACT"
assert fingerprint_tool_schema(tool) == fingerprint_tool_schema(result.optimized)
print("Canonical Fingerprint:", fingerprint_tool_schema(result.optimized))
print(canonical_json(result.optimized.raw))Requires pip install "llmslim[mcp]" (Python 3.10+) and an MCP server you run:
import asyncio
from llmslim.mcp import MCPToolCatalogSource, PlanMode, plan_catalog_context
async def main() -> None:
# Streamable HTTP MCP source with bounded pagination and stale-cache detection
source = MCPToolCatalogSource.from_streamable_http(
"http://127.0.0.1:8000/mcp",
headers={"Authorization": "Bearer local-token"},
)
snapshot = await source.list_tools()
plan = plan_catalog_context(snapshot, mode=PlanMode.FULL)
print(f"Catalog contains {len(snapshot.tools)} tools ({plan.metrics.catalog_tokens} tokens)")
asyncio.run(main())Many libraries make unsubstantiated claims about 90% prompt compression. At LLMSlim, we practice Radical Benchmark Transparency:
Same model and prompt for every configuration; only the context changes. Truncation gets exactly LLMSlim's token count. Tuning used separate development questions only, and every suite was rerun once on a fresh sample after the code was frozen. Full tables, confidence intervals, weak spots, head-to-head runs of LLMLingua-2 and LongLLMLingua, the harness and raw per-question results: benchmarks/live.
| Benchmark | Full context | LLMSlim 0.8 + reranker | LLMSlim 0.8 (no model) | Truncate, same budget | Tokens (full → LLMSlim) |
|---|---|---|---|---|---|
| LongMemEval-S, 90 q (accuracy) | 82.2 | 76.7 | 68.9 | 14.4 | 114,006 → 7,985 |
| … fresh 90 q | 72.2 | 76.7 | 67.8 | 14.4 | |
| NaturalQuestions 20 docs, 300 cases: 100 q × 3 answer positions (accuracy) | 86.3 | 75.0 | 65.7 | 52.0 | 2,889 → 668 |
| … fresh 300 cases | 88.0 | 75.7 | 67.3 | 48.3 | |
| HotpotQA, 200 q (F1) | 74.9 | 69.4 | 67.5 | 49.5 | 2,179 → 939 |
| LongBench v1, 210 samples (macro) | 54.9 | 54.2 | 54.9 | 45.2 | 15,532 → 5,232 |
| … fresh 210 samples | 55.1 | 55.4 | 55.0 | 46.8 | |
| LongBench v2, 180 q (accuracy) | 60.0 | 55.6 | 53.9 | 48.3 | 30,493 → 8,469 |
| SWE-bench Verified Mini, 50 issues (resolved) | 36-38 | not run | 38 | not run | 48-58k → 51k per task |
The reranker is optional (relevance="semantic", a 22M-parameter cross-encoder from the semantic extra); without
it LLMSlim runs no model at all.
Note
The Schema-Tax Measurement: In our v0.4.0 benchmark across 375 synthetic tool schemas in 18 catalogs written for this repository (see the dataset card), lossless schema compression saved 0 tokens (0.00%) when the baseline was already compact canonical JSON. We publish this result transparently: we never claim imaginary savings where none exist.
| Method | Budget success | Context reduction | Required facts | Hard constraints | Mean latency* |
|---|---|---|---|---|---|
| Raw full context | 71.4% | 0.0% | 100% | 100% | measurement only |
| Naive prefix | 100% | 9.2% | 100% | 100% | 2.21 ms |
| Fixed-ratio compressor | 78.6% | 9.6% | 94.0% | 96.4% | 26.55 ms |
| Adaptive planner | 96.4% | 11.4% | 100% | 100% | 208.02 ms |
The 28-case corpus covers chat, RAG, tools, mixed, external-source, and 12-language multilingual cases. The sole adaptive infeasibility is an intentionally impossible full-catalog case; it is reported explicitly. These task-grounded checks are not an LLM-judge or universal quality claim. Latency is specific to the checked-in run and hardware. See the release gate results, raw results, and frozen dataset. The live Sarvam harness was not run without both explicit opt-in and credentials.
Compress files, streams, or prompts directly from your terminal:
# Compress a document to 50% ratio
llmslim document.txt -o compressed.txt --ratio 0.5
# Pipeline integration with jq / curl
cat input.txt | llmslim --ratio 0.4 --mode rag > rag_context.txt
# Inspect token count differences
llmslim document.txt --statsRelease notes for every version, including 0.7.0 and 0.7.1, are in CHANGELOG.md and on GitHub Releases.
LLMSlim operates as an unopinionated context pre-processor. These integrations ship in Core; none of them sends a request for you. Every integration that spends a vendor credit is checked by a UsageGuard before the request leaves the process (per-minute rate, lifetime request cap and a unit cap in INR, USD or queries, configurable with LLMSLIM_<VENDOR>_* variables; see .env.example):
| Provider / Framework | What ships in Core | Pattern |
|---|---|---|
| Sarvam AI | llmslim[sarvam]: SarvamProvider/AsyncSarvamProvider, SarvamLanguageTools, SarvamDocumentSource, annotate_languages()/normalize_scripts(), sarvam_messages() |
Local planning + official sarvamai Python SDK, guarded with dated INR prices |
| Exa | llmslim[exa]: ExaSearchSource, vendor-neutral WebSearchSource |
Untrusted RAG context items with URL, date and rank provenance; spend capped in USD |
| Neo4j | llmslim[neo4j]: Neo4jContextStore |
Explicit tenant-scoped temporal memory: supersede(), recall(as_of=...), history(), conflicts() |
| OpenAI | openai_compatible_request(), openai_responses_request() |
Execution-free request builders; your code sends the request |
| Anthropic Claude | anthropic_messages_request() |
Execution-free request builder with optional prompt-cache markers |
| Google Gemini | gemini_generate_request(), gemini_cached_content_request() |
Execution-free request builders |
| vLLM / self-hosted | vllm_chat_request() |
Execution-free request builder |
| OpenAI Agents SDK | llmslim[agents]: make_openai_agents_input_filter(), to_openai_agents_tools() |
Text-only model-input filter; the SDK keeps execution and tool ownership |
| LangChain | llmslim[langchain]: LLMSlimCompressor |
BaseDocumentCompressor for ContextualCompressionRetriever |
| LlamaIndex | llmslim[llamaindex]: LLMSlimPostprocessor |
BaseNodePostprocessor for query engines |
| Haystack | llmslim[haystack]: LLMSlimDocumentCompressor |
Pipeline component between retriever and prompt builder |
| gptme | llmslim[gptme]: LLMSlimContextProvider |
Context provider for gptme's compaction (entry point llmslim) |
| Hermes Agent | LLMSlimContextEngine (no extra) |
ContextEngine plugin; no LLM call, cache-stable prefix |
| Pydantic AI | llmslim[pydantic-ai]: llmslim_history_processor() |
History processor that keeps tool calls and returns paired |
For other frameworks there is no dedicated adapter. LLMSlim works with any framework
that can pass plain message lists ({"role": ..., "content": ...} dicts) or document
strings; you write the few lines of glue that pass LLMSlim's output to your client.
LLMSlim is open-source software licensed under the MIT License. See LICENSE for full details.
If you use LLMSlim in your research or production systems, please cite:
@software{llmslim2026,
author = {Yashvardhan Thanvi},
title = {LLMSlim: Deterministic Context Compression and Contract-Safe Tool Schemas for LLMs},
year = {2026},
publisher = {GitHub},
url = {https://github.com/Thanatos9404/llmslim}
}Version 0.7.0 added a per-turn context path for agent applications (0.7.0 was not published to PyPI; install 0.7.1 or later). The host supplies messages, retrieved documents, memories, tool results, and authorized tool schemas; LLMSlim returns a quality-checked model input and an explainable local trace. Model calls and tool execution stay with the host.
from llmslim import ContextRuntime, generic_request
runtime = ContextRuntime(model="sarvam-105b", max_input_tokens=8_000)
prepared = runtime.prepare_sync(
user_input="When does Acme renew?",
messages=[{"role": "system", "content": "Use verified dates."}],
documents=[{"id": "contract", "content": "Acme renews on 9 November 2026."}],
)
if prepared.feasible:
request = generic_request(prepared) # the host sends this to its model
print(request["messages"])
print(prepared.trace.explain())The runtime includes ContextEnvelope, ContextGraph, ContextPolicy,
progressive planning, quality gates, bounded in-memory sessions, and
execution-free adapters for generic, Sarvam, OpenAI-compatible, and text-only
OpenAI Agents applications. ContextTrace omits prompt bodies by default.
The existing compress() and plan_context() APIs continue to work.
See the architecture, security model, integrations, migration guide, benchmark, and engineering report.
Cache planning is an opt-in layer for repeated agent turns. LLMSlim identifies
stable provider-visible prefixes, keeps append-only conversation context when
safe, fingerprints cache-sensitive settings, and reports local cache estimates
separately from provider-reported usage. A tenant-scoped CacheManager stores
metadata and provider references, never prompt bodies or KV tensors.
from llmslim import CacheManager, CachePolicy, ContextRuntime
runtime = ContextRuntime(
model="generic-128k",
cache_policy=CachePolicy(mode="auto", provider="openai", tenant_id="my-workspace"),
cache_manager=CacheManager(),
)
prepared = runtime.prepare_sync(
session_id="conversation-1",
messages=[{"role": "system", "content": "Use verified sources."}],
user_input="What changed?",
)
print(prepared.trace.to_dict()["cache"])Execution-free request builders cover OpenAI Responses, Anthropic Messages, Gemini cached resources, and self-hosted vLLM. An advanced in-process Transformers adapter validates KV continuation state. OpenAI provider-stateful continuation and Gemini cached-resource creation require explicit host opt-in. Sarvam prompt caching remains unverified and is disabled by default. The Context Inspector shows prefix segmentation and cache diagnostics without calling a provider. See caching guidance, multi-turn benchmark, and engineering report.
Snyk provides developer security tooling for open-source projects. Learn more about its Secure Developer Program.