helium-harness

Files (15)

• SKILL.md
• __init__.py
• _ipc.py
• admin.py
• auth.py
• daemon.py
• helpers.py
• macos.py
• paths.py
• recorder.py
• run.py
• telemetry.py
• video-template.html
• video.py
• video_render.py

SKILL.md (first lines)

# Helium Harness

Helium Harness connects an agent to the user's Helium browser through the
Chrome DevTools Protocol. Use it for interactive work that needs an existing
Helium session, rendered page state, or browser UI actions.

## Connection

Run a short Python script through the CLI. Helpers are pre-imported.

```powershell
@'
ensure_real_tab()
print(page_info())
'@ | helium-harness
```

The first connection may open Helium's `chrome://inspect/#remote-debugging`
page. Ask the user to enable remote debugging and accept Helium's prompt, then
retry once they confirm.

For an unusual installation location, set `HH_HELIUM_PATH` or `HELIUM_PATH` to
the executable before invoking the harness.

## Workflow

- Begin navigation with `new_tab(url)`, then call `wait_for_load()`.
- Inspect accessibility state before interacting.
- Prefer targeted DOM checks to screenshots unless visual layout matters.
- After an interaction, collect the smallest state check that proves its result.
- Stop at login, password, MFA, CAPTCHA, payment, or final form-submission
  steps unless the user takes over or explicitly confirms the exact action.

## Examples

```python
new_tab("https://example.com")
wait_for_load()
print(page_info())
```

```python
tree = cdp("Accessibility.getFullAXTree")["nodes"]
print([node for node in tree if node.get("role", {}).get("value") == "button"])
```

Use `BU_CDP_URL` or `BU_CDP_WS` only when the user provides an explicit CDP
endpoint. They override local Helium discovery.

From adamtpang/helium-harness, MIT.

More from adamtpang/helium-harness