Cursor Launch Agent: improve lifecycle management and parity with Claude runAgent

[bender-rodriguez-unit1]

The Cursor launchAgent component is missing several lifecycle features that the Claude runAgent already has. This makes it harder to build reliable end-to-end workflows with Cursor agents.

1. Conversation history retrieval

getLastMessage only fetches the last message. There should be a way to get the full conversation history from an agent run so downstream nodes can reason about what the agent did, not just the final output.

2. Session cleanup

Claude runAgent cleans up after itself: deletes the session, uploaded files, and temporary vault on completion. The Cursor component does not perform any cleanup. If the agent created resources (branches, environments), there is no teardown.

3. Execution metadata

The Cursor component stores basic metadata (agent ID, status, branch, PR URL). It should also capture the agent summary and final message content so they are visible in the execution detail view without needing a separate getLastMessage call.

Reference

See Claude runAgent implementation in pkg/integrations/claude/runagent/ for patterns to follow.

[shiroyasha]

/factory

[shiroyasha]

/factory