What would you like to share?

Please choose the correct board before posting so we can review and respond faster:

  • Bugs β†’ something is broken, incorrect, or not working as expected

  • Questions β†’ you need help, clarification, or want to know how something works

  • Feature Requests β†’ ideas for new features or improvements

Recording Status Indicator (LED + Haptic Feedback)

When I'm using double-tap to start/stop recordings, I have zero way to know if Omi is actually recording without digging out my phone. If it's in my pocket and I'm in the middle of an important conversation, that means unlock phone β†’ open Omi app β†’ pray Bluetooth is connected β†’ check status. That's a lot of friction for something that should be instant. What I'm asking for is simple: give me a physical indicator on the Omi device. πŸ”΄ LED light β€” solid or pulsing when recording is active. Red, green, whatever. Just something I can see at a glance. ⏰ Haptic/buzz pattern β€” a distinct buzz on start and another on stop so I can feel the confirmation on omi without looking at my omi or device. In high-value conversations β€” client meetings, important calls, something I know I'm going to want to remember β€” I need to know I'm capturing it in real time, not wonder about it afterward. Every wearable and recording device worth its salt has some version of this. It's table stakes UX. This would be a big productivity win for anyone using Omi in professional settings.

Nick K7 4 months ago

1

Feature request

Hi Omi Team,I'm a user who relies on Omi for important meetings and work recordings. I wanted to flag an urgent feature request: deleted conversation recovery.Currently, once a conversation is deleted, it's gone permanently with no way to recover it. For users with dexterity challenges, accidental deletions are far too easy to trigger when scrolling through the conversation list. I've already lost several critical meeting recordings this way.I'd suggest either:β€’A trash/recycle bin with a short recovery window (e.g., 7 days) β€’A confirmation dialog before deletionβ€’Or both. This is both a usability and accessibility issue that I imagine affects other users too. Happy to discuss further or provide more context.You can also raise this as a GitHub issue at github.com/BasedHardware/omi/issues or on Discord at discord.omi.me.Thanks for building such a great product β€” just want to make it safer for everyone.[Your Name]Want me to tweak the tone or add anything specific?

Jason Watson 3 months ago

Active listening minutes

I like the appand cv1 device a lot actually more than I expected. An issue I ran into though is that it seems the active listening minutes aren’t very accurate or atleast displayed to the user when this counts. 1200minutes should be plenty to test things out but I only had the device since a day and a half and used it for about 40minutes total and it seems that muting the device currently still counts againt the quota but I also turned it off and still somehow ended up with about 4000 words and 850minutes of active listening. I have 8 total transcripts each about 10minutes (slightly less) and enabled the option to use the server side voice detection too (the one to only transcribe if voices are detected) I love that the app is built as open as it is to allow seperate transcription servers but I actually planned to use the subscription version because it doesnt require any additional setup. To be clear I think the limits are fine just it was a bit confusing for me to see 60% of it gone after the first day where I cant see when it is counting as β€œlistening”. Having this either more transparently displayed to a user or factoring in silence or at the very least the mute toggle would help with that. Also that the light on the device does not show when it is muted is kind of a problem as I intended to use the device without my phone in reach (i could have used the phone mic in that case…) But I currently feel the need to monitor the app closely to see if I’m not muted or making sure the device disconnected (even with muting) to not drain the minutes to 0, but I’d like it to be on and just toggle the mute to not have the startup delay, also having the color would help other identify when the device is recording so they dont just have to trust me saying β€œyeah its glowing blue but its muted” Any help with this would be greatly appreciated

Jan Lunge 4 months ago

1

Bug in MCP OAuth endpoint (/v1/mcp/sse) β€” inconsistent Unknown OAuth client and Server not found errors

Hello, I'm trying to connect the Omi MCP server (https://api.omi.me/v1/mcp/sse) as a Custom Connector in Claude (claude.ai), following the exact guidance shown on the "Developer Settings" screen of the Omi app, which specifies using: OAuth Client ID: omi Client Secret: my MCP API key (omi_mcp_...) When attempting to connect, I receive inconsistent errors across different attempts, using the exact same configuration: {"error":"invalid_request","error_description":"Unknown OAuth client"} {"type":"error","error":{"type":"not_found_error","message":"Server not found","details":{"error_visibility":"user_facing"}},"request_id":"req_011CdNonH1Hcr24nfV1LiUEB"} I've tried recreating the connector from scratch multiple times, with different names, double-checking the URL and credentials each time β€” the errors persist, alternating between the two. This suggests the client_id: omi may not actually be registered/recognized on your OAuth authorization server, despite being the value indicated by the app itself. Could you please check the configuration of the /v1/mcp/sse endpoint and the omi OAuth client? Thank you.

Adriano Batista da Mota 1 day ago