Skip to main content
omi-cli is the command-line interface to the Omi developer API. It exposes scoped, JSON-friendly verbs for the four primary nouns Omi maintains about you, so you can drive Omi from shell pipelines, CI jobs, AI agent harnesses, or your own personal scripts.

Memories

Facts and learnings the system knows about you.

Conversations

Captured & processed audio/text exchanges.

Action items

Tasks and follow-ups extracted from your captures.

Goals

Tracked progress metrics over time.

Why a CLI?

Omi already ships:
  • a Python SDK (omi-sdk) for Bluetooth and audio capture,
  • a Flutter mobile app, macOS desktop app, and
  • an MCP server (MCP) for Claude Desktop and similar tools.
omi-cli adds a terminal-native, scriptable, JSON-emitting interface to your data. Modern developer tools ship one, such as gh, stripe, vercel, and linear, and AI agents look for one first. The same binary serves a person checking action items in the terminal and an LLM agent piping --json output through jq.

What you can do with it

How it relates to MCP

The two cover different needs:
  • MCP is the right surface for AI assistants embedded in apps that speak the Model Context Protocol (Claude Desktop, Cursor). You don’t see it. The LLM calls tools directly.
  • CLI is the right surface when you want a stable command line your scripts, agents, and shell pipelines can drive, anywhere a process can run.
Both hit the same Omi API and respect the same scopes.

What’s next

Install

Install the CLI with pipx install omi-cli.

Quickstart

Your first commands, end to end.

Command reference

Every verb, every flag.

For agents

Agent contract, exit codes, JSON shape.