1b62cec0a2
BREAKING: HermesAgentConfig.command and CursorAgentConfig.command are now required string fields (absolute path to CLI binary). Validation rejects non-absolute paths at construction time. - Eliminates PATH resolution ambiguity in spawned worker processes - spawnCli: explicit env: process.env for clarity - bundle-entry: WORKFLOW_CURSOR_COMMAND is now required - Updated tests for both agents
@uncaged/workflow-agent-cursor
AgentFn adapter that runs the cursor-agent CLI against a workspace path derived from the thread.
The agent builds a full prompt (system + task + step history via @uncaged/workflow-util-agent), extracts the absolute workspace path with your extract + Zod schema, then spawns cursor-agent with --workspace, model, and non-interactive flags.
Install
bun add @uncaged/workflow-agent-cursor @uncaged/workflow-runtime @uncaged/workflow-util-agent zod
In this monorepo: "@uncaged/workflow-agent-cursor": "workspace:*" plus workspace:* for @uncaged/workflow-runtime and @uncaged/workflow-util-agent, and zod ^4.
Usage
import { createCursorAgent } from "@uncaged/workflow-agent-cursor";
const agent = createCursorAgent({
model: null, // null → "auto"
timeout: 0, // ms; 0 = no limit (spawnCli timeout disabled)
extract: myExtractFn,
});
API overview
| Export | Description |
|---|---|
createCursorAgent(config) |
Returns AgentFn that runs cursor-agent with buildAgentPrompt(ctx) from @uncaged/workflow-util-agent |
CursorAgentConfig |
model, timeout, extract (must supply workspace path) |
validateCursorAgentConfig |
Config validation result |
Requires cursor-agent on PATH at runtime.