Omi Open-Source Second Brain Platform

repository·main·Indexed 11 days ago

https://github.com/basedhardware/omi

An open-source 'second brain' platform that captures screen and conversation data, transcribes it in real-time, and provides an AI-powered chat interface. Includes a Flutter-based mobile application for iOS and Android, a memory ingestion pipeline, and backend infrastructure including an Agent VM reaper and self-hosted Deepgram Kubernetes deployments.

Tokens
623.7K
Snippets
1.2K
Records
2.6K
Agent score
96%

What's inside Omi

  1. Overview of Omi Triangle v2

    main

    Omi Triangle v2 is an upgraded hardware version of the Omi Triangle v1. Key improvements in v2 include:

    • Added Memory: Support for external storage via a Micro SD card.
    • Speaker: Integrated audio output capabilities.
    • Configurable Momentary Button: A tactile button for user interaction.

    Note: This is currently a developer version. Some new hardware functionality may not be fully supported by the existing firmware. If you are using a device assembled before August 23, 2024, you must perform a speaker function correction to ensure proper operation.

  2. Overview of ClickUp Voice Task Creator for OMI

    main
    The ClickUp Voice Task Creator is an OMI plugin that enables voice-activated task creation in ClickUp. Users can trigger task creation by saying specific phrases followed by task details. The system uses AI to extract task names, descriptions, lists (via fuzzy matching), priority, and due dates/times. It supports timezone-aware parsing and uses a smart collection mechanism to handle multi-segment voice inputs.
  3. Overview of OMI-Composio Integration

    main
    The OMI-Composio plugin enables users to connect external services via Composio to extract memories and facts from platforms like Notion and import them directly into an OMI account. It features OAuth-based Notion connectivity, automated memory extraction from pages and databases, and a mobile-optimized UI.
  4. Overview of Omi SDKs

    main
    Omi SDKs allow you to build applications that connect directly to Omi hardware via Bluetooth Low Energy (BLE). These SDKs enable features such as audio streaming and real-time transcription without requiring a dependency on Omi's backend infrastructure, allowing for completely standalone applications.
  5. Overview of File Index and Knowledge Graph Parity (Mac vs. Windows)

    main

    This audit compares the capabilities of the File Index, Knowledge Graph (KG), and Memory Graph features between macOS and Windows implementations in OMI.

    Key functional areas include:

    • File Indexing: Scanning roots, directory-skip policies, incremental scans, and file-type categorization.
    • Knowledge Graph (KG): Local storage schemas (nodes/edges), backend fetching/rebuilding, and client-side scoping.
    • Onboarding & AI: AI-driven file exploration for entity extraction (creating a 'digital profile') and chat agent context enrichment.
    • Memory Graph Visualization: 3D/2D physics models and interactive UI (drag, rotate, pan, zoom).

    Note: While many features are present on Windows, some (like incremental background refreshes and AI-driven onboarding exploration) are currently absent or weaker compared to the macOS baseline.

  6. Overview of the Omi Python SDK

    main

    The Omi Python SDK is a pip-installable library designed to interface with Omi wearable devices. It provides capabilities for:

    • Bluetooth Connection: Connecting to Omi hardware devices.
    • Opus Decoding: Decoding Opus-encoded audio streams into PCM format.
    • Real-time Transcription: Leveraging Deepgram for real-time Speech-to-Text (STT).
  7. Overview of Omi Firmware

    main

    The Omi firmware is the core software for the Omi AI wearable device. It is built on the Zephyr RTOS and manages critical hardware functions including:

    • Audio Capture: Microphone input and audio buffering.
    • Codec: Processing raw audio data.
    • Transport: Bluetooth connectivity and audio streaming.
    • Storage: SD card operations and audio file management.
    • Battery & LED Control: Power management and visual status feedback.

    Note: Due to its complexity, this firmware cannot be built using the Arduino IDE; it requires a professional toolchain (typically involving CMake and the nRF Connect extension).

  8. Overview of Omi DevKit 2 features

    main

    Omi DevKit 2 is an upgraded wearable in a necklace form factor. Key hardware specifications and features include:

    • Processor: Xiao nRF52840
    • Storage: 8GB onboard storage, which enables Standalone Recording Mode (recording without a phone connection).
    • Audio: Built-in speaker for audio feedback and notifications.
    • Interaction: A programmable button that replaces the traditional on/off switch.

    Note: While DevKit 2 supports standalone recording, you must still connect the device to the Omi app for transcription processing.

  9. Overview of the Omi Monitoring Stack

    main

    The Omi backend uses a Prometheus, Grafana, and Loki observability stack running on Google Kubernetes Engine (GKE). This stack provides metrics collection, log aggregation, and visualization for all backend services.

    Core Components:

    • Prometheus: Metrics collection with 10-day retention and 50Gi storage.
    • Grafana: Visualization and alerting. Access via monitor.omi.me (prod) or monitor.omiapi.com (dev).
    • Loki: Log aggregation using a GCS backend with 15-day retention.
    • Alloy: A DaemonSet used for collecting pod logs via the Kubernetes API.
    • Prometheus Adapter: Translates Prometheus metrics into Kubernetes custom/external metrics APIs to enable Horizontal Pod Autoscaling (HPA).
    • Stackdriver Exporter: Bridges GCP Load Balancer metrics into Prometheus.
  10. Overview of Public Holidays Omi App

    main
    The Public Holidays Omi App is a standalone, no-authentication application that allows users to look up public holidays, upcoming holidays, long weekends, and supported countries via Omi conversations. It is backed by the public Nager.Date API and does not require environment variables, OAuth, or API keys for operation.