Card #1272 · Cursor (AI IDE)
Lack of observability and lifecycle hooks for Cloud Agents
Merchants are unable to get full observability into Cloud Agents because critical lifecycle hooks like session start, end, and final responses do not fire. This creates a blind spot for tracking reasoning, token usage for cost attribution, and trace boundaries in external observability tools.
Pain score
0.50/ 1.00 · weighted product of four components
Reach0.47distinct authors (log-normalized)
Recency1.00freshness decay, half-life months
Engagement0.32upvotes + comments, normalized
Monetization0.50willingness-to-pay cues in evidence
§ Evidence — 3 verified quotes
None of the lifecycle hooks fire at all ( sessionStart , sessionEnd , afterAgentResponse , stop ). Only tool-level hooks work
Final assistant message (the afterAgentResponse /completion text) — this is the single most important one; it’s how we reconstruct what the agent concluded and did.
Token usage — input / output / and ideally cache-read + cache-creation. This is for cost attribution; without it cloud runs are a cost blind spot.
Comments are a Pro feature — join the conversation, share what you've shipped, hear what others are building.
Upgrade to Pro