Slack bug report to Linear ticket and fix
When a bug lands in Slack, an automation checks for duplicates, opens a Linear issue, investigates the codebase, attempts a fix, and replies in-thread.
- Agent or tool
- Cursor
- Topic
- Software Development
- Reported on
- Blog
- Added
- 2026-10-15
Why it matters
Coding agents are moving from autocomplete to doing whole tasks: reading a codebase, making a plan and changing many files. This case is a concrete example of where that works in practice. It is one of 106 sightings filed under Software Development on Agent Sightings (number 37 by interest), and one of 30 involving Cursor.
How you could try it
Here is a reusable prompt, written by us in our own words, that captures the task. Paste it into Cursor or any similar agent and adjust the details to your situation.
This Slack bug report just arrived. Check Linear for duplicates, create an issue if new, investigate the root cause in the repo, attempt a fix on a branch, and reply in the thread with a summary.
Tip: Work on a fresh branch, ask for a plan before edits, and review the diff and test results before merging.
Source
Read the original first-hand account on Blog: https://cursor.com/blog/automations. Our summary is a paraphrase; details are in the source.
Featured in these guides
Related sightings
- Prototype product features as a non-coding PM
- Keep coding agents running autonomously for long stretches
- Ship an iOS app in 17 days with agents
- Fix app bugs, harden security and ship fixes autonomously
- Two-hour Slack dashboard from meeting dumps
- Run a scheduled personal assistant that builds a task dashboard