How to use Cursor to add an iOS trailer mute setting
Cursor helped a developer with limited Swift experience add an iOS trailer mute setting during a hackathon. Iteration and an engineer's review preceded the merge.
news.ycombinator.com
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Examine [iOS codebase] and add a setting under [settings location] to mute [autoplaying media]. Follow existing project conventions, identify all affected playback paths, and explain how to test the behavior before human review.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source poster / publisher
- geuis
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- The mute setting was implemented during an afternoon hackathon and merged a week or two later after review and minor alignment updates.
- Human involvement
- The author iterated on behavior, then an iOS engineer reviewed the change and requested alignment with the existing codebase.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- Asked Cursor to examine the iOS codebase and locate the requested settings area.
- Iterated with Cursor to add a mute setting and resolve behavior across the app.
- Submitted the feature for review at an iOS engineer's request.
During a company hackathon, the author used Cursor to add a missing mute option for autoplaying game trailers in an iOS app. Opening test builds interrupted music they were listening to, and the existing ticket had remained a low priority for the iOS team. The author had written only about a hundred lines of Swift previously.
They asked Cursor to examine the codebase and place a mute button in a particular area of app settings. Within about ten minutes, the model had found where the feature belonged. Some back-and-forth produced a functioning setting that mostly worked throughout the app. Further iteration resolved the remaining issues, with the afternoon's work taking about an hour overall.
The author then contacted an iOS engineer, who asked them to submit the change for review. Review identified a few updates needed to align the implementation with the rest of the codebase, but the author described those as insubstantial. The feature merged a week or two later.
Who it's for: Developers adding a focused feature in an unfamiliar language who have access to experienced code reviewers.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: Hacker News · geuis
Frequently asked questions
How much Swift experience did the author have?
The author estimated having written about a hundred lines of Swift before attempting the feature.
Did the feature go through human review?
Yes. An iOS engineer asked the author to submit it for review. A few codebase-alignment changes were needed before it merged a week or two later.
More details
Remaining steps
- Made codebase-alignment updates before the feature was merged.
About this account
Cursor located the relevant code and implemented the setting through back-and-forth with the author.
Platform: Hacker News. Attribution: https://news.ycombinator.com/item?id=48418112. Prompt: Suggested (written by Agents In Use, not the author's). Sourced by the Agents In Use pipeline.
Credit: geuis on Hacker News
Source published
Added to Agents In Use
Source checked
Tools and topics
Cursor · iOS codebase
iOS · Swift · Code review · App settings
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.