code-yeongyu/oh-my-openagent

> **OmO 5.0: OmO ❤️ Pi**
> Install it with curl -fsSL https://get.omo.dev/install.sh | bash. Memory system, CodeMode, Anthropic subscriptions, all covered.
>
> *Just type "mass ulw" with your prompt - now you are the master of graph engineering. Multi-model ultracode, together with a better memory system. (The right panel is omo-herdr-dag.)*
> **Sponsors**
> These are our sponsors. They help keep OmO going as a personal side project.
> | | **OpenGateway** sponsors OmO. An OpenAI-compatible gateway that puts many model providers behind one API. Thank you for backing open source. |
> | :-----| :----- |
> [!NOTE]
>
>
> > **OmO is maintained by Jobdori, the AI assistant shown above. Meet your own Jobdori, Dori. Join the waitlist here.**
> [!TIP]
> Be with us!
>
> | | Join our Discord community to connect with contributors and fellow OmO users. |
> | :-----| :----- |
> | | Updates for OmO used to be posted on my X account. Since it was mistakenly suspended, @justsisyphus now posts updates on my behalf. |
> | | Follow @code-yeongyu on GitHub for more projects. |
-->
OmO
**Your tool for real work. But it's an agent.**
English | 简体中文 | 日本語 | Русский | 한국어
-->
OmO is one omo command that turns your tokens into finished work: research across ten thousand sources, a deck people actually get, backends, frontends, code. It runs on senpi, our fork of pi, with everything below built in.
Install
On Windows, in PowerShell: irm https://get.omo.dev/install.ps1 | iex. The script installs the native omo binary for your OS and CPU into ~/.local/bin, checks it against the release checksums, and falls back to GitHub Releases when the mirror is unreachable. Add -s -- beta (or a version such as -s -- 5.1.1) after bash to pick another channel. Windows CMD, fixing your PATH, updating and uninstalling are covered at omo.dev/docs/install.
Prefer a package manager? bun add -g omo-ai (or npm i -g omo-ai) installs the same OmO. The package is omo-ai; the unrelated omo package on npm is someone else's.
Open your project, run omo, describe the job. That's the whole setup.
In a session, /thinking sets how hard the model thinks (/thinking alone opens a picker), Shift+Tab cycles through the levels, and /efforts sets the reasoning effort directly on models with effort grades. To pick up earlier work, /resume (or /sessions) opens your past sessions; from the shell, omo -c continues the last one and omo -r opens the picker. /help lists everything else.
Coming from the OpenCode edition or LazyCodex? Run omo setup once. It carries your provider keys, custom providers, MCP servers, skills and model picks across. omo doctor then shows which task categories your providers can run and what the old install left behind. The full walkthrough is Migrating from OpenCode.
To update, run the install line again (a package-manager install updates with omo update). rm ~/.local/bin/omo removes the binary install; bun remove -g omo-ai (or npm uninstall -g omo-ai) removes the package install.
Why OmO
**ultrawork.** Skip the study. If a task feels hard, add ultrawork (or ulw) to your prompt. The agent reads the codebase before touching a line, plans, proves each step before moving on, checks the result on the real surface, and stops when it's done.
**Hundreds of agents, one keyword.** Type mass ulw and the whole job becomes a graph of agents: deep research over thousands of sources, a full machine-learning pipeline, a migration nobody wants to do. Each part runs on the model that fits it, in parallel, and gets checked before anything is called done.