Files
msd-core/.changeset/2089-eos-cursor-imperative-adapter.md
2026-07-09 13:59:48 -04:00

1.5 KiB

type, pr
type pr
Changed 2120

Cursor is now driven through the public Host-Integration Interface, with two capability upgrades (ADR-1239 / EoS). Cursor previously installed via hardcoded runtime === 'cursor'/isCursor branches in bin/install.js; its install/uninstall now runs through the imperative adapter, and every hardcoded cursor branch is folded into descriptor-driven runtime.hostBehaviors (reapplyCommand, frontmatterDialect, hooksJsonSurface, skipSharedHooksInstall, reportCommandsDir, managedHookEvents). Install/uninstall output is byte-identical (golden parity asserted for all 16 runtimes). Two Context7-verified upgrades land: (1) expanded hook-bus coverage — GSD registers all 6 managed lifecycle events in Cursor's hooks.json (preToolUse, stop, subagentStart, subagentStop in addition to the original sessionStart/postToolUse), driven by a new descriptor-driven adapter module (src/host-integration-adapters/imperative-hook-bus.cts) that reads hostBehaviors.managedHookEvents instead of a hardcoded event pair; cite https://cursor.com/docs/hooks. (2) named/background nested subagent dispatch — Cursor's dispatch.background/backgroundDispatch/nested are all true with maxDepth: 2, so shouldFlattenDispatch(cursor) returns false and GSD's wave-based execution drives Cursor's native background + depth-2 nested subagent invocation instead of flattening to inline sequential calls; cite https://cursor.com/docs/subagents + https://cursor.com/docs/sdk/typescript. (#2089)