Shadow - The interface AI needs. One that sees, hears, and runs.
by•
Shadow is the AI interface for your Mac. It sees your screen, hears your voice, and runs the prompts you build — on a keyboard shortcut, or in your meetings.
🪄 Skills do the work.
Quick Reply drafts emails from what you say and what’s on screen. Voice Typing turns talking into clean text, anywhere. Meeting Skills capture every word and screen, then deliver notes and follow-ups the moment you hang up. Build your own — every Skill is a prompt, a context, and an output.


Replies
Shadow
Shadow
Hey Product Hunt! 👋 We worked really hard on this one. Hope you enjoy it! If Shadow makes even one part of your day a little easier, that means a lot to us. Would love to hear what you think! Your feedback genuinely shapes what we build next. 🙏
Shadow
@escphoenix🫡🫡🫡
Fere AI
Quite amazing. What models are included? BYOK?
Shadow
@pranavprakash Glad you like it! We don't have BYOK available, and we aren't letting users choose specific AI models right now as we're focused on automatically detecting the best context for each situation. That said, it's definitely something we're considering for later.
Shadow
Our team poured a lot into this launch — every detail was deliberate. We focused heavily on making things smoother and more intuitive, so Shadow fits into your workflow rather than the other way around. Hope it genuinely makes your day a little easier. Can't wait to hear how it's working for you 🙌
Shadow
@kevin_lee525 🫡🫡🫡
Shadow
Hey Product Hunt! 👋 We've put everything into this, and I'm genuinely excited to finally share it with you all. I hope you get to experience firsthand how Shadow can change the way you work. Give it a try, and please share any feedback, what you liked, what felt confusing, or what could be better. Every comment helps us make it better. 💪
Shadow
@jayden2 🫡🫡🫡
The “prompt, context, output” shape for Skills is a strong abstraction. The place I’d be most curious to see exposed is context boundaries: when a Skill uses screen state, meeting transcript, selected text, or prior notes, can the user see exactly which inputs were used before the output gets sent or saved?
That matters a lot for trust in quick replies and follow-ups. If the interface makes context visible and editable, Shadow feels less like a hidden automation layer and more like a controllable work surface for AI.
Shadow
@jim_jeffers Appreciate the comment, Jim. We value user privacy, so we've designed Shadow so that you can manually control exactly which data(screenshot, voice input, and etc.) is used for each Skill. For meetings, transcripts, participant data, and others are shared when you use a meeting Skill, but you have full control over which Skill is active and when. Nothing is hidden from the user. It’s meant to be a tool that lets you capture context and run your own prompts with total visibility into what's happening!
That makes sense — the manual control is the important part.
One UX idea I’d be curious about: a small “context receipt” after a Skill runs. Something like: screenshot used, transcript segment used, selected text used, voice instruction used. Even if users choose inputs up front, that receipt would make it easier to audit a quick reply later, especially when the output gets sent into email, Slack, CRM, etc.@jaythesong
Four launches in, still Mac-only. For a solo power user that's fine. But the moment this becomes a team tool you hit the wall immediately if anyone's on Windows. Congrats on the launch!
Shadow
@jared_salois Thanks for the comment! You’re right. The Windows version is taking much longer than we initially anticipated, but we’ve been prioritizing getting the Mac version right first.