I've been a Shadow user for well over a year now and find it a major part of my workflow.
I was first drawn to Shadow due to its offline transcription. This is a considerable plus in highly regulated industries. The automation of skills is also another great time saver, such as exporting Markdown meeting notes to a folder for synchronization or connecting with Obsidian and other note-taking apps.
Now they've introduced screen recording, which gives the models much more context about what you were doing. This should be a significant boost in productivity and recall.
It would be difficult to keep up with work without it. I don't know how Iβor anyone elseβgot by without it before it existed.
Shadow
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Β
This is exactly the kind of tool I've been looking for to cut down on repetitive Mac tasks. Does it work well with multi-step workflows, or is it better for single commands?
Shadow
@rich_nashawatyΒ Hey Rich! thanks for the comment. Currently, it's a single command but more agentic / multi-step workflow is where we are headed!
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
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π«‘π«‘π«‘
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Β π«‘π«‘π«‘