Instructions & rules
The global guidance that makes each tool feel like yours, including native rules.
AGENTS.md · CLAUDE.md
At home on
Omarchy
Your tools.
Your setup.
Everywhere.
A familiar AI setup, on every computer. Keep your global instructions, settings, skills, and MCPs in sync—from one quiet corner of your desktop.
CodexClaude Code
Free & open source · Linux · MIT
✦ omaiPREVIEW
Your setup is up to date
Changes sync in the background.
You can keep
working.
Codex2 skills · 3 settings
Claude Code1 instruction · 2 MCPs
OpenCode1 skill · 2 settings
● Automatic sync on
Just now
Your changes are safe here
The remote is unavailable.
omai will retry when
connected.
✓ Applied to your local tools
✓ Saved on this computer
◷ Waiting to reach your remote
Keep working offlineNo action needed
You choose what to keep
Both computers edited this file.
Both versions are
saved.
codex / instructions.md
THIS COMPUTER
Keep responses concise.
REMOTE VERSION
Include short examples.
Review, choose, confirm.Your decision.
Interactive preview · sample configuration, not your device.
01 Your Git remote02 Works locally03 No omai account04 Open source
01 / YOUR SETUP, TOGETHER
Pick up where you left off.
Each provider keeps its own configuration. A shared workflow doesn’t have to mean identical tools.
Skills & resources
Your reusable skills and their supporting text files, ready on another computer.
SKILL.md + supporting files
Tool preferences
Supported global model, reasoning, permission, and interface preferences.
Provider-specific settings
MCP connections
Native server declarations and environment references. Credential values stay local.
Commands · URLs · options
Supported hooks, agents, commands, and plugin declarations are included too. Explore compatibility ↗
02 / A QUIET DAILY ROUTINE
Set it up. Get back to work.
No extra dashboard to babysit. Your bar tells you when something needs attention.
Choose your home base
Connect a Git repository you control, or start locally. Setup happens inside the plugin window.
Edit where you already do
Change supported provider files or your editable sync source. omai picks up those changes automatically.
Bring another computer along
Install omai there and connect the same remote. If versions differ, review and choose what to keep.
03 / YOUR CONFIGURATION, YOUR CALL
Your remote.
Your control.
omai synchronizes through ordinary Git. There’s no omai cloud account, hosted configuration database, or usage analytics in the plugin.
Authentication stays with your Git tools and AI providers. Use a trusted remote: configuration can include executable hooks and commands, and content checks cannot recognize every secret.
Read the privacy policy →
This computerYour native tools
Your Git remoteYour access rules
Your Git remoteConfiguration history
Another computerThe same familiar setup
Local recovery stays local. Only validated sync source enters Git.
04 / ONE SMALL ADDITION
Make room for omai.
Add the plugin to Omarchy, then do the rest in its window. Your AI tools keep working as usual.
Requires Omarchy 4.0.3 or later on Linux x86-64, Git, curl, Python 3.11+, and a systemd user session. Bring a Git remote to sync across computers.
Installation & documentation ↗
Terminal Install the plugin
omarchy plugin add https://github.com/pablousx/omai.git
--enable --yes
- Open the ✦ icon. Choose Set up omai.
- Connect a remote or stay local. Review the import options.
- Start syncing. Setup installs the companion executable when needed.
Setup uses the matching published release. For an unpublished local checkout, the panel offers a source-build retry.
05 / GOOD TO KNOW
A few practical details.
Does omai require a cloud account?
No omai account is needed. Local sync works without a remote. To sync across computers, bring an existing Git repository and its usual authentication.
Will it mix my providers’ configurations?
Newly discovered instructions, skills, rules, and MCP declarations stay scoped to their provider. Explicitly shared source entries are also supported when you want them.
What happens while I’m offline?
Local reconciliation continues and your changes remain on your computer. When automatic sync is running, omai retries the remote connection.
What if two computers change the same thing?
omai keeps both versions and asks you to choose. It doesn’t silently pick the newest edit or force-push over another computer’s work.
What stays out of the synced source?
Credentials, account databases, sessions, histories, caches, and project-level configuration stay local. Resource files must be text. Linked user skills are read as snapshots; omai does not overwrite their package-managed targets.
Can I pause, undo, or stop using it?
Yes. Pause from the panel, review recovery history in Advanced, or confirm Undo last apply. Clearing settings stops sync and returns to setup while keeping your configuration files. Removing only the bar plugin does not stop its companion service; see the operations guide.