conduct-cli 0.8.5__tar.gz → 0.8.7__tar.gz

{conduct_cli-0.8.5 → conduct_cli-0.8.7}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: conduct-cli
-Version: 0.8.5
+Version: 0.8.7
 Summary: CLI for Conduct AI — secure, govern, install agents, manage projects, run tests
 Author-email: Conduct AI <hello@conductai.ai>
 License: MIT

{conduct_cli-0.8.5 → conduct_cli-0.8.7}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "conduct-cli"
-version = "0.8.5"
+version = "0.8.7"
 description = "CLI for Conduct AI — secure, govern, install agents, manage projects, run tests"
 readme = "README.md"
 license = { text = "MIT" }

{conduct_cli-0.8.5 → conduct_cli-0.8.7}/src/conduct_cli/api.py

@@ -69,17 +69,27 @@ def req_text(method: str, url: str, hdrs: dict, body_text: str, timeout: int = 3
 
 
 def stream(url: str, hdrs=None):
-    """Yield parsed SSE data dicts."""
+    """Yield parsed SSE data dicts.
+
+    Uses a socket read timeout to detect stalled streams. Server sends
+    ': keepalive' pings every 15s, so a 60s timeout is safe.
+    """
     r = urllib.request.Request(url, headers=hdrs or {})
     try:
-        resp = urllib.request.urlopen(r)
+        resp = urllib.request.urlopen(r, timeout=60)
     except urllib.error.HTTPError as e:
         msg = e.read().decode()
         raise RuntimeError(f"Stream {e.code}: {msg}")
 
     buf = b""
     while True:
-        chunk = resp.read(1)
+        try:
+            chunk = resp.read(1)
+        except socket.timeout:
+            raise RuntimeError(
+                "Stream stalled (no data for 60s). The run may still be executing on the server — "
+                "check `conduct runs list` or the UI."
+            )
         if not chunk:
             break
         buf += chunk

conduct_cli-0.8.7/src/conduct_cli/guard_policy.md

@@ -0,0 +1,16 @@
+At the start of every conversation:
+- Call `guard_activity` ONCE with a one-line summary of what the user is asking.
+
+Then, for the request itself:
+- Call `guard_check` ONCE per intent — not per file, per command, or per edit.
+- Re-check only when scope changes (reads → writes, local → network, or a new task).
+- If BLOCKED: stop and explain the policy rule to the user.
+- If WARNING: proceed but surface the warning inline.
+- If the response is `ok` or empty: proceed silently. Do NOT narrate it in the chat.
+
+Example:
+1. User asks to fix a bug → call `guard_activity` once with the summary.
+2. Before starting the code changes → call `guard_check` once with the intent (e.g. `write_file`, `bash`).
+3. Do NOT re-check for every subsequent read or edit in the same task.
+
+Never write secrets to files or output. Never send PII to external endpoints.

{conduct_cli-0.8.5 → conduct_cli-0.8.7}/src/conduct_cli.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: conduct-cli
-Version: 0.8.5
+Version: 0.8.7
 Summary: CLI for Conduct AI — secure, govern, install agents, manage projects, run tests
 Author-email: Conduct AI <hello@conductai.ai>
 License: MIT

conduct_cli-0.8.5/src/conduct_cli/guard_policy.md

@@ -1,16 +0,0 @@
-At the start of every conversation:
-- Call `guard_activity` once with a one-line summary of the user's request.
-
-Before every shell command, file write, network request, API call, or code change:
-- Call `guard_check` with the proposed action and parameters.
-- If BLOCKED: stop and explain the policy rule.
-- If WARNING: proceed and surface the warning.
-- If ALLOWED: proceed normally.
-
-Example:
-1. User asks to fix a bug → call `guard_activity` once.
-2. Before reading files or running tests → call `guard_check`.
-3. Before editing code → call `guard_check` again.
-
-Never write secrets to files or output.
-Never send PII to external endpoints.