recall-langgraph 0.1.0__tar.gz

recall_langgraph-0.1.0/.gitignore

@@ -0,0 +1,13 @@
+__pycache__/
+*.pyc
+.pytest_cache/
+.ruff_cache/
+.venv/
+python/dist/
+python/build/
+*.egg-info/
+
+# The LiveKit example: provider keys, and the local Recall database with its key
+examples/livekit/.env
+examples/livekit/memory-api-key
+recall-data/

recall_langgraph-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 2026 Polign, Inc.
+
+   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.

recall_langgraph-0.1.0/PKG-INFO

@@ -0,0 +1,209 @@
+Metadata-Version: 2.5
+Name: recall-langgraph
+Version: 0.1.0
+Summary: Resume LangGraph agents from their own records, backed by Recall by Polign
+Project-URL: Homepage, https://polign.com
+Project-URL: Documentation, https://polign.com/integrations.html
+Project-URL: Repository, https://github.com/Polign/polign
+Project-URL: Issues, https://github.com/Polign/polign/issues
+Author: Polign
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: agent memory,langchain,langgraph,polign,recall,resume
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Requires-Python: >=3.10
+Requires-Dist: langchain-core<2,>=1.0
+Requires-Dist: langgraph<2,>=1.0
+Requires-Dist: polign-recall>=0.4.0
+Description-Content-Type: text/markdown
+
+# recall-langgraph
+
+Resume [LangGraph](https://github.com/langchain-ai/langgraph) agents from
+their own records, backed by [Recall by Polign](https://polign.com/recall.html).
+
+A long-running agent that crashes, gets rescheduled, or moves to another
+machine usually starts over, or restores an exact snapshot of its state. With
+this package it picks up where it left off from what it wrote down instead:
+while it works, it keeps a working state (its goal, plan, progress and
+decisions) and pointers to where its work lives, and every message of the run
+is recorded. The next process that opens the same agent id gets a fresh
+starting context built from those records, sized to a token budget.
+
+This sits beside your checkpointer, not in place of it. LangGraph's
+checkpointer still handles threads and interrupts however you configure it.
+
+```bash
+pip install recall-langgraph
+```
+
+pip also brings the [`polign_db`](https://pypi.org/project/polign-db/)
+package with the `polign` CLI and `polign-server` binaries for Linux, macOS
+and Windows, so there is no separate database to download.
+
+## Usage with create_react_agent
+
+```python
+from langchain_openai import ChatOpenAI
+from langgraph.prebuilt import create_react_agent
+from recall_langgraph import RecallResume, recall_tools
+
+with RecallResume("billing-migrator", local_dir="./recall-data") as resume:
+    agent = create_react_agent(
+        ChatOpenAI(model="gpt-4.1"),
+        tools=[*your_tools, *recall_tools(resume)],
+        prompt=(
+            "You move the billing service to the v2 API. Keep your working state "
+            "current with update_working_state, and call milestone when a step is done."
+        ),
+        pre_model_hook=resume.pre_model_hook,
+        post_model_hook=resume.post_model_hook,
+    )
+    agent.invoke({"messages": [("user", "Carry on with the migration.")]})
+```
+
+Run it, stop it halfway, and run it again: the second run starts from the
+working state, pointers and recent turns the first one wrote.
+
+What happens:
+
+1. Entering the `with` block resumes the agent. It takes a lease on the id,
+   so only one process acts for the agent at a time, and reads back its
+   records. The first time an id is used, it starts fresh.
+2. Before every model call, `pre_model_hook` puts one `SystemMessage` in
+   front of the messages, the briefing: the working state, pointers to the
+   work, relevant memories, and the most recent turns, within
+   `token_budget`. It goes to the model as `llm_input_messages`, so the
+   graph's `messages` state never holds it.
+3. The hooks record each new message once, in order, as a turn: human
+   messages before the model call, the model's reply right after it, and tool
+   results before the next call. A reply with tool calls is recorded with the
+   calls as JSON text. A turn longer than the output threshold is stored whole
+   as an output, and the briefing shows a reference the model can pass to
+   `fetch_output`.
+4. The model keeps its working state current through the tools from
+   `recall_tools`.
+5. Leaving the block (or calling `release()`) hands the lease over, so the
+   next process can resume at once. A process that dies without releasing
+   holds the lease until it expires (60 seconds by default).
+
+Recall never replays old messages into the state: the briefing already
+carries the recent turns as text, and a replayed tool result without its
+matching tool call would be refused by the model API. On a new `thread_id`,
+the resumed run starts from the briefing alone. On the old `thread_id`, a
+persistent checkpointer restores the old messages as well, and nothing is
+recorded twice: each turn keeps its message id, so the first recording after
+a resume skips every restored message up to the last one Recall already has.
+Messages after that one, such as the caller's new input or a reply the dead
+process never recorded, are recorded as usual. The model then sees the
+restored history and the briefing both; start a new thread if you would
+rather it saw only the briefing.
+
+`create_react_agent` is deprecated in LangGraph 1.0 in favor of
+`langchain.agents.create_agent`, but it still ships in `langgraph.prebuilt`
+and the hooks work with it. Use `version="v2"` (the default), since
+`post_model_hook` needs it.
+
+## Your own StateGraph
+
+```python
+from langgraph.graph import START, MessagesState, StateGraph
+
+def call_model(state: MessagesState):
+    return {"messages": [model.invoke(resume.with_briefing(state["messages"]))]}
+
+builder = StateGraph(MessagesState)
+builder.add_node("model", call_model)
+builder.add_node("record", resume.record_node)
+builder.add_edge(START, "model")
+builder.add_edge("model", "record")
+```
+
+- `with_briefing(messages)` returns the messages with the briefing in front,
+  for the model's input, and leaves the state alone.
+- `record_node` records every message not recorded yet and changes nothing.
+  Put it after each node that adds messages. `record(messages)` does the same
+  from your own code.
+- `briefing_node` adds the briefing to the `messages` state itself, once per
+  thread, if you would rather keep it there. Put it first.
+
+The hooks and nodes work with `invoke` and `ainvoke`.
+
+## The tools
+
+| Tool | What the model uses it for |
+|---|---|
+| `update_working_state` | Save its goal, plan, progress, focus, decisions, open questions and notes. Fields it leaves out are kept. |
+| `milestone` | Declare a durable point, such as tests passing. |
+| `fetch_output` | Read a stored output in full by its ref. |
+| `set_pointer` | Record where a piece of work lives: a git branch or commit, an object, an environment, an external item, or a process. |
+
+A failed call comes back to the model as the tool's text. Your own code can
+call `resume.update_working_state`, `resume.milestone`, `resume.fetch_output`
+and `resume.set_pointer`, and `resume.agent` is the underlying
+`polign_recall.ResumedAgent` for everything else (`record_turn`,
+`recent_turns`, `store_output`, `pointers`, `working_state_history`).
+`resume.context` is what the resume returned, and `resume.briefing` its text.
+
+## Options
+
+| Option | Default | What it does |
+|---|---|---|
+| `client` | none | A `polign_recall.Client` opened with `agent=True`, to share one subprocess. Without it, `RecallResume` opens its own and closes it on release. |
+| `local_dir` | none | Keep the database in this directory and run its server (only when `RecallResume` opens its own client) |
+| `env` | process environment | `POLIGN_URL`, `POLIGN_API_KEY` and the rest, for a server you run yourself |
+| `token_budget` | 8000 | Bound on the briefing, in tokens |
+| `lease_ttl` | 60 | Seconds each lease epoch lasts; renewed in the background |
+| `holder` | host, pid and a random suffix | Names this process in lease records |
+| `output_threshold` | 2000 | Turns longer than this many tokens are stored as outputs |
+
+## Errors
+
+If another process holds the agent, resuming raises
+`polign_recall.RecallError` with code `"lease_held"`. Wait and try again, or
+stop. If another process takes the agent over mid-run, the next record fails
+with code `"lease_lost"`, which stops the graph run; this process should
+stop acting for the agent.
+
+Records are append-only. Removing or trimming messages in the graph state
+changes what the model sees, never what was recorded.
+
+## Where the records are stored
+
+`local_dir="./recall-data"` keeps the database on this machine; the first
+process to open the directory starts a `polign-server` for it in the
+background, and later ones share it. Agents that move between machines need
+one shared server: run `polign-server` where they can all reach it
+([Get started](https://polign.com/developers.html) shows how, including
+storing into S3, GCS or Azure) and pass its address through `env` or the
+environment:
+
+```python
+RecallResume(
+    "billing-migrator",
+    env={"POLIGN_URL": "http://memory.internal:23000", "POLIGN_API_KEY": key},
+)
+```
+
+The agent's records live in their own collection next to the memory
+collection (`<collection>_agents`).
+
+## Development
+
+```bash
+cd python/recall-langgraph
+python -m pip install -e . pytest pytest-asyncio
+pytest tests/unit_tests -q                # a fake Recall client, no network
+pytest tests/integration_tests -v         # real polign-server and polign CLI
+```
+
+The integration tests locate the binaries like the other packages' tests do
+(`POLIGN_SERVER`, `POLIGN_SOURCE`, `POLIGN_SERVER_VERSION`, or the latest
+release download) and skip when none is found or when the CLI has no
+`polign mcp -agent`. Both suites drive real compiled graphs with a scripted
+chat model, so no model API key is needed.

recall_langgraph-0.1.0/README.md

@@ -0,0 +1,185 @@
+# recall-langgraph
+
+Resume [LangGraph](https://github.com/langchain-ai/langgraph) agents from
+their own records, backed by [Recall by Polign](https://polign.com/recall.html).
+
+A long-running agent that crashes, gets rescheduled, or moves to another
+machine usually starts over, or restores an exact snapshot of its state. With
+this package it picks up where it left off from what it wrote down instead:
+while it works, it keeps a working state (its goal, plan, progress and
+decisions) and pointers to where its work lives, and every message of the run
+is recorded. The next process that opens the same agent id gets a fresh
+starting context built from those records, sized to a token budget.
+
+This sits beside your checkpointer, not in place of it. LangGraph's
+checkpointer still handles threads and interrupts however you configure it.
+
+```bash
+pip install recall-langgraph
+```
+
+pip also brings the [`polign_db`](https://pypi.org/project/polign-db/)
+package with the `polign` CLI and `polign-server` binaries for Linux, macOS
+and Windows, so there is no separate database to download.
+
+## Usage with create_react_agent
+
+```python
+from langchain_openai import ChatOpenAI
+from langgraph.prebuilt import create_react_agent
+from recall_langgraph import RecallResume, recall_tools
+
+with RecallResume("billing-migrator", local_dir="./recall-data") as resume:
+    agent = create_react_agent(
+        ChatOpenAI(model="gpt-4.1"),
+        tools=[*your_tools, *recall_tools(resume)],
+        prompt=(
+            "You move the billing service to the v2 API. Keep your working state "
+            "current with update_working_state, and call milestone when a step is done."
+        ),
+        pre_model_hook=resume.pre_model_hook,
+        post_model_hook=resume.post_model_hook,
+    )
+    agent.invoke({"messages": [("user", "Carry on with the migration.")]})
+```
+
+Run it, stop it halfway, and run it again: the second run starts from the
+working state, pointers and recent turns the first one wrote.
+
+What happens:
+
+1. Entering the `with` block resumes the agent. It takes a lease on the id,
+   so only one process acts for the agent at a time, and reads back its
+   records. The first time an id is used, it starts fresh.
+2. Before every model call, `pre_model_hook` puts one `SystemMessage` in
+   front of the messages, the briefing: the working state, pointers to the
+   work, relevant memories, and the most recent turns, within
+   `token_budget`. It goes to the model as `llm_input_messages`, so the
+   graph's `messages` state never holds it.
+3. The hooks record each new message once, in order, as a turn: human
+   messages before the model call, the model's reply right after it, and tool
+   results before the next call. A reply with tool calls is recorded with the
+   calls as JSON text. A turn longer than the output threshold is stored whole
+   as an output, and the briefing shows a reference the model can pass to
+   `fetch_output`.
+4. The model keeps its working state current through the tools from
+   `recall_tools`.
+5. Leaving the block (or calling `release()`) hands the lease over, so the
+   next process can resume at once. A process that dies without releasing
+   holds the lease until it expires (60 seconds by default).
+
+Recall never replays old messages into the state: the briefing already
+carries the recent turns as text, and a replayed tool result without its
+matching tool call would be refused by the model API. On a new `thread_id`,
+the resumed run starts from the briefing alone. On the old `thread_id`, a
+persistent checkpointer restores the old messages as well, and nothing is
+recorded twice: each turn keeps its message id, so the first recording after
+a resume skips every restored message up to the last one Recall already has.
+Messages after that one, such as the caller's new input or a reply the dead
+process never recorded, are recorded as usual. The model then sees the
+restored history and the briefing both; start a new thread if you would
+rather it saw only the briefing.
+
+`create_react_agent` is deprecated in LangGraph 1.0 in favor of
+`langchain.agents.create_agent`, but it still ships in `langgraph.prebuilt`
+and the hooks work with it. Use `version="v2"` (the default), since
+`post_model_hook` needs it.
+
+## Your own StateGraph
+
+```python
+from langgraph.graph import START, MessagesState, StateGraph
+
+def call_model(state: MessagesState):
+    return {"messages": [model.invoke(resume.with_briefing(state["messages"]))]}
+
+builder = StateGraph(MessagesState)
+builder.add_node("model", call_model)
+builder.add_node("record", resume.record_node)
+builder.add_edge(START, "model")
+builder.add_edge("model", "record")
+```
+
+- `with_briefing(messages)` returns the messages with the briefing in front,
+  for the model's input, and leaves the state alone.
+- `record_node` records every message not recorded yet and changes nothing.
+  Put it after each node that adds messages. `record(messages)` does the same
+  from your own code.
+- `briefing_node` adds the briefing to the `messages` state itself, once per
+  thread, if you would rather keep it there. Put it first.
+
+The hooks and nodes work with `invoke` and `ainvoke`.
+
+## The tools
+
+| Tool | What the model uses it for |
+|---|---|
+| `update_working_state` | Save its goal, plan, progress, focus, decisions, open questions and notes. Fields it leaves out are kept. |
+| `milestone` | Declare a durable point, such as tests passing. |
+| `fetch_output` | Read a stored output in full by its ref. |
+| `set_pointer` | Record where a piece of work lives: a git branch or commit, an object, an environment, an external item, or a process. |
+
+A failed call comes back to the model as the tool's text. Your own code can
+call `resume.update_working_state`, `resume.milestone`, `resume.fetch_output`
+and `resume.set_pointer`, and `resume.agent` is the underlying
+`polign_recall.ResumedAgent` for everything else (`record_turn`,
+`recent_turns`, `store_output`, `pointers`, `working_state_history`).
+`resume.context` is what the resume returned, and `resume.briefing` its text.
+
+## Options
+
+| Option | Default | What it does |
+|---|---|---|
+| `client` | none | A `polign_recall.Client` opened with `agent=True`, to share one subprocess. Without it, `RecallResume` opens its own and closes it on release. |
+| `local_dir` | none | Keep the database in this directory and run its server (only when `RecallResume` opens its own client) |
+| `env` | process environment | `POLIGN_URL`, `POLIGN_API_KEY` and the rest, for a server you run yourself |
+| `token_budget` | 8000 | Bound on the briefing, in tokens |
+| `lease_ttl` | 60 | Seconds each lease epoch lasts; renewed in the background |
+| `holder` | host, pid and a random suffix | Names this process in lease records |
+| `output_threshold` | 2000 | Turns longer than this many tokens are stored as outputs |
+
+## Errors
+
+If another process holds the agent, resuming raises
+`polign_recall.RecallError` with code `"lease_held"`. Wait and try again, or
+stop. If another process takes the agent over mid-run, the next record fails
+with code `"lease_lost"`, which stops the graph run; this process should
+stop acting for the agent.
+
+Records are append-only. Removing or trimming messages in the graph state
+changes what the model sees, never what was recorded.
+
+## Where the records are stored
+
+`local_dir="./recall-data"` keeps the database on this machine; the first
+process to open the directory starts a `polign-server` for it in the
+background, and later ones share it. Agents that move between machines need
+one shared server: run `polign-server` where they can all reach it
+([Get started](https://polign.com/developers.html) shows how, including
+storing into S3, GCS or Azure) and pass its address through `env` or the
+environment:
+
+```python
+RecallResume(
+    "billing-migrator",
+    env={"POLIGN_URL": "http://memory.internal:23000", "POLIGN_API_KEY": key},
+)
+```
+
+The agent's records live in their own collection next to the memory
+collection (`<collection>_agents`).
+
+## Development
+
+```bash
+cd python/recall-langgraph
+python -m pip install -e . pytest pytest-asyncio
+pytest tests/unit_tests -q                # a fake Recall client, no network
+pytest tests/integration_tests -v         # real polign-server and polign CLI
+```
+
+The integration tests locate the binaries like the other packages' tests do
+(`POLIGN_SERVER`, `POLIGN_SOURCE`, `POLIGN_SERVER_VERSION`, or the latest
+release download) and skip when none is found or when the CLI has no
+`polign mcp -agent`. Both suites drive real compiled graphs with a scripted
+chat model, so no model API key is needed.

recall_langgraph-0.1.0/pyproject.toml

@@ -0,0 +1,47 @@
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+[project]
+name = "recall-langgraph"
+version = "0.1.0"
+description = "Resume LangGraph agents from their own records, backed by Recall by Polign"
+readme = "README.md"
+license = "Apache-2.0"
+license-files = ["LICENSE"]
+requires-python = ">=3.10"
+authors = [{ name = "Polign" }]
+keywords = ["langgraph", "langchain", "agent memory", "resume", "recall", "polign"]
+classifiers = [
+    "Development Status :: 3 - Alpha",
+    "License :: OSI Approved :: Apache Software License",
+    "Intended Audience :: Developers",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3 :: Only",
+    "Topic :: Software Development :: Libraries :: Python Modules",
+]
+dependencies = [
+    "polign-recall>=0.4.0",
+    "langgraph>=1.0,<2",
+    "langchain-core>=1.0,<2",
+]
+
+[project.urls]
+Homepage = "https://polign.com"
+Documentation = "https://polign.com/integrations.html"
+Repository = "https://github.com/Polign/polign"
+Issues = "https://github.com/Polign/polign/issues"
+
+[tool.hatch.build]
+ignore-vcs = true
+
+[tool.hatch.build.targets.sdist]
+include = ["recall_langgraph/", "tests/", "README.md", "LICENSE"]
+exclude = ["**/__pycache__", "**/.pytest_cache"]
+
+[tool.hatch.build.targets.wheel]
+packages = ["recall_langgraph"]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+asyncio_mode = "auto"

recall_langgraph-0.1.0/recall_langgraph/__init__.py

@@ -0,0 +1,20 @@
+"""Recall by Polign for LangGraph.
+
+``RecallResume`` resumes an agent from its own records: its working state,
+pointers to its work, relevant memories and recent turns come back as a
+briefing for the model, and the run's messages are recorded as turns for the
+next resume. ``recall_tools`` gives the model the tools that keep those
+records current. It sits beside your checkpointer; it does not replace it.
+"""
+
+from .resume import BRIEFING_ID, RecallResume
+from .tools import recall_tools
+
+__all__ = ["BRIEFING_ID", "RecallResume", "recall_tools"]
+
+try:
+    from importlib.metadata import version as _version
+
+    __version__ = _version("recall-langgraph")
+except Exception:  # pragma: no cover - source checkout without metadata
+    __version__ = "0.1.0"