Observed facts: Cognition’s documentation says users can start Devin sessions from Pylon issues, attach screenshots or logs, and receive plans, commands, file edits, pull requests, and session links back in the issue. It also says Pylon events can trigger automations and that the integration creates a default Pylon security profile for delegated sessions.
Mechanism: The integration joins a support queue to an engineering agent through an issue context and event triggers, while separating the permissions to read or write Pylon data from Git access. Why now: This moves a customer-reported problem closer to an executable engineering workflow without requiring the handoff to begin in an engineering tracker.
First implication: A support-to-code path is only as safe as the permissions attached to the delegated session; the documented default is read-only Git access, with no customer-reply sending. Evidence boundary: The source documents product capabilities and defaults, not actual deployment, adoption, safety performance, or measured resolution outcomes.
First watch condition: Watch whether teams can demonstrate reliable ticket-to-change workflows while keeping ticket content untrusted and write permissions narrowly scoped. The documentation explicitly flags support tickets as untrusted and instructs administrators to review the security profile before enabling workflows.
This starts a distinct analytical record because no prior New Runtime record is supplied for this specific support-ticket-to-coding-session integration.