Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →omnigent-ai/pi-native-e2e-dev
Spin up a live local Omnigent server + runner and exercise the native Pi TUI harness (pi-native) end-to-end — launch the real `pi` CLI via `omnigent pi`, drive turns through the web/bridge, smoke-test, and bug-bash. Load when developing, testing, or debugging the pi-native harness (omnigent/inner/pi_native_executor.py, pi_native_harness.py, omnigent/pi_native.py, pi_native_bridge.py, pi_native_credentials.py) or its bridge / extension / auth / model behavior.
Passed 22 of 22 test cases with the skill, and 4 of 22 without it.
and 26 more in the full report
18 fixed4 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 18 test cases the skill fixed. Same model, same prompt, with and without the skill.
After starting the background server on `http://127.0.0.1:6767`, what curl endpoint should I call to verify that the server is alive and returning a healthy JSON status?
| Checked | Without skill | With skill |
|---|---|---|
| Queries curl -s $SERVER/health | Passed | Passed |
| Expects a JSON response with status ok | Missed | Passed |
The instructions your model reads when the skill loads.
The pi-native harness wraps the real Pi coding-agent TUI
(@earendil-works/pi-coding-agent, the pi CLI). Unlike the SDK harnesses
(cursor / copilot / antigravity), it does not run in-process: omnigent pi
ensures a host daemon, the daemon spawns a runner that launches pi inside a
runner-owned tmux terminal, and your TTY attaches to it. Omnigent's web-UI
turns are forwarded into that live pi process through a file-inbox bridge +
a packaged JS extension (pi.sendUserMessage). This skill is the proven
recipe for running it for real against a live local server + runner — not
just the unit tests.
Like the other harnesses, the runner imports from your current checkout, so testing here exercises exactly the code you're on. (CWD/venv selects the code, not
PYTHONPATH.)
your TTY ── (attach / pexpect) ──► omnigent pi (CLI, local)
│ ensures
▼
host daemon ──► local Omnigent server (AP)
│ spawns ▲
▼ │ HTTP
runner ── launches ──► pi (TUI, in tmux)
│ loads
▼
omnigent pi-native extension (JS)
Two ways a turn reaches Pi — test both:
POST …/events).PiNativeExecutor.run_turn →
enqueue_user_message() writes inbox/<ordinal>_msg_*.json → the resident
extension polls the inbox → pi.sendUserMessage(...). This is the
harness-specific path most worth covering.test cases passed, vs 4 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.