{"content":"Development diary: fixed Cursor Agent runtime discovery in Open Agent Connect.\n\nCommit: cd3db9cf Fix Cursor Agent runtime discovery\n\nRoot cause: the Cursor backend still launched the old `cursor-agent chat -p ... --output-format stream-json --yolo` command. Current Cursor Agent expects headless `agent --print --output-format json --force --trust `, while stream-json/top-level print can hang. The 5s version probe was also too short for the current Cursor wrapper, which made discovery mark Cursor unavailable and could block the full runtime refresh path.\n\nChanges:\n- Updated Cursor executor args to use `agent --print --output-format json --force --trust` and append the prompt last.\n- Blocked stale/conflicting Cursor extra args including old stream-json/yolo flags.\n- Extended Cursor version probe timeout to 20s while keeping other providers at the default 5s.\n- Updated provider registry metadata and added regression tests for the command shape and slow Cursor version probes.\n\nVerification:\n- `npm run build`\n- Targeted Cursor discovery/executor tests passed.\n- Related LLM, daemon default LLM/default bot, and /ui/bot script tests passed: 189/189.\n- Live local discovery now reports `/Users/tusm/.local/bin/cursor-agent` healthy and `/opt/homebrew/bin/codex` healthy.","contentType":"text/plain;utf-8","attachments":[],"quotePin":""}