Popup Hush

A mac permission popup blocker app idea: a rule-based dismisser for noisy Mac permission popups. One week build with Swift, SwiftUI, Accessibility API and Claude API, for mac users who keep getting interrupted mid-typing.

See the spec
Why now

Why now

Auto Dismiss Mac OS "Allow <app> to find devices on local networks?" drew 154 points and 130 comments on Hacker News, so the annoyance is clearly shared. A rules and log layer would extend that idea to other dialogs. From the signals of the week of 26 Oct 2026.

The spec

The spec

Lets you set rules for which system permission dialogs to dismiss automatically, with a log of what was closed. It stops popups from stealing focus while you type.

Build time

One weekAPIs or integrations · Level 3 of 5

Audience

Mac users who keep getting interrupted mid-typing.

Stack

  • Swift
  • SwiftUI
  • Accessibility API
  • Claude API

Fun factor

Every popup that no longer breaks your typing is a small, visible payoff.

Core features

  • Menu bar app with on and off toggle
  • Rules by app and dialog text
  • Dismissal log with undo hints
  • Pause for an hour option

AI features

  • Suggests a rule from a screenshot or pasted text of a new dialog
  • Summarises the weekly log and flags apps that keep asking

Stretch goals

  • Share rule sets between Macs
  • Add a per-app allow list
  • Support more dialog types

First version

A menu bar app that detects the local network dialog and clicks Don't Allow, with a simple log.

Build plan

Build plan

4 milestones, in the order you would build them. Saved ideas get this plan with checkboxes and notes.

Detect the dialogUse the accessibility API to find the popup window and its buttons.
Start here
Click the right buttonDismiss it based on a hardcoded rule and log the action.
Add rulesStore rules by app name and dialog text in a settings file.
Build the log viewList recent dismissals in the menu bar dropdown.
The build prompt

The build prompt

Paste this into ChatGPT, Claude, Codex, or Cursor, then build the first version before anything else.

popup-hush.prompt.md
# Build Popup Hush

You are a senior full-stack engineer pairing with me on a side project. Build a working first version of the product described below. Read the whole brief before writing any code, then follow "How to work" at the end.

## The idea

**Popup Hush.** Lets you set rules for which system permission dialogs to dismiss automatically, with a log of what was closed. It stops popups from stealing focus while you type.

**Why now:** Auto Dismiss Mac OS "Allow <app> to find devices on local networks?" drew 154 points and 130 comments on Hacker News, so the annoyance is clearly shared. A rules and log layer would extend that idea to other dialogs.

**Who it is for:** Mac users who keep getting interrupted mid-typing

**What makes it fun:** Every popup that no longer breaks your typing is a small, visible payoff.

## Scope

- **Build time:** One week. Size every decision to ship a working first version inside this window.
- **Technical ambition:** Level 3 of 5, "APIs or integrations". The product leans on third-party APIs. Wrap each integration in its own module, handle its failures and rate limits, and cache what is safe to cache.
- **First version only.** Ship the core features below end to end. Stretch goals are listed so you can design around them, not build them.

## Core features (each must work end to end in the first version)

1. Menu bar app with on and off toggle
2. Rules by app and dialog text
3. Dismissal log with undo hints
4. Pause for an hour option

## AI features

- Suggests a rule from a screenshot or pasted text of a new dialog
- Summarises the weekly log and flags apps that keep asking

How to build them:
- Put every model call behind one server-side module with a typed interface, so the provider can change without touching the UI.
- Read API keys from environment variables only, and document each one in `.env.example`.
- Write prompts as versioned constants with clear instructions and an example of the expected output; parse and validate responses before using them.
- Handle timeouts, rate limits, and malformed output with a graceful fallback the user can understand. Stream responses where a wait would exceed a couple of seconds.
- Never let a feature depend on the model being perfect. Show the result, let the user edit or retry.

## Stretch goals (later, not in the first version)

- Share rule sets between Macs
- Add a per-app allow list
- Support more dialog types

Leave clean seams for these (a module boundary, a nullable column, a feature flag), but do not implement them unless I ask.

## Tech stack

Use exactly: Swift, Accessibility API, Claude.

Stay on current stable versions, follow each tool's official conventions, and add a library only when the standard library or the chosen stack cannot do the job cleanly. If part of this stack is a poor fit for a specific requirement, say so and propose the smallest change.

## Owner's notes

Written by me, the project owner. Treat these as requirements and preferences that override the generated material above when they conflict.

The first version should be exactly this, and no bigger: A menu bar app that detects the local network dialog and clicks Don't Allow, with a simple log.

## Build plan (with saved progress)

0 of 4 steps complete. Resume at step 1: Detect the dialog. Before you start it, check what is already implemented so you do not repeat finished work.

1. **Detect the dialog** [not started]
   Use the accessibility API to find the popup window and its buttons.

2. **Click the right button** [not started]
   Dismiss it based on a hardcoded rule and log the action.

3. **Add rules** [not started]
   Store rules by app name and dialog text in a settings file.

4. **Build the log view** [not started]
   List recent dismissals in the menu bar dropdown.

## Definition of done for the first version

- [ ] Menu bar app with on and off toggle works end to end, with real data, not a placeholder.
- [ ] Rules by app and dialog text works end to end, with real data, not a placeholder.
- [ ] Dismissal log with undo hints works end to end, with real data, not a placeholder.
- [ ] Pause for an hour option works end to end, with real data, not a placeholder.
- [ ] Every screen handles loading, empty, and error states.
- [ ] Typecheck, lint, and any tests pass, and the main user flow was exercised by hand.
- [ ] A README explains setup, environment variables, and how to run it locally.

## Quality bar

- Responsive from a phone to a desktop, keyboard-accessible, semantic HTML, visible focus states, labelled inputs, and sensible contrast.
- Loading, empty, and error states for every screen that reads or writes data. Errors say what happened and what to do next.
- Validate on the server, never trust the client, and keep secrets in environment variables with a committed `.env.example`.
- Type-safe end to end. No `any` without a comment explaining why.
- Small, readable modules named after what they do. No premature abstraction, no dead code, no TODOs left for later without a note.
- Sensible defaults over settings. If a choice is not in this brief, pick the simplest option that keeps the product coherent and say what you chose.

## How to work

1. **Read, then restate.** Summarize the product in three sentences and list your assumptions. Ask only the questions that block implementation. For everything else, decide and note the decision.
2. **Plan before code.** List the files and modules you will create, in build order, mapped to the core features. If a build plan is included above, use it instead: resume at the first step not marked done and check what already exists before touching it.
3. **Set up.** If a project already exists, inspect its code, instructions, and conventions first and build on them. Otherwise scaffold the stack above with linting, formatting, a typecheck script, `.env.example`, and a README stub.
4. **Model the data first.** Define the types, schema, and any migrations before the UI, so the shape of the product is settled early.
5. **Build in vertical slices.** Finish one core feature end to end (data, logic, UI) before starting the next. Keep the app runnable after every slice and commit each slice with a message that says what changed and why.
6. **Then the interface.** Apply the quality bar above to each screen as it lands, not as a final pass.
7. **Verify.** Run typecheck, lint, and tests. Exercise the main user flow by hand. Check each item in the definition of done and each acceptance criterion.
8. **Report.** Tell me what works, what you tested and how, what is not done, every setup step I must complete myself, and the three most useful next steps. Never claim a service, test, or flow was verified when it was not.

If you can edit and run the project, start implementing right after the short plan. If you cannot, give me concrete code and the exact commands to run for the next step.

Rules: keep the product name and the scope as written, do not invent features, prefer boring and proven choices, and stop to ask me when a decision would be expensive to reverse.

How to use

  1. Copy the prompt above.
  2. Open ChatGPT, Claude, or your AI editor and paste it into a new conversation.
  3. Build milestone one, run it, then move to the next. Add stretch goals only after the first version works.

Want ideas built around you instead? Generate four from your own interests, time, and stack.

Frequently asked questions

FAQ

Frequently asked questions

Answers on what Popup Hush is, how to build it, and where example ideas come from.

Similar ideas

Similar to Popup Hush

More productivity ideas, then a few from other categories.

Generate your own

Ready to generate yours?

Four ideas per round, shaped by your interests, skill level, and how much time you have.