Hypha Debugger
A lightweight, injectable debugger for web pages and Python processes, powered by Hypha RPC. Designed for AI agent workflows — inject a debugger, get a URL, call it remotely.
No browser extension required. Just import and start.
┌─────────────────────────┐ ┌──────────────┐ ┌─────────────────────────┐
│ Target (Browser/Python) │ ──WS──▶ │ Hypha Server │ ◀──WS── │ Remote Client │
│ │ │ │ │ (curl / Python / Agent) │
│ - Registers debug svc │ │ Routes RPC │ │ - Calls debug functions │
│ - Executes remote code │ │ messages │ │ - Takes screenshots │
│ - Returns results │ │ │ │ - Queries DOM/state │
└─────────────────────────┘ └──────────────┘ └─────────────────────────┘
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:
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_mdincludes these same bootstrap instructions, so an AI agent can self-install and connect from the URL alone.
JavaScript (Browser)
Inject into any web page to enable remote DOM inspection, screenshots, JavaScript execution, and React component tree inspection.
Quick Start
Via CDN (easiest):
<script src="https://cdn.jsdelivr.net/npm/hypha-rpc@0.20.97/dist/hypha-rpc-websocket.min.js"></script>
<script src="https://cdn.jsdelivr.net/npm/hypha-debugger/dist/hypha-debugger.min.js"></script>
<script>
hyphaDebugger.startDebugger({ server_url: 'https://hypha.aicell.io' });
</script>
Via npm:
npm install hypha-debugger hypha-rpc
import { startDebugger } from 'hypha-debugger';
const session = await startDebugger({
server_url: 'https://hypha.aicell.io',
});
console.log(session.service_url); // HTTP endpoint for remote calls
console.log(session.token); // JWT token for authentication
What You Get
After starting, the debugger prints:
[hypha-debugger] Connected to https://hypha.aicell.io
[hypha-debugger] Service URL: https://hypha.aicell.io/ws-xxx/services/clientId:web-debugger
[hypha-debugger] Token: eyJ...
[hypha-debugger] Test it:
curl 'https://hypha.aicell.io/ws-xxx/services/clientId:web-debugger/get_page_info' -H 'Authorization: Bearer eyJ...'
A floating debug overlay (🐛) appears on the page with connection status, service URL (with copy button), and a live log of remote operations.
Service Functions (JavaScript)
All functions are callable via the HTTP URL or Hypha RPC:
| Function | Description |
|---|---|
get_page_info() |
URL, title, viewport size, detected frameworks, performance timing |
get_console_logs(level?, limit?) |
Captured console output (log/warn/error/info) |
query_dom(selector, limit?) |
Query elements by CSS selector — returns tag, text, attributes, bounds |
click_element(selector) |
Click an element |
fill_input(selector, value) |
Set value of input/textarea/select (works with React) |
scroll_to(target) |
Scroll to element (CSS selector) or position ({x, y}) |
get_computed_styles(selector, properties?) |
Get computed CSS styles |
get_element_bounds(selector) |
Get bounding rectangle and visibility |
take_screenshot(selector?, format?, scale?) |
Capture page/element as base64 PNG/JPEG |
execute_script(code, timeout_ms?) |
Execute arbitrary JavaScript, return result |
navigate(url) |
Navigate to URL |
go_back() / go_forward() / reload() |
Browser history navigation |
get_react_tree(selector?, max_depth?) |
Inspect React component tree (fiber-based) — names, props, state |
Calling via curl
# Get page info
curl 'SERVICE_URL/get_page_info' -H 'Authorization: Bearer TOKEN'
# Take a screenshot
curl 'SERVICE_URL/take_screenshot' -H 'Authorization: Bearer TOKEN'
# Execute JavaScript
curl -X POST 'SERVICE_URL/execute_script' \
-H 'Authorization: Bearer TOKEN' \
-H 'Content-Type: application/json' \
-d '{"code": "document.title"}'
# Query DOM
curl -X POST 'SERVICE_URL/query_dom' \
-H 'Authorization: Bearer TOKEN' \
-H 'Content-Type: application/json' \
-d '{"selector": "button"}'
# Click a button
curl -X POST 'SERVICE_URL/click_element' \
-H 'Authorization: Bearer TOKEN' \
-H 'Content-Type: application/json' \
-d '{"selector": "#submit-btn"}'
Calling via Python
from hypha_rpc import connect_to_server
server = await connect_to_server({
"server_url": "https://hypha.aicell.io",
"workspace": "WORKSPACE",
"token": "TOKEN",
})
debugger = await server.get_service("web-debugger")
info = await debugger.get_page_info()
screenshot = await debugger.take_screenshot()
result = await debugger.execute_script(code="document.title")
tree = await debugger.get_react_tree()
Configuration
await startDebugger({
server_url: 'https://hypha.aicell.io', // Required
workspace: 'my-workspace', // Optional, auto-assigned
token: 'jwt-token', // Optional
service_id: 'web-debugger', // Default: 'web-debugger'
service_name: 'Web Debugger', // Default: 'Web Debugger'
show_ui: true, // Default: true (floating overlay)
visibility: 'public', // 'public' | 'protected' | 'unlisted'
});
Python
Inject into any Python process to enable remote code execution, variable inspection, file browsing, and process monitoring.
Quick Start
pip install hypha-debugger
CLI (simplest — just run and get instructions):
hypha-debugger
Or with options:
hypha-debugger --server-url https://hypha.aicell.io --service-id my-debugger
hypha-debugger --no-token # URL-secret mode, no auth needed
python -m hypha_debugger # alternative
Async:
import asyncio
from hypha_debugger import start_debugger
async def main():
session = await start_debugger(server_url="https://hypha.aicell.io")
session.print_instructions() # print instructions anytime
await session.serve_forever()
asyncio.run(main())
Sync (scripts, notebooks):
from hypha_debugger import start_debugger_sync
session = start_debugger_sync(server_url="https://hypha.aicell.io")
session.print_instructions() # print instructions anytime
What You Get
The debugger prints copy-paste instructions on startup:
[hypha-debugger] Connected to https://hypha.aicell.io
[hypha-debugger] Service ID: ws-xxx/clientId:py-debugger
[hypha-debugger] Service URL: https://hypha.aicell.io/ws-xxx/services/py-debugger
SERVICE_URL="https://hypha.aicell.io/ws-xxx/services/py-debugger"
TOKEN="eyJ..."
# Quick test:
curl "$SERVICE_URL/get_process_info?_mode=last" -H "Authorization: Bearer $TOKEN"
# Execute code:
curl -X POST "$SERVICE_URL/execute_code?_mode=last" -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" -d '{"code": "import sys; sys.version"}'
Call session.print_instructions() anytime to reprint them.
Service Functions (Python)
| Function | Description |
|---|---|
get_process_info() |
PID, CWD, Python version, hostname, platform, memory usage |
execute_code(code, namespace?) |
Execute arbitrary Python code, return stdout/stderr/result |
get_variable(name, namespace?) |
Inspect a variable — type, value, shape (for numpy), keys (for dicts) |
list_variables(namespace?, filter?) |
List variables in scope |
get_stack_trace() |
Stack trace of all threads |
list_files(path?, pattern?) |
List files in directory (sandboxed to CWD) |
read_file(path, max_lines?, encoding?) |
Read a file (sandboxed to CWD) |
get_installed_packages(filter?) |
List installed pip packages |
Calling via curl
# Get process info
curl 'SERVICE_URL/get_process_info' -H 'Authorization: Bearer TOKEN'
# Execute Python code
curl -X POST 'SERVICE_URL/execute_code' \
-H 'Authorization: Bearer TOKEN' \
-H 'Content-Type: application/json' \
-d '{"code": "2 + 2"}'
# List files
curl 'SERVICE_URL/list_files' -H 'Authorization: Bearer TOKEN'
# Read a file
curl -X POST 'SERVICE_URL/read_file' \
-H 'Authorization: Bearer TOKEN' \
-H 'Content-Type: application/json' \
-d '{"path": "main.py"}'
Calling via Python (remote client)
from hypha_rpc import connect_to_server
server = await connect_to_server({
"server_url": "https://hypha.aicell.io",
"workspace": "WORKSPACE",
"token": "TOKEN",
})
debugger = await server.get_service("py-debugger")
info = await debugger.get_process_info()
result = await debugger.execute_code(code="import sys; sys.version")
files = await debugger.list_files()
How It Works
- Your target (browser page or Python process) connects to a Hypha server via WebSocket
- It registers an RPC service with schema-annotated functions
- The debugger prints a Service URL and Token
- Remote clients call service functions via HTTP REST or Hypha RPC WebSocket
- All functions have JSON Schema annotations, making them compatible with LLM/AI agent tool calling
License
MIT
Metadata
Release files for hypha-debugger 0.2.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| hypha_debugger-0.2.5.tar.gz | 34.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| hypha_debugger-0.2.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 66.0 kB
Release files / hypha_debugger-0.2.5.tar.gz
| Download URL | hypha_debugger-0.2.5.tar.gz |
|---|---|
| Size | 34.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7325098d3616d30bec428206570d1a15af2a33b996171b02e41ef9122bffedf1
|
|
BLAKE2b-256 checksum How to use checksums |
0e2f235c719a869f2fb71125621f1b96ea83a080a6a601b05c44d1fa3c5552d4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 15, 2026.
Transparency logRelease files / hypha_debugger-0.2.5-py3-none-any.whl
| Download URL | hypha_debugger-0.2.5-py3-none-any.whl |
|---|---|
| Size | 31.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
99c31874008f2b92c8b7bd247eefba90dd596c4ed2eb982a6557f3863c7bc6cb
|
|
BLAKE2b-256 checksum How to use checksums |
19eab253ee138a695f94d08b5850a7cf0bac6e483535e16c3baa9b4cbd5e1a9c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 15, 2026.
Transparency log