b3os-langchain 0.1.0__tar.gz

b3os_langchain-0.1.0/.gitignore

@@ -0,0 +1,6 @@
+.venv/
+__pycache__/
+*.egg-info/
+dist/
+.mypy_cache/
+.pytest_cache/

b3os_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.

b3os_langchain-0.1.0/PKG-INFO

@@ -0,0 +1,110 @@
+Metadata-Version: 2.5
+Name: b3os-langchain
+Version: 0.1.0
+Summary: LangChain integrations for B3OS beta: a Deep Agents sandbox backend on a B3OS sandbox.
+Project-URL: Documentation, https://docs.beta.b3os.org
+Project-URL: Source, https://github.com/b3-fun/b3os-beta
+Project-URL: Homepage, https://beta.b3os.org
+License-Expression: Apache-2.0
+License-File: LICENSE
+Classifier: Programming Language :: Python :: 3
+Classifier: Typing :: Typed
+Requires-Python: >=3.11
+Requires-Dist: b3os<0.3,>=0.2.1
+Requires-Dist: deepagents<0.8,>=0.7.38
+Provides-Extra: dev
+Requires-Dist: mypy>=1.13; extra == 'dev'
+Requires-Dist: pytest>=8; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# b3os-langchain
+
+LangChain integrations for B3OS beta. Today one: `B3OSSandbox`, a [Deep Agents](https://github.com/langchain-ai/deepagents)
+sandbox backend, so a Deep Agent's shell and files live in a B3OS sandbox (a Firecracker microVM) while its model
+can be served by the same node (`/v1/infer`).
+
+```sh
+pip install b3os-langchain langchain-openai
+```
+
+It brings the B3OS SDK (`b3os` 0.2.1 or later in 0.2) and `deepagents`. From a checkout of this repository:
+`pip install ./packages/sdk-python ./packages/adapters-python/langchain`.
+
+```python
+import os
+
+from b3os import B3OS
+from deepagents import create_deep_agent
+from langchain_b3os import B3OSSandbox
+from langchain_openai import ChatOpenAI
+
+sbx = B3OS().sandboxes.create({"template": "base"})          # B3OS_API_KEY from the environment
+backend = B3OSSandbox(sandbox=sbx)
+model = ChatOpenAI(model="b3os/qwen3.5-9b", base_url="https://beta-api.b3os.org/v1/infer", api_key=os.environ["B3OS_API_KEY"],
+                   profile={"max_input_tokens": 32768})                        # context_length in /v1/infer/models
+agent = create_deep_agent(model=model, system_prompt="You are a Python coding assistant with sandbox access.", backend=backend)
+try:
+    result = agent.invoke({"messages": [{"role": "user", "content": "Create a small Python package and run pytest"}]})
+finally:
+    sbx.kill()
+```
+
+## What it implements
+
+`B3OSSandbox(sandbox=..., timeout=1800, user="root", cwd="/")` subclasses `deepagents.backends.sandbox.BaseSandbox` (read at
+deepagents 0.7.38) and implements its four abstract members over the B3OS Python SDK's `Sandbox` handle:
+
+| Member | B3OS call | Behaviour |
+|---|---|---|
+| `id` | `sbx.id` | The `sbx_...` id |
+| `execute(command, timeout=None)` | `sbx.exec(["/bin/bash", "-c", command], cwd="/", timeout_ms=...)` | Runs in `/`, where Deep Agents roots a relative file path (`write_file("pkg/a.py")` is `/pkg/a.py`), so `mkdir pkg` and `cd pkg` reach the same files; `cwd="/workspace"` (B3OS's own default) for an agent told to work there. Output is stdout, then stderr on its own line. Up to 60 s it is one buffered call; longer (and the default 30 minutes) streams. `timeout=None` uses the backend's default, `0` and anything over an hour are held to B3OS's one-hour cap. A command killed at its timeout returns exit code 124 and `Command timed out after N seconds` before its partial output; one a signal ended returns 128 + n. `truncated` is true when B3OS dropped output (a buffered call returns at most 1 MiB of each stream) or a streamed command wrote more than 1 MiB to one stream (the SDK keeps the first 1 MiB as it arrives, `max_output_bytes`, and drops the rest) |
+| `upload_files(files)` | `sbx.files.write(path, data, mkdir=True)` per file | Bytes as given (binary is fine); parent directories made |
+| `download_files(paths)` | `sbx.files.read(path)` per path | Bytes as stored |
+
+File errors are per file, in input order, never raised: a relative path (or one with a NUL byte or over 4,096
+bytes) is `invalid_path` without a call; `file_not_found`, `is_directory`, `permission_denied` and `invalid_path`
+map from the files API's answers; anything else is `"<code>: <detail>"`, for example
+`file_too_large: ...` past the 64 MiB transfer cap. Absolute paths anywhere in the sandbox are allowed, as in the
+partner backends: the sandbox is the boundary. Once the sandbox is gone (`sandbox_not_found`, `sandbox_not_running`)
+the rest of a batch gets the same error without further calls, and `execute` raises the SDK's `B3OSError`.
+When a command's answer is lost on the way rather than refused (`stream_interrupted` on a long stream, the SDK's
+idle `timeout`, `connection_error`), `execute` does not raise, since Deep Agents' execute tool would end the whole
+run: it returns no exit code and one JSON line, `{"error": "B3OS lost this command's answer (<code>: <detail>,
+request req_...) ..."}`, which BaseSandbox's `ls`, `read`, `edit`, `grep` and `glob` read as a failure.
+
+The other file tools (`ls`, `read`, `write`, `edit`, `delete`, `grep`, `glob`) are BaseSandbox's, built on
+`execute` and `upload_files`; async methods are the protocol's thread-backed defaults, as in the Modal, Daytona and
+Runloop backends. Capture-to-file offload of large output (`enable_capture_offload`) stays off, BaseSandbox's
+default. The backend never creates or deletes a sandbox: you own its lifetime (`sbx.kill()`, `timeout_s` at create).
+
+## Limits and B3OS gaps
+
+- Commands run as root by default; B3OS's own default is `user` (uid 1000). Deep Agents
+  writes its own files under `/` (`/large_tool_results/` when a tool result is too large, `/conversation_history/`
+  when it summarizes), and BaseSandbox's `write` and `edit` make and change files through `execute`. As `user`
+  those fail with `Permission denied` on `/`, while the files API, which writes as root, succeeds: the two halves
+  of the sandbox act as different users. `user="user"` is there for agents that keep to `/workspace` and `/tmp`.
+- Deep Agents summarizes a long conversation only when it knows the model's context size. LangChain has no
+  profile for `b3os/qwen3.5-9b`, so pass it: `ChatOpenAI(..., profile={"max_input_tokens": 32768})`
+  (`context_length` in `GET /v1/infer/models`). Without it a long run ends in `400 context_length_exceeded`.
+- B3OS answers "is a directory" and "permission denied" as the same code, `path_invalid`; the backend tells them
+  apart by the `detail` text.
+- No single command runs longer than an hour (B3OS's streamed exec cap).
+- Past 1 MiB of a stream nothing more is kept, so `yes` costs the agent's process 1 MiB, not an hour of output:
+  the backend passes `max_output_bytes` to `Sandbox.exec`, and a broken stream's error carries its request id
+  (both from b3os 0.2.1, the SDK floor).
+
+## Development
+
+```sh
+cd packages/adapters-python/langchain
+uv run --python 3.12 --locked --extra dev pytest -q      # the SDK's real handle over a fake API; no network
+uv run --python 3.12 --locked --extra dev mypy --strict  # also on --python 3.11
+```
+
+The tests run on the SDK in this repository; `.github/workflows/release.yml` runs them again against the b3os wheel
+it publishes beside this package. `uv.lock` is resolved with nothing newer than 2026-11-13 15:00 UTC
+(`[tool.uv] exclude-newer`) and the SDK from `packages/sdk-python`.
+The production proof (Deep Agents' own sandbox example on beta-api, model on `/v1/infer`) is in `proof/`, its
+results in `bench/sandboxes/results/20261114T155056Z-deepagents-prod/`. The docs page is prepared in
+`NOTES/integrations/langchain.mdx` until the package is published (`NOTES/integrations/README.md`).

b3os_langchain-0.1.0/README.md

@@ -0,0 +1,91 @@
+# b3os-langchain
+
+LangChain integrations for B3OS beta. Today one: `B3OSSandbox`, a [Deep Agents](https://github.com/langchain-ai/deepagents)
+sandbox backend, so a Deep Agent's shell and files live in a B3OS sandbox (a Firecracker microVM) while its model
+can be served by the same node (`/v1/infer`).
+
+```sh
+pip install b3os-langchain langchain-openai
+```
+
+It brings the B3OS SDK (`b3os` 0.2.1 or later in 0.2) and `deepagents`. From a checkout of this repository:
+`pip install ./packages/sdk-python ./packages/adapters-python/langchain`.
+
+```python
+import os
+
+from b3os import B3OS
+from deepagents import create_deep_agent
+from langchain_b3os import B3OSSandbox
+from langchain_openai import ChatOpenAI
+
+sbx = B3OS().sandboxes.create({"template": "base"})          # B3OS_API_KEY from the environment
+backend = B3OSSandbox(sandbox=sbx)
+model = ChatOpenAI(model="b3os/qwen3.5-9b", base_url="https://beta-api.b3os.org/v1/infer", api_key=os.environ["B3OS_API_KEY"],
+                   profile={"max_input_tokens": 32768})                        # context_length in /v1/infer/models
+agent = create_deep_agent(model=model, system_prompt="You are a Python coding assistant with sandbox access.", backend=backend)
+try:
+    result = agent.invoke({"messages": [{"role": "user", "content": "Create a small Python package and run pytest"}]})
+finally:
+    sbx.kill()
+```
+
+## What it implements
+
+`B3OSSandbox(sandbox=..., timeout=1800, user="root", cwd="/")` subclasses `deepagents.backends.sandbox.BaseSandbox` (read at
+deepagents 0.7.38) and implements its four abstract members over the B3OS Python SDK's `Sandbox` handle:
+
+| Member | B3OS call | Behaviour |
+|---|---|---|
+| `id` | `sbx.id` | The `sbx_...` id |
+| `execute(command, timeout=None)` | `sbx.exec(["/bin/bash", "-c", command], cwd="/", timeout_ms=...)` | Runs in `/`, where Deep Agents roots a relative file path (`write_file("pkg/a.py")` is `/pkg/a.py`), so `mkdir pkg` and `cd pkg` reach the same files; `cwd="/workspace"` (B3OS's own default) for an agent told to work there. Output is stdout, then stderr on its own line. Up to 60 s it is one buffered call; longer (and the default 30 minutes) streams. `timeout=None` uses the backend's default, `0` and anything over an hour are held to B3OS's one-hour cap. A command killed at its timeout returns exit code 124 and `Command timed out after N seconds` before its partial output; one a signal ended returns 128 + n. `truncated` is true when B3OS dropped output (a buffered call returns at most 1 MiB of each stream) or a streamed command wrote more than 1 MiB to one stream (the SDK keeps the first 1 MiB as it arrives, `max_output_bytes`, and drops the rest) |
+| `upload_files(files)` | `sbx.files.write(path, data, mkdir=True)` per file | Bytes as given (binary is fine); parent directories made |
+| `download_files(paths)` | `sbx.files.read(path)` per path | Bytes as stored |
+
+File errors are per file, in input order, never raised: a relative path (or one with a NUL byte or over 4,096
+bytes) is `invalid_path` without a call; `file_not_found`, `is_directory`, `permission_denied` and `invalid_path`
+map from the files API's answers; anything else is `"<code>: <detail>"`, for example
+`file_too_large: ...` past the 64 MiB transfer cap. Absolute paths anywhere in the sandbox are allowed, as in the
+partner backends: the sandbox is the boundary. Once the sandbox is gone (`sandbox_not_found`, `sandbox_not_running`)
+the rest of a batch gets the same error without further calls, and `execute` raises the SDK's `B3OSError`.
+When a command's answer is lost on the way rather than refused (`stream_interrupted` on a long stream, the SDK's
+idle `timeout`, `connection_error`), `execute` does not raise, since Deep Agents' execute tool would end the whole
+run: it returns no exit code and one JSON line, `{"error": "B3OS lost this command's answer (<code>: <detail>,
+request req_...) ..."}`, which BaseSandbox's `ls`, `read`, `edit`, `grep` and `glob` read as a failure.
+
+The other file tools (`ls`, `read`, `write`, `edit`, `delete`, `grep`, `glob`) are BaseSandbox's, built on
+`execute` and `upload_files`; async methods are the protocol's thread-backed defaults, as in the Modal, Daytona and
+Runloop backends. Capture-to-file offload of large output (`enable_capture_offload`) stays off, BaseSandbox's
+default. The backend never creates or deletes a sandbox: you own its lifetime (`sbx.kill()`, `timeout_s` at create).
+
+## Limits and B3OS gaps
+
+- Commands run as root by default; B3OS's own default is `user` (uid 1000). Deep Agents
+  writes its own files under `/` (`/large_tool_results/` when a tool result is too large, `/conversation_history/`
+  when it summarizes), and BaseSandbox's `write` and `edit` make and change files through `execute`. As `user`
+  those fail with `Permission denied` on `/`, while the files API, which writes as root, succeeds: the two halves
+  of the sandbox act as different users. `user="user"` is there for agents that keep to `/workspace` and `/tmp`.
+- Deep Agents summarizes a long conversation only when it knows the model's context size. LangChain has no
+  profile for `b3os/qwen3.5-9b`, so pass it: `ChatOpenAI(..., profile={"max_input_tokens": 32768})`
+  (`context_length` in `GET /v1/infer/models`). Without it a long run ends in `400 context_length_exceeded`.
+- B3OS answers "is a directory" and "permission denied" as the same code, `path_invalid`; the backend tells them
+  apart by the `detail` text.
+- No single command runs longer than an hour (B3OS's streamed exec cap).
+- Past 1 MiB of a stream nothing more is kept, so `yes` costs the agent's process 1 MiB, not an hour of output:
+  the backend passes `max_output_bytes` to `Sandbox.exec`, and a broken stream's error carries its request id
+  (both from b3os 0.2.1, the SDK floor).
+
+## Development
+
+```sh
+cd packages/adapters-python/langchain
+uv run --python 3.12 --locked --extra dev pytest -q      # the SDK's real handle over a fake API; no network
+uv run --python 3.12 --locked --extra dev mypy --strict  # also on --python 3.11
+```
+
+The tests run on the SDK in this repository; `.github/workflows/release.yml` runs them again against the b3os wheel
+it publishes beside this package. `uv.lock` is resolved with nothing newer than 2026-11-13 15:00 UTC
+(`[tool.uv] exclude-newer`) and the SDK from `packages/sdk-python`.
+The production proof (Deep Agents' own sandbox example on beta-api, model on `/v1/infer`) is in `proof/`, its
+results in `bench/sandboxes/results/20261114T155056Z-deepagents-prod/`. The docs page is prepared in
+`NOTES/integrations/langchain.mdx` until the package is published (`NOTES/integrations/README.md`).

b3os_langchain-0.1.0/biome.json

@@ -0,0 +1,20 @@
+{
+  "$schema": "https://biomejs.dev/schemas/2.6.3/schema.json",
+  "root": false,
+  "extends": "//",
+  "files": {
+    "includes": [
+      "**",
+      "!.venv",
+      "!**/__pycache__",
+      "!.pytest_cache",
+      "!.mypy_cache",
+      "!**/node_modules",
+      "!**/dist",
+      "!**/*.md",
+      "!**/*.mdx",
+      "!**/*.yaml",
+      "!**/*.yml"
+    ]
+  }
+}

b3os_langchain-0.1.0/proof/README.md

@@ -0,0 +1,28 @@
+# Production proof of b3os-langchain
+
+Runs on dev-h200 against beta-api.b3os.org through the public edge, with the bench key, the model on the node's
+own `/v1/infer` (`b3os/qwen3.5-9b` through `langchain_openai.ChatOpenAI`), so the model, the sandbox and the tools
+are on one node. Three steps, one sandbox each, run one after the other; every sandbox is killed by its step and
+`run.sh` lists the organization's running sandboxes before and after (`sweep.json`).
+
+| Step | Script | What it shows |
+|---|---|---|
+| `probe` | `probe.py` | Each protocol call on a real sandbox: exit codes and stderr (buffered and streamed), a timeout, a signal, truncation at 1 MiB, bytes that are not UTF-8, a binary file both ways, a directory, a missing file, a path through a file, paths outside `/workspace`, BaseSandbox's own `write`/`read`/`edit`/`ls`/`grep`/`glob`/`delete`, and every call after the sandbox is gone; buffered against streamed `execute("true")` |
+| `example` | `run_example.py` running `sandbox_example.py` | Deep Agents' own sandbox example (docs.langchain.com, Sandboxes, Basic usage, Modal tab: `upstream_modal_example.py`, from langchain-ai/docs at 04d4d4a, `src/snippets/sandboxes-basic-tabs-py.mdx`) with only the sandbox lines and the model line changed (`sandbox_example.diff` in the results). The runner wraps `B3OSSandbox.execute` to log commands and `b3os.Sandbox.kill` to list the files the agent left and rerun its last pytest command before the example deletes the sandbox |
+| `loop` | `loop_task.py` | A task that needs the loop: write `/workspace/stats.py`, run it into `out.txt`, read that back, run a seeded test file whose `test_empty_list` checks an error message the task does not state, and fix `stats.py` until the tests pass |
+
+Install: one virtualenv from `requirements-proof.txt` (`uv pip install --require-hashes --only-binary :all:`,
+compiled with nothing newer than 2026-11-13 15:00 UTC; the command is in `requirements-proof.in`), then this tree's
+`packages/sdk-python` and `packages/adapters-python/langchain` with `--no-deps`.
+
+    ops/sync.sh deepagents
+    ops/box.sh deepagents -- sh -c 'export B3OS_API_KEY="$(cat /opt/b3os/etc-dev/credentials/bench-api-key)";
+      PROOF_COMMIT=<commit> bash packages/adapters-python/langchain/proof/run.sh'
+
+Results go to `/opt/b3os/run/deepagents/<UTC ts>-deepagents-prod/` (copied into
+`bench/sandboxes/results/`): `probe.json`, `example-attempt<n>.json`, `loop-attempt<n>.json` (up to three attempts each, stopping at the first pass, and reported as k of n attempts
+in `meta.json`: "PASS, 1 of 2 attempts passed" means the first failed; the example's pytest check reads pytest's
+summary line from the command's whole output, not from the 1,500 characters recorded; each with its wire log: method, path,
+status, request id and `Server-Timing` of every call, the model's tool calls; no header or body, scrubbed of keys),
+their logs, `pip-freeze.txt`, `requirements-proof.txt`, `sandbox_example.diff`, `sweep.json` and `meta.json`.
+A step starts only inside a box window (`ops/windows.json`) and while `/proc/pressure/io` full avg10 is at most 40.