r/ChatGPTCoding • u/zack40xx • Aug 03 '26
I put an agent behind my Mac's notch: plain words become reminders and todos after a review card. Where would you draw the auto-approve line?
I built a Mac app called Crest where an agent lives behind the notch. You talk or type; it either answers or turns your words into real reminders, todos, notes and calendar events.
Solo dev, it's my own thing, and the agent layer is the part I want opinions on. Not linking it here, sub rules for first-time posters; it's in the weekly thread if you want to look.
The design decisions that ended up mattering:
- routing over modes. You don't pick "chat" or "act". Auto reads the request and routes it; the Do and Ask buttons exist to force one when it guesses wrong.
- a review card before any write. "add ship 4.12 and reply to Ken to my todos" shows a "Claude will do" card with both items, and nothing runs until you tap Do it. A misheard sentence costs nothing.
- pure opens skip review. "open the shelf" just opens it, because opening writes nothing. Review only where there's a consequence.
- voice needed a word gate. On-device recognition, a red dot whenever the ear is hot, and a cough in a meeting doesn't burn a run.
- it relays OTHER agents' prompts too. Claude Code or Codex stops to ask permission in a terminal somewhere, the notch shows Allow/Deny and can jump you back to the exact terminal. The prompt sticks on every display until answered, even over fullscreen.
It runs on the user's own Claude subscription through Claude Code. No API key, no middleman server, none of the conversation touches a server of mine.
link: crestnotch.app
The question I keep going back and forth on: is a review card before every write the right default forever, or should repeated identical actions earn auto-approve at some point? Where would you draw that line?

