Cursor IDE subagentStart hook input doesn't include subagent_model

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

The subagent hook input does not include subagent_model, which is document. Additionally I believe the subagent type is always, “general_purpose”

Steps to Reproduce

Run subagents and look at cursor.hooks.log, see
═══════════════════════════════════════════════════════════════════════════════════════
subagentStart
═══════════════════════════════════════════════════════════════════════════════════════
Command: .cursor/hooks/block-explore-subagent.sh (472ms) exit code: 0

INPUT:
{
“conversation_id”: “b950150f-eda9-4c38-9d83-c92d2a6be18a”,
“generation_id”: “b950150f-eda9-4c38-9d83-c92d2a6be18a”,
“model”: “gpt-5.3-codex”,
“subagent_id”: “call_SbFRlMHiWQGs7gPhfSlvuQuR\nfc_010746da2e9a9d97f09c8e9103e69c7f606f8119c6abb2db795051005982a”,
“subagent_type”: “general-purpose”,
“task”: “”,
“parent_conversation_id”: “b950150f-eda9-4c38-9d83-c92d2a6be18a”,
“tool_call_id”: “call_SbFRlMHiWQGs7gPhfSlvuQuR\nfc_010746da2e9a9d97f09c8e9103e69c7f606f8119c6abb2db795051005982a”,
“is_parallel_worker”: false,
“hook_event_name”: “subagentStart”,
“cursor_version”: “2.6.22”,
“workspace_roots”: [
redacted
],
“user_email”: “redacted”,
“transcript_path”: “redacted”
}

Expected Behavior

Follows documentation

Operating System

MacOS

Version Information

Version: 2.6.22 (Universal)
VSCode Version: 1.105.1
Commit: c6285feaba0ad62603f7c22e72f0a170dc8415a0
Date: 2026-03-27T15:59:31.561Z
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.4.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey @Jack_Williams1,

These are both confirmed bugs. Both are tracked by our team and being worked on. In the meantime, you can use the model field (which does get populated via a fallback) as a workaround for the missing subagent_model — though note that it reflects the parent conversation model, not the subagent-specific one.

I’ll keep you posted when fixes ship. Thanks for the detailed bug report with the hook log output — that was really helpful.