needlepath-langchain 0.1.0__tar.gz

needlepath_langchain-0.1.0/.gitignore

@@ -0,0 +1,7 @@
+.venv/
+dist/
+build/
+*.egg-info/
+__pycache__/
+node_modules/
+*.tsbuildinfo

needlepath_langchain-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

needlepath_langchain-0.1.0/PKG-INFO

@@ -0,0 +1,229 @@
+Metadata-Version: 2.4
+Name: needlepath-langchain
+Version: 0.1.0
+Summary: Needlepath context selection for LangChain agents (AgentMiddleware) and LangGraph.
+Project-URL: Homepage, https://nextmoca.com
+Author: Next Moca Global, Inc.
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: agents,context,langchain,langgraph,middleware,needlepath
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Typing :: Typed
+Requires-Python: >=3.10
+Requires-Dist: langchain<2.0.0,>=1.2.9
+Requires-Dist: needlepath<1.0.0,>=0.1.0
+Provides-Extra: dev
+Requires-Dist: mypy>=1.8; extra == 'dev'
+Requires-Dist: pytest-asyncio>=0.23; extra == 'dev'
+Requires-Dist: pytest>=7; extra == 'dev'
+Requires-Dist: ruff>=0.5; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# `needlepath-langchain`
+
+Needlepath context selection for LangChain agents — and, in this same package,
+the LangGraph recipe.
+
+```bash
+pip install needlepath-langchain
+```
+
+## One line
+
+```python
+from langchain.agents import create_agent
+from needlepath_langchain import NeedlepathMiddleware
+
+agent = create_agent(
+    model,
+    tools,
+    middleware=[NeedlepathMiddleware(operating_point="np-2026-07-r2")],
+)
+```
+
+The key comes from `NEEDLEPATH_API_KEY`, the operating point is pinned
+explicitly, and if the service is slow, down, or stands down, the agent runs on
+its original context and says so in message metadata.
+
+## The two seams
+
+### `wrap_tool_call` — the sweet spot
+
+The only documented, first-class, mutate-the-tool-result seam in the ecosystem.
+A tool returns 40 KB of JSON; what enters the message list is the part of it that
+answers the current step.
+
+Engages only when a single tool result exceeds `tool_result_max_tokens` (default
+2000), which is also the budget. Below it, no call is made and nothing is
+touched.
+
+### `wrap_model_call` — selection over the accumulated history
+
+Before every model call, the tool results already in the history are selected
+against the *current* task. A result that mattered three steps ago and does not
+matter now collapses to a placeholder; the one that matters is excerpted
+verbatim. Engages only when the prunable history exceeds `history_max_tokens`
+(default 8000).
+
+Non-destructive by construction: `request.override(messages=…)` returns a new
+request and never touches `request.state`, so the graph keeps the full history
+and only the model sees the selection.
+
+Both seams are on by default and independently switchable
+(`select_tool_results=`, `select_history=`).
+
+## Configuration
+
+| Parameter | Default | What it does |
+|---|---|---|
+| `operating_point` | — | **Required.** Immutable label. Also `NEEDLEPATH_OPERATING_POINT`. |
+| `shadow` | `False` | Measure and report; never apply. |
+| `enabled` | `True` | Kill switch. Needs no credentials when `False`. |
+| `select_tool_results` / `select_history` | `True` | The two seams. |
+| `tool_result_max_tokens` | `2000` | Trigger *and* budget for one tool result. |
+| `history_max_tokens` | `8000` | Trigger *and* budget for the history. |
+| `preserve_recent` | `2` | Trailing messages never rewritten. |
+| `include_ai_messages` / `include_human_messages` | `False` | Widen beyond tool results. |
+| `placeholder` | see source | Replaces an unselected tool result. |
+| `name` | class name | **Must be unique** if you register two instances. |
+
+Any other keyword is forwarded to the core client (`base_url`, `api_key`,
+`timeout`, `max_retries`, …).
+
+## Two invariants, and why they cost tokens
+
+**A message is never removed, only rewritten.** LangGraph's
+`_validate_chat_history` raises when an `AIMessage` carrying `tool_calls` loses
+its matching `ToolMessage`, and every provider rejects the same shape:
+
+```
+ValueError: Found AIMessages with tool_calls that do not have a corresponding ToolMessage.
+```
+
+A selector that drops messages has to reason about tool-call pairing on every
+path and get it right every time. One that only rewrites content in place cannot
+break the pairing at all — the message objects, their ids and their
+`tool_call_id`s are exactly what they were. We take the second option and give up
+the savings from deleting message envelopes.
+
+**A rewrite never grows a message and never empties one.** An excerpt longer than
+what it replaces, or an empty excerpt applied to a non-empty message, is refused
+here rather than trusted upstream.
+
+By default only `ToolMessage`s are rewritten. `SystemMessage` never is, on any
+setting. An `AIMessage` carrying `tool_calls` never is: its content is usually
+empty and the part that matters is the call list.
+
+## Fail open
+
+Every error path passes the original context through, with the reason recorded in
+`response_metadata["needlepath"]`:
+
+```python
+{
+    "applied": False,
+    "reason": "engine_fallback",
+    "request_id": "np-…",
+    "tokens_before": 8400,
+    "tokens_saved": 0,
+    "gate_reason": "standdown:flat_gap",
+}
+```
+
+`reason` is an open enum. Treat an unrecognized value as "not applied".
+
+`middleware.stats.as_dict()` aggregates the same counters — the input to a
+shadow report.
+
+## Sync **and** async
+
+Both variants of both hooks are implemented, and that is not optional:
+`create_agent` puts a middleware in *both* the sync and async hook lists if it
+implements *either*, specifically so the base class's `NotImplementedError`
+fires. A middleware that implements only the sync hooks raises under `ainvoke()`.
+
+If you pass your own `client=` without an `async_client=`, the async hooks run it
+on the default executor rather than blocking the event loop.
+
+## Lifecycle
+
+A middleware is normally wired up once and lives as long as the agent, so you
+never need to close it. If you construct one per request or per test, call
+`middleware.close()` / `await middleware.aclose()` to release the connection
+pools. Clients you passed in with `client=` / `async_client=` are yours and are
+never closed for you.
+
+## LangGraph
+
+Same package, not a second distribution.
+
+```python
+from langgraph.prebuilt import create_react_agent
+from needlepath_langchain.langgraph import needlepath_pre_model_hook
+
+agent = create_react_agent(
+    model,
+    tools,
+    pre_model_hook=needlepath_pre_model_hook(operating_point="np-2026-07-r2"),
+)
+```
+
+**Prefer `create_agent` + `NeedlepathMiddleware` if you can.** `pre_model_hook`
+exists only on `create_react_agent`, which is deprecated since LangGraph v1.0 and
+slated for removal in v2.0.
+
+| Mechanism | Graph state | Verdict |
+|---|---|---|
+| `RemoveMessage` → `add_messages` | **destroys** the removed messages | incompatible with selection |
+| `pre_model_hook` → `llm_input_messages` | `messages` untouched | compatible |
+| `create_agent` + `wrap_model_call` | nothing written at all | **preferred** |
+
+`add_messages` is the only writer of the `messages` channel and its removal path
+physically drops entries. Once it runs, they are gone from the live thread and
+every checkpoint after it. That is a *history compaction* primitive — what
+`SummarizationMiddleware` uses it for — not a *selection* primitive. Selection is
+per-call by definition: the record that does not matter at step 7 may be the one
+that matters at step 9.
+
+### Four sharp edges, all handled
+
+1. **`llm_input_messages` is a persisted channel, not a transient.** It lands in
+   the checkpoint, so every turn adds a full copy of the selection to the
+   checkpoint blob. Real storage on long threads.
+2. **Stale-selection leak.** It is a `LastValue` channel that survives between
+   `invoke()` calls. A hook that *conditionally* skips writing it silently reuses
+   the previous turn's selection. This hook writes it **unconditionally, every
+   pass**.
+3. **An empty selection silently degrades to the full history.** The reader does
+   `state.get("llm_input_messages") or state.get("messages")`, and `[]` is falsy.
+   This hook never emits an empty list.
+4. **`_validate_chat_history` runs on your selection.** Covered by the
+   never-remove-a-message invariant above.
+
+### One caveat this package cannot fix
+
+With `response_format` on `create_react_agent`, the structured-output node reads
+`state["messages"]` directly and does **not** consult `llm_input_messages`. That
+call sees the full history, not your selection. Price your savings accordingly.
+
+## Positioning
+
+LangChain ships `ContextEditingMiddleware` with a `ClearToolUsesEdit` strategy
+in-tree and free, which clears the oldest tool results once a token trigger
+trips. This is not a competitor to "can something prune tool results" — it is a
+different answer to *which bytes should survive*. We select verbatim against the
+current task rather than clearing by age, stand down when trimming would not pay,
+and report what was actually saved.
+
+If clearing by age is enough for your workload, use the free one.
+
+## Tested against
+
+`langchain==1.3.14`, `langchain-core==1.5.3`, `langgraph==1.2.10`. Floor
+`>=1.2.9` (the first release where `ToolCallRequest`, `ModelCallResult` and
+`ExtendedModelResponse` are all importable from the public
+`langchain.agents.middleware` package and `ModelRequest.system_message` is
+stable). Capped at `<2.0.0`; CI runs against the newest 1.x minor.

needlepath_langchain-0.1.0/README.md

@@ -0,0 +1,205 @@
+# `needlepath-langchain`
+
+Needlepath context selection for LangChain agents — and, in this same package,
+the LangGraph recipe.
+
+```bash
+pip install needlepath-langchain
+```
+
+## One line
+
+```python
+from langchain.agents import create_agent
+from needlepath_langchain import NeedlepathMiddleware
+
+agent = create_agent(
+    model,
+    tools,
+    middleware=[NeedlepathMiddleware(operating_point="np-2026-07-r2")],
+)
+```
+
+The key comes from `NEEDLEPATH_API_KEY`, the operating point is pinned
+explicitly, and if the service is slow, down, or stands down, the agent runs on
+its original context and says so in message metadata.
+
+## The two seams
+
+### `wrap_tool_call` — the sweet spot
+
+The only documented, first-class, mutate-the-tool-result seam in the ecosystem.
+A tool returns 40 KB of JSON; what enters the message list is the part of it that
+answers the current step.
+
+Engages only when a single tool result exceeds `tool_result_max_tokens` (default
+2000), which is also the budget. Below it, no call is made and nothing is
+touched.
+
+### `wrap_model_call` — selection over the accumulated history
+
+Before every model call, the tool results already in the history are selected
+against the *current* task. A result that mattered three steps ago and does not
+matter now collapses to a placeholder; the one that matters is excerpted
+verbatim. Engages only when the prunable history exceeds `history_max_tokens`
+(default 8000).
+
+Non-destructive by construction: `request.override(messages=…)` returns a new
+request and never touches `request.state`, so the graph keeps the full history
+and only the model sees the selection.
+
+Both seams are on by default and independently switchable
+(`select_tool_results=`, `select_history=`).
+
+## Configuration
+
+| Parameter | Default | What it does |
+|---|---|---|
+| `operating_point` | — | **Required.** Immutable label. Also `NEEDLEPATH_OPERATING_POINT`. |
+| `shadow` | `False` | Measure and report; never apply. |
+| `enabled` | `True` | Kill switch. Needs no credentials when `False`. |
+| `select_tool_results` / `select_history` | `True` | The two seams. |
+| `tool_result_max_tokens` | `2000` | Trigger *and* budget for one tool result. |
+| `history_max_tokens` | `8000` | Trigger *and* budget for the history. |
+| `preserve_recent` | `2` | Trailing messages never rewritten. |
+| `include_ai_messages` / `include_human_messages` | `False` | Widen beyond tool results. |
+| `placeholder` | see source | Replaces an unselected tool result. |
+| `name` | class name | **Must be unique** if you register two instances. |
+
+Any other keyword is forwarded to the core client (`base_url`, `api_key`,
+`timeout`, `max_retries`, …).
+
+## Two invariants, and why they cost tokens
+
+**A message is never removed, only rewritten.** LangGraph's
+`_validate_chat_history` raises when an `AIMessage` carrying `tool_calls` loses
+its matching `ToolMessage`, and every provider rejects the same shape:
+
+```
+ValueError: Found AIMessages with tool_calls that do not have a corresponding ToolMessage.
+```
+
+A selector that drops messages has to reason about tool-call pairing on every
+path and get it right every time. One that only rewrites content in place cannot
+break the pairing at all — the message objects, their ids and their
+`tool_call_id`s are exactly what they were. We take the second option and give up
+the savings from deleting message envelopes.
+
+**A rewrite never grows a message and never empties one.** An excerpt longer than
+what it replaces, or an empty excerpt applied to a non-empty message, is refused
+here rather than trusted upstream.
+
+By default only `ToolMessage`s are rewritten. `SystemMessage` never is, on any
+setting. An `AIMessage` carrying `tool_calls` never is: its content is usually
+empty and the part that matters is the call list.
+
+## Fail open
+
+Every error path passes the original context through, with the reason recorded in
+`response_metadata["needlepath"]`:
+
+```python
+{
+    "applied": False,
+    "reason": "engine_fallback",
+    "request_id": "np-…",
+    "tokens_before": 8400,
+    "tokens_saved": 0,
+    "gate_reason": "standdown:flat_gap",
+}
+```
+
+`reason` is an open enum. Treat an unrecognized value as "not applied".
+
+`middleware.stats.as_dict()` aggregates the same counters — the input to a
+shadow report.
+
+## Sync **and** async
+
+Both variants of both hooks are implemented, and that is not optional:
+`create_agent` puts a middleware in *both* the sync and async hook lists if it
+implements *either*, specifically so the base class's `NotImplementedError`
+fires. A middleware that implements only the sync hooks raises under `ainvoke()`.
+
+If you pass your own `client=` without an `async_client=`, the async hooks run it
+on the default executor rather than blocking the event loop.
+
+## Lifecycle
+
+A middleware is normally wired up once and lives as long as the agent, so you
+never need to close it. If you construct one per request or per test, call
+`middleware.close()` / `await middleware.aclose()` to release the connection
+pools. Clients you passed in with `client=` / `async_client=` are yours and are
+never closed for you.
+
+## LangGraph
+
+Same package, not a second distribution.
+
+```python
+from langgraph.prebuilt import create_react_agent
+from needlepath_langchain.langgraph import needlepath_pre_model_hook
+
+agent = create_react_agent(
+    model,
+    tools,
+    pre_model_hook=needlepath_pre_model_hook(operating_point="np-2026-07-r2"),
+)
+```
+
+**Prefer `create_agent` + `NeedlepathMiddleware` if you can.** `pre_model_hook`
+exists only on `create_react_agent`, which is deprecated since LangGraph v1.0 and
+slated for removal in v2.0.
+
+| Mechanism | Graph state | Verdict |
+|---|---|---|
+| `RemoveMessage` → `add_messages` | **destroys** the removed messages | incompatible with selection |
+| `pre_model_hook` → `llm_input_messages` | `messages` untouched | compatible |
+| `create_agent` + `wrap_model_call` | nothing written at all | **preferred** |
+
+`add_messages` is the only writer of the `messages` channel and its removal path
+physically drops entries. Once it runs, they are gone from the live thread and
+every checkpoint after it. That is a *history compaction* primitive — what
+`SummarizationMiddleware` uses it for — not a *selection* primitive. Selection is
+per-call by definition: the record that does not matter at step 7 may be the one
+that matters at step 9.
+
+### Four sharp edges, all handled
+
+1. **`llm_input_messages` is a persisted channel, not a transient.** It lands in
+   the checkpoint, so every turn adds a full copy of the selection to the
+   checkpoint blob. Real storage on long threads.
+2. **Stale-selection leak.** It is a `LastValue` channel that survives between
+   `invoke()` calls. A hook that *conditionally* skips writing it silently reuses
+   the previous turn's selection. This hook writes it **unconditionally, every
+   pass**.
+3. **An empty selection silently degrades to the full history.** The reader does
+   `state.get("llm_input_messages") or state.get("messages")`, and `[]` is falsy.
+   This hook never emits an empty list.
+4. **`_validate_chat_history` runs on your selection.** Covered by the
+   never-remove-a-message invariant above.
+
+### One caveat this package cannot fix
+
+With `response_format` on `create_react_agent`, the structured-output node reads
+`state["messages"]` directly and does **not** consult `llm_input_messages`. That
+call sees the full history, not your selection. Price your savings accordingly.
+
+## Positioning
+
+LangChain ships `ContextEditingMiddleware` with a `ClearToolUsesEdit` strategy
+in-tree and free, which clears the oldest tool results once a token trigger
+trips. This is not a competitor to "can something prune tool results" — it is a
+different answer to *which bytes should survive*. We select verbatim against the
+current task rather than clearing by age, stand down when trimming would not pay,
+and report what was actually saved.
+
+If clearing by age is enough for your workload, use the free one.
+
+## Tested against
+
+`langchain==1.3.14`, `langchain-core==1.5.3`, `langgraph==1.2.10`. Floor
+`>=1.2.9` (the first release where `ToolCallRequest`, `ModelCallResult` and
+`ExtendedModelResponse` are all importable from the public
+`langchain.agents.middleware` package and `ModelRequest.system_message` is
+stable). Capped at `<2.0.0`; CI runs against the newest 1.x minor.