Buddy
A push-to-talk Mac assistant that answers from your screen with spoken responses.
Tagline
Ask your screen. Get answers.
Stop tab-switching for every screen question.
A Mac assistant that explains what’s on-screen.
Hold, ask, and hear the answer at your cursor.
Category-defining: Buddy is a screen-aware voice assistant for Mac, not a chat app in a window.
The product’s core differentiation is context plus voice: it captures the screen under your cursor, answers in real time, and uses a cursor companion to point at the UI. That is materially different from text-first copilots that live in panels.
Alternative-to: Replace tab-switching to ChatGPT, Claude, or docs searches with one keyboard hold.
Buddy’s push-to-talk flow removes the need to copy screenshots, open a browser, or paste context into another app. The page strongly emphasizes speed, no wake word, and no chat window.
Pain-killer: For people who need to understand what’s on their screen fast, Buddy turns screenshots into spoken guidance.
The cursor companion, warm spoken summary, and grounded answers are designed for immediate interpretation of on-screen content, which is a sharper use case than generic productivity assistance.
Primary user
Mac power user who spends all day inside complex desktop apps and wants answers without switching contexts
ICP #1
Mac-based product manager at a SaaS company juggling Figma, Linear, Notion, and browser tabs
Pain
They constantly lose context when switching between apps to understand a screen, decode a workflow, or inspect a UI detail for a stakeholder question.
Why this solves
Buddy stays on top of the screen, captures what they are looking at, and answers in place with both text and voice so they can keep moving.
ICP #2
Customer support lead handling technical screenshots from users on macOS
Pain
They need to interpret user screenshots fast, explain what is happening, and guide customers through UI steps without opening a separate chat window every time.
Why this solves
Buddy is explicitly screen-aware and speaks short guidance next to the cursor, which makes it better for live walkthroughs than a generic chatbot.
ICP #3
Independent Mac developer or designer who lives in keyboard shortcuts and hates modal tooling
Pain
They want quick, hands-free answers while debugging UI states, checking docs, or understanding something on screen, but don’t want another app that interrupts flow.
Why this solves
The hold-to-talk interaction, draggable response window, and cursor companion are built to minimize friction and keep the interaction lightweight.
Strengths
- +The core interaction is instantly understandable: hold Ctrl + Option, ask, release, answer.
- +The screen-aware value proposition is concrete and differentiated instead of vague AI hype.
- +The cursor companion and floating answer window are memorable UI hooks that make the product feel real.
Weaknesses
- −The page buries the actual user outcome under feature language; it explains mechanics better than value.
- −It does not clearly show the killer use cases, so visitors have to infer why this matters.
- −Pricing is confusingly split between hosted and BYOK without a strong explanation of who each plan is for.
- −The product sounds like a demo prototype more than a daily tool because there are few trust signals, testimonials, or real workflows.
- −There is almost no explicit differentiation versus ChatGPT Mac, Raycast, or Claude Desktop beyond screen awareness.
Fix these
- Lead with one concrete use case headline, such as understanding anything on your screen without switching apps.
- Add 3-4 screenshot-based use case demos: bug triage, UI explanation, dashboard interpretation, and support walkthroughs.
- Compare Buddy directly to ChatGPT Mac, Claude Desktop, and Raycast AI in a simple feature matrix.
- Clarify who should choose Hosted versus BYOK with plain-English personas and example cost math.
- Show the cursor companion and draggable answer window in motion with annotated GIFs, not just a Vimeo embed.
Drop-in replacement copy
Headline
Understand any Mac screen fast
Hold Ctrl + Option and ask Buddy.
Ask about what’s actually on screen
Buddy captures the display under your cursor, so the answer is grounded in the exact UI, dashboard, or document you’re looking at. You stop explaining context and start getting useful help.
Stay in flow while it speaks
You get a floating markdown answer and a short spoken summary in a warm voice next to your cursor. That means less reading, less switching, and less friction between question and next action.
Use one gesture instead of a workflow
Hold Ctrl + Option, ask, release, done. The whole product is built around speed, because the best assistant is the one you actually keep using every day.
Choose hosted or bring your own key
Hosted is for people who want it to just work. BYOK is for users who want control and lower ongoing cost, with API keys stored in macOS Keychain.
FAQ
How is Buddy different from ChatGPT for Mac?
Buddy is screen-aware first. It answers from the display under your cursor, so you don’t need to copy context into a separate chat window before getting help.
Who is this actually for?
People who spend all day in complex Mac apps: PMs, designers, support teams, founders, and anyone who keeps interrupting work just to understand what’s on screen.
Do I need to use my own API key?
No. Buddy offers hosted and BYOK options. Hosted is simpler; BYOK is for users who want more control and predictable usage costs.
What does the voice part do?
Buddy speaks a short summary beside your cursor so you can stay focused on the screen. The full answer also appears in a draggable floating window if you want more detail.
Is it always listening?
No. Buddy uses a push-to-talk flow. You hold Ctrl + Option when you want help, then release when you’re done.
Built Buddy: a Mac assistant that answers from your screen. Hold Ctrl + Option, ask out loud, and get a grounded answer with a floating markdown reply + short spoken summary next to your cursor. It’s for people who live in Figma, Linear, Notion, and browser chaos.
Buddy is the “what am I looking at?” button for Mac. Hold Ctrl + Option anywhere, ask a question, and it uses the screen under your cursor as context. No copying screenshots. No opening ChatGPT. No context reset.
Buddy’s whole flow is: hold, ask, answer. That’s it. No wake word. No chat window hunting. No modal maze. If an AI tool makes you stop working to use it, it’s the wrong UX.
Spent way too much time shaving latency off Buddy. Screen capture, response, voice, cursor guidance. The difference between “cool demo” and “daily tool” is often 2 seconds.
If your day is full of dashboards, bugs, and weird UI states, you know the pain. You can either explain the screen in a chat box, or Buddy can look at it and answer in place.
The old workflow: 1. take screenshot 2. open chatbot 3. paste 4. explain 5. wait Buddy cuts that down to one hold key and a question.
Cursor on a confusing dashboard widget? Hold Ctrl + Option and ask: “What does this chart mean?” Buddy answers with a floating markdown card and a short spoken summary right by your cursor.
Buddy doesn’t just chat. It points. It speaks. It stays on top of your work. That tiny difference makes it feel like a real assistant, not another tab.
The reaction so far has been annoyingly consistent: “Wait, I can just ask about the screen?” Yes. That’s the product. Fast enough to use all day, not just show on a launch video.
If a tool makes you reach for it without thinking, that’s the signal. Buddy is built for that loop: hold, ask, answer. Not a chatbot. More like a friend sitting next to your cursor.
Angle: screen-aware alternative to chat apps
I kept seeing the same workflow problem at work: people were asking AI to explain what was on their screen, but the process was absurdly manual. Take screenshot. Open ChatGPT. Paste. Add context. Wait. So I built Buddy for Mac. Hold Ctrl + Option anywhere, ask out loud, and Buddy uses the screen under your cursor as context. It responds in two ways: - a floating markdown answer you can drag around - a short spoken summary next to your cursor The goal wasn’t “another AI app.” It was to remove the tab-switching tax. If you live in Figma, Linear, Notion, dashboards, docs, or support screenshots all day, you already know why this matters. I’d love feedback from people who spend most of their day in desktop apps: what’s the most annoying moment where you currently leave your flow just to understand what’s on screen?
Angle: why the UX is hold, ask, answer
Most AI products still make you change state before they help you. Open a panel. Copy context. Paste text. Think in prompts. That’s fine for a chat session. It’s bad for real work. Buddy is built around three gestures: Hold. Ask. Answer. That’s the entire interaction. It captures the display under your cursor, gives you a grounded response, and speaks a short summary in a warm voice so you can keep your eyes on the screen. There’s a floating response window if you want detail, and a cursor companion if you need guidance on what to look at. The design goal was simple: don’t interrupt the work to help with the work. I’m curious how others think about AI UX on Mac. What’s your threshold for “useful enough to keep installed every day”?
Angle: productivity tool for PMs, support, and makers
Buddy started from a specific observation: a lot of Mac work is really just interpreting screens. A PM looking at a dashboard. A support lead reading a user screenshot. A designer checking a UI state. A founder debugging something in a browser window. In all of those cases, the value is not more text. It’s faster understanding. Buddy is a screen-aware voice assistant for macOS. It stays close to the cursor, grounds answers in what you’re actually looking at, and keeps the experience lightweight enough to use repeatedly. I built it because the existing alternatives felt too general, too chat-first, or too detached from the thing on screen. If your team deals with screenshots, workflows, and desktop apps all day, I’d love to know: where does the most friction happen today when someone just needs to explain “what’s happening here”?
No visuals for this kit yet.
Tagline
A screen-aware voice assistant for Mac
Description
Hold Ctrl + Option, ask out loud, and get a grounded answer from the screen under your cursor. Buddy replies in a floating markdown window and a short spoken summary, so you stay in flow.
Maker's first comment
I built Buddy because I was tired of the screenshot-to-chat-to-answer loop. The moment kept happening: I’d be inside Figma, Linear, Notion, or a browser, hit a weird screen state, and then lose a minute switching apps just to understand what I was looking at. Buddy is my attempt to make that instant. The product is intentionally small: hold, ask, answer. It captures the display under your cursor, gives you a grounded response, and speaks a short summary in a warm voice so you don’t have to leave the task. The floating response window and cursor companion are there to make it feel like a real helper, not a panel you have to manage. I’d love feedback on two things: whether the use case is immediately clear, and whether the hosted/BYOK split makes sense to first-time users.
Pinned maker comment
Would love feedback on the landing page clarity, the phrasing of the core use case, and whether the pricing explanation is simple enough for PMs, support teams, and solo Mac users.
Meta
Stop copying screenshots into chat.
Hypothesis: Mac power users will click because the workflow pain is obvious. Buddy answers from the screen under your cursor, so users stay in context instead of opening another app.
Google Search
Screen-aware voice assistant for Mac
Hypothesis: searchers comparing ChatGPT for Mac, Claude Desktop, or Raycast AI want a faster way to understand what’s on screen. Buddy uses Ctrl + Option to capture context and speak the answer in place.
Reddit Promoted
If you live in screenshots all day:
Hypothesis: indie hackers, PMs, and support folks will engage with a tool that removes the screenshot-explain-switch loop. Buddy is a Mac assistant that reads the screen under your cursor and answers with text + voice.
Subreddits
r/SideProject
Show the exact hold-ask-answer flow with a short GIF and ask for blunt feedback on whether it feels useful or gimmicky.
Rules: No spam, disclose you made it, keep the post demo-heavy, avoid link dumping without context.
r/indiehackers
Share the build story: why screenshot-to-chat is too slow and how you cut it down to one keyboard hold.
Rules: Focus on lessons and metrics, not product promotion alone; posts should invite discussion.
r/microsaas
Position Buddy as a tiny but sticky Mac utility for screen interpretation and workflow speed.
Rules: Small product updates are welcome; avoid hype and keep it practical.
r/EntrepreneurRideAlong
Walk through the launch and ask for feedback on the first-use experience and pricing clarity.
Rules: Be transparent, keep it conversational, and don’t sound like an ad.
r/macapps
Lead with Mac-native workflow value: keyboard shortcut, floating window, cursor companion, low latency.
Rules: Must be relevant to Mac users, include screenshots/GIFs, and avoid obvious self-promo.
Communities
Post as a build log or launch thread focused on UX tradeoffs, latency, and why voice + screen context beats generic chat.
Share the origin story, pricing decisions, and what you learned shipping a Mac utility with BYOK and hosted options.
Join Mac productivity threads, answer questions, and post the product only where users are already discussing tools and workflows.
Cold outreach template
Hey {firstName} — saw you working in {context} and thought of Buddy. It’s a Mac assistant that answers from the screen under your cursor, so you don’t have to copy screenshots into chat. Want me to send a 20-second demo?
Product Hunt timing
Launch Tuesday at 12:01 AM PT, then spend the first 6 hours replying fast to every comment. Tuesday gives you a full weekday tail, and the early comment velocity matters more than the exact hour.
Indie Hackers post ideas
- 01I built a Mac assistant that answers from your screen instead of a chat box
- 02Why I killed the screenshot-to-ChatGPT workflow for Mac users
- 03What I learned building a voice AI that has to feel instant
Competitor alternatives
Current tone of voice
Friendly, product-demo casual, and slightly whimsical. The page literally calls it "Your mac \"buddy\"" and describes the voice as "a friend next to you," which makes the brand feel approachable rather than enterprise-serious.
Your kit is ready. Sign up free to unlock, takes 10 seconds.
7 more X posts · 2 LinkedIn · Product Hunt copy · ad hooks · 100-user playbook · landing critique