Spin up a live local Omnigent server and exercise the Cursor SDK harness end-to-end — build cursor agents, run real turns, smoke-test, and bug-bash. Load when developing, testing, or debugging the cursor harness (omnigent/inner/cursor_executor.py, cursor_harness.py, cursor_auth.py) or its auth / model / tool-bridge behavior.
SkillScore91Maintained
Automatic
◆AI Engineer pack
Last verified 10/9/2026
What it changes
Passed 21 of 23 test cases with the skill, and 4 of 23 without it.
Without skill17%
With skill91%
Checks it passed that the model alone missed
wraps turn execution in timeout 280
stops the background server using .venv/bin/omni server stop
explains that turns take between 30 and 90 seconds to execute
and 25 more in the full report
17 fixed4 passed either way2 still failing0 broke
Pass-rate lift
+74 pp
Tokens
+56%
Agent turns
0%
Response time
-55%
Model gemini-3.6-flashMeasured 10/9/2026v321 of 23 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 17 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 17
Prompt
Which specific PyTest file runs the gated end-to-end integration harness test for Cursor in the codebase?
What was checked, without and with the skill
Checked
Without skill
With skill
uses pytest with tests/e2e/omnigent/test_per_harness_cursor.py
Missed
Passed
case-17 · gemini-3.6-flash · 10/9/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md171 linessingle file
Cursor SDK harness: end-to-end dev & testing
The cursor harness drives the Cursor Python SDK (cursor_sdk, an
AsyncAgent over a local bridge) and bridges Omnigent's sys_* tools into
Cursor as SDK custom_tools. This skill is the proven recipe for running it
for real against a live local server — not just the unit tests.
The harness runs as a local runner from your current checkout, so
omni run <bundle> --server <url> exercises exactly the code you're on.
Prerequisites (check these first)
You're on the branch you want to test. The cursor harness merged to
main (#203/#204). Test on main unless validating a specific branch.
A Cursor API key is configured. The SDK requires an API key
(crsr_…); there is no cursor-agent login path. Verify (booleans only —
never print the key):
If both are False, run omni setup and register a Cursor key, or
export CURSOR_API_KEY=crsr_….
cursor-sdk is installed (a baseline dependency):
.venv/bin/python -c "import cursor_sdk; print(cursor_sdk.__file__)".
Network egress to Cursor's backend. The bridge subprocess talks to
Cursor's own API; a turn that hangs or fails to connect on a locked-down
host is usually an egress problem, not a harness bug.
Step 1 — start a local server
cd /path/to/omnigent
.venv/bin/omni server --background # spawns a detached server on a free loopback port
.venv/bin/omni server status # prints the URL, e.g. http://127.0.0.1:6767
Use the printed URL below as $SERVER. (You can also run a foreground
server on a fixed port with omnigent server --port 7777 --no-open.)