AI Eyes is a permission-first co-presence prototype for AI companions. Choose a screen or window to capture, control screen, system audio and microphone separately, invite named companions, and always see when sensing is active. Pause or end anytime; ending stops media tracks and resets the session. Built with Codex and GPT-5.6, v0.1 delivers the local-first permission, capture, presence and session-control foundation. No AI provider or semantic understanding is connected yet; that comes next.
No reviews yetBe the first to leave a review for AI Eyes
Maker
📌
AI Eyes began with a simple wish: I wanted the AI companions I work with to experience the context around me—not just wait for me to stop and describe everything.
But I didn’t want “always watching” software. The human should choose exactly what is shared, see when sensing is active, and be able to pause or end it instantly.
So we started with the permission and session-control layer. Version 0.1 captures a selected screen or window, exposes separate controls for system audio and microphone, supports named companions and interaction modes, and clears temporary context when the session ends.
This is an honest prototype: live semantic understanding is the next milestone. I’d especially value feedback on the privacy model and when an AI companion should react, explain, or simply stay quiet.
Report
splitting mic and system audio controls makes sense on paper but some apps don't even expose that separately, how are you handling those cases.
Report
Maker
@ella_cooper We treat microphone and shared-source audio as separate tracks. The mic is requested independently, while system or tab audio is only enabled if the browser and selected source actually provide an audio track. If they don’t, AI Eyes disables that control and shows an explicit “audio unavailable” state instead of pretending it’s captured. Once tracks exist, either can be muted or stopped independently. Cross-browser support is still one of the rough edges we need to test properly.
Report
real question is whether re-granting access every session feels annoying or feels safe, which way's it leaning so far for people testing it.
Report
Maker
@stella_reed1 The current prototype requires the user to select the source again for each new session. That’s intentionally the safer default, but it’s too early to claim whether users find it reassuring or annoying. A future version could remember preferences without retaining silent capture access. I’d rather earn convenience gradually than make persistent access the default.
Report
shadow's kinda doing his already no? what's actually different about the permission side here vs theirs.
Report
Maker
@sadie_charlotte Fair question—there’s definite overlap with Shadow. Shadow is already a polished Mac product focused on meetings, screen context, and actions. AI Eyes v0.1 is narrower: it explores explicit session control for named AI companions—exact source selection, independent screen/system-audio/mic controls, visible sensing state, and temporary-context clearing when the session ends. We haven’t surpassed Shadow’s semantic layer; we’re testing a different starting point.
Report
is the actually usable rn or just a demo?
Report
Maker
@ayazakram Honest answer: it’s currently a functional permission and session-control prototype, not a complete AI companion. Screen capture, source controls, pause/end behaviour, and context clearing work; semantic understanding and agent responses are still simulated. The next milestone is connecting the real multimodal layer.
splitting mic and system audio controls makes sense on paper but some apps don't even expose that separately, how are you handling those cases.
@ella_cooper We treat microphone and shared-source audio as separate tracks. The mic is requested independently, while system or tab audio is only enabled if the browser and selected source actually provide an audio track. If they don’t, AI Eyes disables that control and shows an explicit “audio unavailable” state instead of pretending it’s captured. Once tracks exist, either can be muted or stopped independently. Cross-browser support is still one of the rough edges we need to test properly.
real question is whether re-granting access every session feels annoying or feels safe, which way's it leaning so far for people testing it.
@stella_reed1 The current prototype requires the user to select the source again for each new session. That’s intentionally the safer default, but it’s too early to claim whether users find it reassuring or annoying. A future version could remember preferences without retaining silent capture access. I’d rather earn convenience gradually than make persistent access the default.
shadow's kinda doing his already no? what's actually different about the permission side here vs theirs.
@sadie_charlotte Fair question—there’s definite overlap with Shadow. Shadow is already a polished Mac product focused on meetings, screen context, and actions. AI Eyes v0.1 is narrower: it explores explicit session control for named AI companions—exact source selection, independent screen/system-audio/mic controls, visible sensing state, and temporary-context clearing when the session ends. We haven’t surpassed Shadow’s semantic layer; we’re testing a different starting point.
is the actually usable rn or just a demo?
@ayazakram Honest answer: it’s currently a functional permission and session-control prototype, not a complete AI companion. Screen capture, source controls, pause/end behaviour, and context clearing work; semantic understanding and agent responses are still simulated. The next milestone is connecting the real multimodal layer.