hypha-debugger 0.2.3__tar.gz → 0.2.5__tar.gz

{hypha_debugger-0.2.3 → hypha_debugger-0.2.5}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: hypha-debugger
-Version: 0.2.3
+Version: 0.2.5
 Summary: Injectable debugger for Python processes and AI agents, powered by Hypha RPC
 Author: Amun AI AB
 License: MIT
@@ -43,6 +43,41 @@ A lightweight, injectable debugger for web pages and Python processes, powered b
 └─────────────────────────┘         └──────────────┘         └─────────────────────────┘
 ```
 
+## The `hyd` CLI — talk to any remote with minimal overhead
+
+Installing this package also gives you the **`hyd`** command — the low-overhead way
+for an agent (or you) to drive a remote target. Store the connection once as a
+**profile**, then every command is a short `hyd sh '…'` / `hyd js '…'` with the
+connection + working directory remembered — far fewer tokens than re-sending
+authenticated curl. One CLI drives **both** target types:
+
+```bash
+pip install hypha-debugger            # or: pipx install hypha-debugger  (always on PATH)
+
+# Terminal target (a Python process running this debugger):
+hyd profile add box "<py-debugger-service-url>"          # type inferred = terminal
+export HYD_PROFILE=box
+hyd sh 'uname -a && pwd'              # remote shell   | hyd 'ls -la' (bare form)
+hyd py 'import sys; sys.version'      # remote Python via execute_code
+
+# Browser target (a Hypha Navigator web service):
+hyd profile add web "<navigator-service-url>" --type browser
+export HYD_PROFILE=web
+hyd 'document.title'                 # bare form runs JavaScript on a browser profile
+hyd nav 'https://example.com'        # navigate   | hyd shot page.png  (screenshot)
+hyd call get_browser_state           # call any service function
+
+hyd status                           # confirm the connection
+```
+
+The current profile + directory live in the `HYD_PROFILE` / `HYD_CWD` environment
+variables (per-terminal, nothing session-specific on disk); the remote stays
+stateless. If `hyd` isn't on your PATH after a `--user` install, use
+`python -m hypha_debugger.cli` (identical arguments). Run `hyd` with no args for help.
+
+> Any debugger's `GET <service-url>/get_skill_md` includes these same bootstrap
+> instructions, so an AI agent can self-install and connect from the URL alone.
+
 ## JavaScript (Browser)
 
 [![npm](https://img.shields.io/npm/v/hypha-debugger)](https://www.npmjs.com/package/hypha-debugger)

{hypha_debugger-0.2.3 → hypha_debugger-0.2.5}/README.md

@@ -14,6 +14,41 @@ A lightweight, injectable debugger for web pages and Python processes, powered b
 └─────────────────────────┘         └──────────────┘         └─────────────────────────┘
 ```
 
+## The `hyd` CLI — talk to any remote with minimal overhead
+
+Installing this package also gives you the **`hyd`** command — the low-overhead way
+for an agent (or you) to drive a remote target. Store the connection once as a
+**profile**, then every command is a short `hyd sh '…'` / `hyd js '…'` with the
+connection + working directory remembered — far fewer tokens than re-sending
+authenticated curl. One CLI drives **both** target types:
+
+```bash
+pip install hypha-debugger            # or: pipx install hypha-debugger  (always on PATH)
+
+# Terminal target (a Python process running this debugger):
+hyd profile add box "<py-debugger-service-url>"          # type inferred = terminal
+export HYD_PROFILE=box
+hyd sh 'uname -a && pwd'              # remote shell   | hyd 'ls -la' (bare form)
+hyd py 'import sys; sys.version'      # remote Python via execute_code
+
+# Browser target (a Hypha Navigator web service):
+hyd profile add web "<navigator-service-url>" --type browser
+export HYD_PROFILE=web
+hyd 'document.title'                 # bare form runs JavaScript on a browser profile
+hyd nav 'https://example.com'        # navigate   | hyd shot page.png  (screenshot)
+hyd call get_browser_state           # call any service function
+
+hyd status                           # confirm the connection
+```
+
+The current profile + directory live in the `HYD_PROFILE` / `HYD_CWD` environment
+variables (per-terminal, nothing session-specific on disk); the remote stays
+stateless. If `hyd` isn't on your PATH after a `--user` install, use
+`python -m hypha_debugger.cli` (identical arguments). Run `hyd` with no args for help.
+
+> Any debugger's `GET <service-url>/get_skill_md` includes these same bootstrap
+> instructions, so an AI agent can self-install and connect from the URL alone.
+
 ## JavaScript (Browser)
 
 [![npm](https://img.shields.io/npm/v/hypha-debugger)](https://www.npmjs.com/package/hypha-debugger)

{hypha_debugger-0.2.3 → hypha_debugger-0.2.5}/hypha_debugger/__init__.py

@@ -12,5 +12,5 @@ Usage (sync):
 
 from hypha_debugger.debugger import start_debugger, start_debugger_sync, DebugSession
 
-__version__ = "0.2.3"
+__version__ = "0.2.5"
 __all__ = ["start_debugger", "start_debugger_sync", "DebugSession", "__version__"]

{hypha_debugger-0.2.3 → hypha_debugger-0.2.5}/hypha_debugger/debugger.py

@@ -2,6 +2,7 @@
 
 import asyncio
 import logging
+import os
 import secrets
 import threading
 from dataclasses import dataclass, field
@@ -21,6 +22,24 @@ from hypha_debugger.services.source import get_source, get_skill_md
 logger = logging.getLogger("hypha_debugger")
 
 
+def _ensure_ssl_certs() -> None:
+    """Point OpenSSL at certifi's CA bundle when the system trust store is
+    unconfigured — otherwise the hypha websocket TLS handshake fails with
+    CERTIFICATE_VERIFY_FAILED (macOS framework Python, minimal containers, fresh
+    venvs). Only sets the env vars if the user hasn't already; must run before
+    the first TLS connection (SSLContext reads these at creation time)."""
+    if os.environ.get("SSL_CERT_FILE"):
+        return
+    try:
+        import certifi
+
+        bundle = certifi.where()
+        os.environ["SSL_CERT_FILE"] = bundle
+        os.environ.setdefault("SSL_CERT_DIR", os.path.dirname(bundle))
+    except Exception:
+        pass
+
+
 def _build_service_url(server_url: str, service_id: str) -> str:
     """Build the HTTP service URL from server URL and full service ID.
 
@@ -200,6 +219,7 @@ async def start_debugger(
     Returns:
         A DebugSession with service_id, workspace, server, service_url, and token.
     """
+    _ensure_ssl_certs()
     from hypha_rpc import connect_to_server
 
     effective_id, effective_visibility = _resolve_id_and_visibility(
@@ -290,6 +310,7 @@ def start_debugger_sync(
     Returns:
         A DebugSession with service_id, workspace, server, service_url, and token.
     """
+    _ensure_ssl_certs()
     from hypha_rpc.sync import connect_to_server
 
     effective_id, effective_visibility = _resolve_id_and_visibility(

{hypha_debugger-0.2.3 → hypha_debugger-0.2.5}/hypha_debugger/services/source.py

@@ -92,13 +92,18 @@ def _get_skill_md_impl() -> str:
 A remote debugger is attached to a running Python process. You have full access
 to run shell + Python, read/write files, inspect variables, and install packages.
 
-**START HERE → install the `hyd` CLI (next section).** Decision rule: if you'll run
-more than ~2 commands here (i.e. almost any real task), `hyd` is the intended
-interface — one `pip install`, then every command is a short `hyd sh '…'` /
-`hyd py '…'` with the connection + working directory remembered for you, far fewer
-tokens than re-sending an authenticated curl each time, and it behaves like a local
-shell. Only for a single throwaway call is raw curl (further down) simpler. The raw
-HTTP API is the low-level fallback and powers the CLI.
+**RECOMMENDED → install the `hyd` CLI (next section).** Decision rule: if you'll run
+more than ~2 commands here (i.e. almost any real task) and you *can* install a pip
+package, `hyd` is the intended interface — one `pip install`, then every command is
+a short `hyd sh '…'` / `hyd py '…'` with the connection + working directory
+remembered for you, far fewer tokens than re-sending an authenticated curl each
+time, and it behaves like a local shell.
+
+**No install? Use `curl` — everything works without the CLI.** If you can't install
+packages (no pip, no network to PyPI, locked-down sandbox), skip `hyd` entirely: the
+raw HTTP API below is complete on its own, with copy-paste `curl` examples for every
+function (it's exactly what `hyd` calls under the hood). Recommended path is `hyd`;
+guaranteed-available path is `curl`. Either fully operates the remote host.
 
 ## Fast path — the `hyd` CLI (do this first)
 

{hypha_debugger-0.2.3 → hypha_debugger-0.2.5}/hypha_debugger.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: hypha-debugger
-Version: 0.2.3
+Version: 0.2.5
 Summary: Injectable debugger for Python processes and AI agents, powered by Hypha RPC
 Author: Amun AI AB
 License: MIT
@@ -43,6 +43,41 @@ A lightweight, injectable debugger for web pages and Python processes, powered b
 └─────────────────────────┘         └──────────────┘         └─────────────────────────┘
 ```
 
+## The `hyd` CLI — talk to any remote with minimal overhead
+
+Installing this package also gives you the **`hyd`** command — the low-overhead way
+for an agent (or you) to drive a remote target. Store the connection once as a
+**profile**, then every command is a short `hyd sh '…'` / `hyd js '…'` with the
+connection + working directory remembered — far fewer tokens than re-sending
+authenticated curl. One CLI drives **both** target types:
+
+```bash
+pip install hypha-debugger            # or: pipx install hypha-debugger  (always on PATH)
+
+# Terminal target (a Python process running this debugger):
+hyd profile add box "<py-debugger-service-url>"          # type inferred = terminal
+export HYD_PROFILE=box
+hyd sh 'uname -a && pwd'              # remote shell   | hyd 'ls -la' (bare form)
+hyd py 'import sys; sys.version'      # remote Python via execute_code
+
+# Browser target (a Hypha Navigator web service):
+hyd profile add web "<navigator-service-url>" --type browser
+export HYD_PROFILE=web
+hyd 'document.title'                 # bare form runs JavaScript on a browser profile
+hyd nav 'https://example.com'        # navigate   | hyd shot page.png  (screenshot)
+hyd call get_browser_state           # call any service function
+
+hyd status                           # confirm the connection
+```
+
+The current profile + directory live in the `HYD_PROFILE` / `HYD_CWD` environment
+variables (per-terminal, nothing session-specific on disk); the remote stays
+stateless. If `hyd` isn't on your PATH after a `--user` install, use
+`python -m hypha_debugger.cli` (identical arguments). Run `hyd` with no args for help.
+
+> Any debugger's `GET <service-url>/get_skill_md` includes these same bootstrap
+> instructions, so an AI agent can self-install and connect from the URL alone.
+
 ## JavaScript (Browser)
 
 [![npm](https://img.shields.io/npm/v/hypha-debugger)](https://www.npmjs.com/package/hypha-debugger)

{hypha_debugger-0.2.3 → hypha_debugger-0.2.5}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "hypha-debugger"
-version = "0.2.3"
+version = "0.2.5"
 description = "Injectable debugger for Python processes and AI agents, powered by Hypha RPC"
 readme = "README.md"
 license = {text = "MIT"}

{hypha_debugger-0.2.3 → hypha_debugger-0.2.5}/tests/test_services.py

@@ -342,3 +342,20 @@ def test_debug_session_print_instructions(capsys):
     assert "get_skill_md" in captured.out
     assert isinstance(result, str)
     assert "py-debugger-abc" in result
+
+
+def test_ensure_ssl_certs_sets_when_unset(monkeypatch):
+    import os
+    from hypha_debugger.debugger import _ensure_ssl_certs
+    monkeypatch.delenv("SSL_CERT_FILE", raising=False)
+    _ensure_ssl_certs()
+    # certifi is a dependency, so a real CA bundle path should now be set
+    assert os.environ.get("SSL_CERT_FILE") and os.path.exists(os.environ["SSL_CERT_FILE"])
+
+
+def test_ensure_ssl_certs_respects_existing(monkeypatch):
+    import os
+    from hypha_debugger.debugger import _ensure_ssl_certs
+    monkeypatch.setenv("SSL_CERT_FILE", "/custom/ca-bundle.pem")
+    _ensure_ssl_certs()
+    assert os.environ["SSL_CERT_FILE"] == "/custom/ca-bundle.pem"