A native macOS app for omo, the coding agent.
Skills on /, parallel agents you can watch, todos and goals, and an Aside-style side chat, in one window.
Install · Feature tour · Shortcuts · How it works · Development
OmO UI runs the omo you installed with curl -fsSL https://get.omo.dev/install.sh | bash. It starts omo app-server with your login-shell environment, so it uses the same sessions, skills, models and credentials as omo in your terminal. The interface comes from the DeepSeek Harness web GUI (MIT), restyled and rewired for omo.
On each app launch, automatic updates check native omo with omo update --dry-run before starting the app server. The compiled updater prints replacement instructions rather than installing, so OmO UI runs the official installer for the reported version in the located launcher's directory; it verifies SHA-256 and replaces the executable atomically without editing shell profiles or removing other installs. The check is limited to 20 seconds, installation to 120 seconds, and version verification to 20 seconds. Offline, timeout, unsupported installations, and other failures leave startup enabled with a notice in Settings > omo. The window opens immediately; no running app server is interrupted by an update. Settings > omo shows the result and an automatic-update toggle (on by default, changes apply on the next app launch). Crash recovery and the Restart omo button do not repeat the update.
OmO for iPhone can control this Mac's omo over a USB cable: install the iPhone app, connect the cable, and keep the app open on the phone. OmO UI connects automatically while it runs, and Settings > iPhone shows the connection and device. The bridge is on by default; set OMO_UI_IPHONE_BRIDGE=0 to disable it. See the iOS guide and the USB protocol.
- Skills on
/: pick/ulw-loop,/mass-ulwor any skill omo can load for the workspace; several skills can go into one message. - Watch the agents work: DAG runs, waves, child tasks, todos and the session goal update live while omo works.
- Ask on the side with
/btw: a side chat answers from the session's context in its own panel and never touches the session. - Edit or regenerate: change an earlier message or reroll the last answer; each opens a branch and keeps the original session.
- Accounts and quota: see every Claude and ChatGPT subscription account's 5-hour and weekly usage, and add accounts through omo's own sign-in.
- Approvals and questions inline: allow a command once or for the session, or answer omo's questions without leaving the conversation.
- Your history, restored: every omo session is listed, including the ones you started in the terminal, with full tool and reasoning history.
- Installs omo for you: if omo is missing, the first screen offers to run the official installer.
- Light, dark, English and Korean.
OmO for iPhone is the native SwiftUI companion: connect your iPhone to the Mac with a USB cable to browse sessions, stream replies, send or steer omo, stop a turn, and answer approvals and questions. The Mac keeps running omo and holding its credentials; the phone communicates through Apple's USB multiplexer, not Wi-Fi or Bluetooth. iOS suspends the app in the background, so keep it open while you use it. See the iOS guide for building, signing, installing, and the 7-day renewal of free provisioning.
The tour below was captured from the built app by npm run screenshots, which plays scripted demo sessions through the repository's fake omo (tests/fixtures/fake-omo.mjs): every screen is the real interface, and none shows a real person's sessions. The last screenshot is the same app on the installed omo with a real model.
Type / at the start of the message or after a space. The menu lists the skills omo can load for the session's workspace, with their scope and description, plus the /btw command. Arrow keys move, Enter or Tab inserts, Escape closes. Up to five skills go into one message, and the sent message shows each as a chip.
When omo fans work out, for example with mass-ulw, the Activity chip in the header counts running work. Open it to see each DAG run with its waves and node states, the live activity of running nodes, and every child task with its agent, model, progress and result. omo's todo list and the session goal sit above the composer.
Type /btw <question> (or /side <question>), press ⌘E, or click Side chat. The answer streams into a panel beside the conversation, docked or as an overlay in a narrow window, while the main turn keeps running. Each side chat is its own omo session that receives the recent conversation as read-only background; nothing is added to the main transcript. Side chats are kept per session as BTW #1, BTW #2 and so on.
When omo needs permission, the card shows the command, the working directory and, when omo gives one, the reason. Allow it once, allow it for the session, or deny it with an optional reason; with the card focused, Enter allows once and Escape denies. Questions from omo arrive as cards with their options and, when omo allows it, a free-text answer.
Answers stream as Markdown with headings, tables, inline code and highlighted code blocks; reasoning, searches, file edits and commands appear as compact tool cards in the order omo ran them.
If omo is missing, OmO UI says so and offers the official installer, or the command to paste into a terminal. After the install it reconnects on its own.
Every label in the window is available in Korean; the macOS menu bar stays in English. Choose the language in Settings, or follow the system language.
The same window on the installed omo with a real model, with the sidebar collapsed (⌘\).
Requirements: macOS 12 (Monterey) or later on Apple silicon, and omo from the official installer (curl -fsSL https://get.omo.dev/install.sh | bash). If omo is missing, the onboarding screen offers to run the installer. Building from source needs Node.js 22 or later and npm.
brew install --cask realsigridjin/tap/omo-uiThe cask installs the latest GitHub release into /Applications and clears the quarantine flag, because the app is ad-hoc signed and Gatekeeper would otherwise refuse to open it. brew upgrade --cask omo-ui updates it; quit OmO UI first.
curl -fsSL https://raw.githubusercontent.com/realsigridjin/omo-ui-macosapp/main/scripts/install.sh | bashThe script downloads the arm64 zip of the latest release, replaces /Applications/OmO UI.app (set OMO_UI_APP_DIR to install elsewhere), clears the quarantine flag, and refuses to run while OmO UI is open.
npm ci
npm run package:mac
npm run install:appnpm run package:mac writes release/mac-arm64/OmO UI.app, a DMG and a zip into release/. npm run install:app copies the app into /Applications (or ~/Applications when /Applications is not writable), replaces an older copy, and clears the quarantine flag. Quit OmO UI before installing; the script refuses to replace a running app.
Open release/OmO UI-<version>-arm64.dmg and drag OmO UI into Applications.
Builds are ad-hoc signed, not signed with an Apple Developer ID or notarized, so Gatekeeper blocks a copy that carries the quarantine flag (for example, a DMG or zip you downloaded). Either right-click the app in Finder, choose Open, and confirm, or clear the flag:
xattr -dr com.apple.quarantine "/Applications/OmO UI.app"| Keys | Action |
|---|---|
| ⌘N | New session |
| ⌘E | Show or hide the side chat |
| ⌘\ | Show or hide the sidebar |
| ⌘, | Settings |
/ |
Skills and commands menu: ↑ ↓ to move, Enter or Tab to insert, Esc to close |
| Enter / Shift+Enter | Send, or steer the running turn / new line |
| Enter / Esc on an approval card | Allow once / deny |
- New session: choose a workspace folder; omo runs with that folder as its working directory. Recent folders are remembered.
- Sidebar: lists every omo session, including sessions you started in the terminal, grouped by workspace and searchable. The pills under the search keep only running sessions, or sessions updated today or in the last 7 or 30 days. Selecting one loads its full history.
- Conversation: answers stream as they are written. Reasoning, tool calls (commands, file edits, searches) and their results appear as cards.
- Skills: type
/at the start of a message or after a space to list the skills omo can run in the session's workspace, plus the/btwcommand; the list loads once the session has started. Use the arrow keys and Enter or Tab, or click, to insert a skill; Escape closes the list. Pick up to five skills for one message; OmO UI sends them to omo as/skill:namecommands in front of your text. - omo's own message parts: sent and restored messages show invoked skills as chips, with their instructions behind Show skill instructions. Reminders and pointers that omo adds to a message fold into an omo context chip, and session titles show
/skillnames instead of the injected text. - Provider errors: when the model provider fails (for example a timeout or a billing error), the turn shows the error omo recorded instead of staying empty.
- Activity: when omo spawns child tasks or runs a DAG (for example with mass-ulw), an Activity chip in the conversation header counts running work against the total. Click it to list each DAG run with its status, node counts and waves, every node with its state (pending, blocked, scheduled, running, completed, failed, cancelled or skipped) and the latest activity of running nodes, and each child task with its category or agent, model, status, progress and result or error.
- Todo list and goal: omo's todo list appears above the composer with done/total counts; expand it to see each phase and item. A goal set in the session (for example by ulw-loop) shows below it with its status, objective and time used.
- Restored sessions: a session opened from the sidebar shows the last todo list and the child tasks recorded in its session file, tagged restored. DAG runs and live progress appear only while omo reports them.
- Approvals and questions: when omo asks for permission or asks you a question, the app shows it inline; answer to let the turn continue.
- Stop and steering: Stop interrupts the running turn. Sending a message while a turn runs steers it; a
/btwmessage goes to the side chat instead. - Side chat (/btw): type
/btw <question>(or/side <question>) to ask a side question without touching the session, or press ⌘E or click Side chat in the header. The answer streams into a side panel beside the conversation (over it in a narrow window), and the session's transcript gets nothing, even while its turn runs. Each side chat is its own omo session in the same workspace; its first message carries the session's recent messages (at most 64 messages and 64 KiB) as read-only background with an instruction not to edit files, run state-changing commands or start subagents unless you ask. Remove the conversation chip before asking to start without that background. Side chats are kept per session: the picker lists them as BTW #1, BTW #2 and so on, follow-ups continue the selected one, and deleting the session deletes its side chats. They never appear in the sidebar. omo's own/btwexists only in its terminal UI, so OmO UI never sends/btwto omo. - Edit and regenerate: hover a sent message and click the pencil to edit it (⌘↩ sends, Esc cancels), or click Regenerate under the last answer. Both write a new session holding the conversation before that message, titled "… (edited)", resume it and send there; the original session stays unchanged. Both wait until no turn of the session runs.
- Accounts and quota: Settings > Accounts lists the subscription accounts in omo's
~/.omo/agent/auth.jsonwith each account's usage windows (Claude 5-hour, weekly and extra usage; ChatGPT windows and plan), how much is used and when it resets. The app reads usage with each account's own token in the main process; tokens never reach the window. Accounts whose token has expired fold into one line. Add account opens omo in Terminal running/claude-account add,/gpt-account addor/login, so omo performs and stores the sign-in; the list refreshes when you return. Pin and Remove call omo for the accounts omo lists. - Model picker: shows the model omo is running and switches models for the next turns.
- Settings: theme (system, light, dark), language (system, English, Korean), omo diagnostics (binary path, version, where it was found, process id, whether the login-shell environment was captured, and the
PATHomo runs with), restart omo, and reinstall omo. MCP lists servers, connection status, and expandable tools from omo's~/.omo/agent/mcp.json; use Refresh to reload, and log in through omo in the terminal when needed.
flowchart TB
subgraph App["OmO UI.app"]
R["Renderer<br/>React + DeepSeek Harness GUI"] <-->|"allowlisted IPC"| M["Electron main"]
end
M <-->|"JSON-RPC over stdin/stdout"| S["omo app-server --listen stdio://"]
S -->|"writes"| F[("~/.omo/agent/sessions/*.jsonl")]
M -.->|"reads full history"| F
The Electron main process starts omo app-server --listen stdio:// as a child process and talks to it over JSON-RPC on stdin/stdout. The child receives your login-shell environment (captured by running $SHELL -ilc), so it sees the same PATH, API keys and configuration as omo in your terminal. The omo binary is found in this order: ~/.omo/install.json, ~/.local/bin/omo, then your login-shell PATH. Session history is read from omo's session files under ~/.omo/agent/sessions. Quitting the app stops the omo child.
- omo not found: install it with
curl -fsSL https://get.omo.dev/install.sh | bash, or use the install button on the onboarding screen. Settings shows the binary in use and where it was found. To force a specific binary, launch withOMO_UI_OMO_BIN=/path/to/omo open -n "/Applications/OmO UI.app". - Works in the terminal but not in the app: apps launched from Finder do not inherit your terminal's environment. OmO UI reads your login shell's environment, so export
PATHand API keys in a login-shell file (~/.zprofileor~/.zshrcfor zsh), then use Restart omo in Settings. - A skill is missing from the
/list: the list comes from omo for the session's workspace after the session starts. Workspace skills live in<workspace>/.omo/skills/<name>/SKILL.md. Skills that omo could not load are counted in a warning row at the bottom of the list. - omo terminal commands such as
/modelor/compact: they exist only in omo's terminal UI; use the model picker in the composer instead. - Reset preferences: quit the app and delete
~/Library/Application Support/OmO UI/preferences.json(theme, language, recent workspaces, model). omo's own sessions and configuration are not stored there.
npm ci # also downloads the Electron binary (postinstall)
npm run dev # Vite dev server (renderer hot reload) + Electron
npm run typecheck
npm test # vitest unit tests
npm run test:e2e # Playwright-Electron against a fake omo
OMO_UI_E2E_REAL=1 npm run test:e2e:real # Playwright-Electron against the real omo
npm run package:mac:dir # build only release/mac-arm64/OmO UI.app (no DMG/zip)
npm run icon # re-render build/icon.icns and build/icon.png from build/icon.svg
npm run screenshots # re-capture docs/media from the built app (ffmpeg encodes the GIF)npm run screenshots drives the built app with Playwright against the demo scenes in scripts/readme-demo.mjs, played by tests/fixtures/fake-omo.mjs when FAKE_OMO_DEMO is set. node scripts/readme-media.mjs --only hero,migrate,korean,onboarding,gif re-captures a subset. The real-omo screenshot is not produced by the script; it was taken from a session on the installed omo in a throwaway workspace.
Environment variables (defined in shared/ipc.ts):
| Variable | Effect |
|---|---|
OMO_UI_OMO_BIN |
Absolute path of the omo binary; when set, no other location is tried. |
OMO_UI_QA_PICK_DIR |
Folder returned by the workspace picker without opening the native dialog (tests and QA). |
OMO_UI_USER_DATA |
Overrides the app's data directory (tests and QA). |
OMO_UI_DEV_URL |
Renderer dev-server URL loaded instead of the bundled dist/index.html. |
- The interface, design tokens and icons are taken from DeepSeek Harness, Copyright (c) 2026 DeepSeek, MIT License. See NOTICE.
- The Geist and Geist Mono fonts (
src/dsh/theme/Geist-OFL.txt) and the Montserrat font (src/dsh/theme/Montserrat-OFL.txt) are licensed under the SIL Open Font License 1.1. - The side chat's layout follows a study of the Aside browser's side panel; no Aside code, artwork or fonts are included.
- The OmO UI app icon is an original design.
MIT. See LICENSE.











