Route support bugs into an AI investigation and PR

Pylon can pass detailed bug tickets to Devin, which inspects code and logs and may draft a pull request for an engineer to review.

Done with Devin· Intermediate· Oct 2026

What they did
Pylon set up a workflow that looks for support tickets with enough detail to investigate, such as an error message or reproduction steps. When one appears, it adds an escalation tag that kicks off a Devin run with the ticket as context. Devin then searches the repository and linked logs, tries to recreate the issue, and may open a PR if it has the right Git access; an engineer still checks the work and decides whether to merge.
How it went
The example describes a launch, not performance data. Some runs can end with only findings and no pull request. Pylon can report whether Devin-created PRs were opened, merged, or closed, but it cannot verify that the customer’s problem is actually resolved.
Tips
Devin’s default Pylon setup is read-only for Git, so an admin has to grant push and PR rights first. Codebase search through Pylon is free, but full coding sessions count against a Devin plan.

Try it yourself with Devin

Watch for a support ticket from [support tool] that includes [error message / reproduction steps / other concrete details] and has the [tag] label. Investigate the repository at [repo URL] and any connected logs to identify the likely cause, then write a short findings summary. If you have enough confidence to propose a fix, prepare a draft pull request with a test plan, but do not send, merge, delete, or submit anything until you ask me for approval. If the evidence is inconclusive, stop after the investigation and report what you found.

Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.

Read the original on quasa.io ↗

Get 3 agent uses like this every morning

With the day's top AI news. Free, and one click to unsubscribe.