How to use Cursor to build an Airbnb price sorter
An experienced developer used Cursor and o3 Mini High to build an Airbnb sorting extension, supplying HTML element IDs and removing excessive permissions before publishing.
news.ycombinator.com
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Build a browser extension that sorts [listing page] by [price field]. Use these HTML element IDs: [IDs]. Address sorting on initial load, iterate on [observed problems], and explain every requested permission so I can review and remove unnecessary access before publishing.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source poster / publisher
- gonzor
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- The author described the Airbnb extension as fully functional after several iterations and trimmed excessive permissions before publishing.
- Human involvement
- The author identified loading problems, provided HTML element IDs and manually trimmed permissions before publishing.
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
- Selected a small Airbnb price-sorting extension as a personal project.
- Used o3 Mini High and iterated on initial-load sorting problems.
- Manually supplied the required HTML element IDs.
The author, an experienced developer, chose two small personal projects to test whether AI could handle implementation: an Airbnb price-sorting extension and a Spotify macOS Notification Center widget. They described using Cursor and the o3 Mini High model. The Airbnb extension was their first extension project, although they were already comfortable with web technologies.
Sorting on the initial page load did not work smoothly at first. After several iterations, the model produced code the author described as fully functional. The only information they said they had to provide manually was the HTML element IDs. Before publishing, they also removed excessive permissions requested by the generated extension.
The companion Spotify project had a less satisfactory outcome. The author could not get UserDefaults to synchronize between its extension and app, and the AI repeatedly suggested the same fixes. They temporarily disabled part of the sandbox for personal use. This separates the successful Airbnb result from the unresolved difficulty in the other experiment.
Who it's for: Developers testing small browser-extension ideas while retaining responsibility for iteration and permission review.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: Hacker News · gonzor
Frequently asked questions
What did the author manually provide for the extension?
They reported manually supplying the HTML element IDs. They also trimmed excessive extension permissions before publishing.
Did both personal projects succeed equally?
No. The Airbnb sorter became fully functional after iterations. The Spotify widget retained a UserDefaults synchronization problem, leading to a temporary partial sandbox disablement.
More details
Remaining steps
- Removed excessive permissions before publishing the extension.
About this account
The model produced the extension code through iterations, while the author supplied page identifiers and adjusted permissions.
Platform: Hacker News. Attribution: https://news.ycombinator.com/item?id=43194175. Prompt: Suggested (written by Agents In Use, not the author's). Sourced by the Agents In Use pipeline.
Credit: gonzor on Hacker News
Source published
Added to Agents In Use
Source checked
Tools and topics
Cursor · o3 Mini High
Browser extensions · Airbnb · Permissions
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.