sbxloop 0.4.4__tar.gz → 0.4.5__tar.gz

{sbxloop-0.4.4 → sbxloop-0.4.5}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: sbxloop
-Version: 0.4.4
+Version: 0.4.5
 Summary: Agentic loop orchestration on Docker Sandboxes (sbx) with isolated credential domains
 Project-URL: Homepage, https://github.com/brettbergin/sbxloop
 Project-URL: Repository, https://github.com/brettbergin/sbxloop

{sbxloop-0.4.4 → sbxloop-0.4.5}/src/sbxloop/_version.py

@@ -18,7 +18,7 @@ version_tuple: tuple[int | str, ...]
 commit_id: str | None
 __commit_id__: str | None
 
-__version__ = version = '0.4.4'
-__version_tuple__ = version_tuple = (0, 4, 4)
+__version__ = version = '0.4.5'
+__version_tuple__ = version_tuple = (0, 4, 5)
 
 __commit_id__ = commit_id = None

{sbxloop-0.4.4 → sbxloop-0.4.5}/src/sbxloop/engine/prompts/execute.md

@@ -9,6 +9,20 @@ the host so the user receives everything you put in it. Write all outputs and
 artifacts here — files created anywhere else are lost when the sandbox is
 destroyed.
 
+## Environment notes
+
+- Debian/Ubuntu VM. The system Python is externally managed (PEP 668):
+  bare `pip install X` fails. For Python dependencies create a virtualenv
+  first — `python3 -m venv .venv && .venv/bin/pip install X` — and run
+  project commands through `.venv/bin/...`.
+- If a tool or apt package is missing, you have passwordless sudo:
+  `sudo apt-get install -y <package>`.
+- Network egress is allowlisted. PyPI, GitHub, and apt mirrors are
+  reachable; other hosts (npm registry, arbitrary APIs) may not be. If a
+  download times out repeatedly, say so in your summary instead of
+  retrying forever — the allowlist is user configuration, not something
+  you can change.
+
 ## Overall outcome
 
 $outcome

{sbxloop-0.4.4 → sbxloop-0.4.5}/src/sbxloop/engine/prompts/plan.md

@@ -32,4 +32,11 @@ Respond with exactly one fenced JSON block:
 
 Steps must be specific enough that an executor with no other context can
 follow them. Include the task's own verification ideas in `verify_commands`.
+
+Environment facts to plan around: Debian/Ubuntu VM; the system Python is
+externally managed (PEP 668), so Python dependencies belong in a project
+virtualenv (`python3 -m venv .venv`) and commands — including your
+`verify_commands` — should use `.venv/bin/...` paths; missing apt packages
+can be installed with passwordless sudo; network egress is allowlisted
+(PyPI, GitHub, and apt mirrors are reachable — other registries may not be).
 $retry_context