Skip to content

Oh-My-Pi ​

Connect Oh-My-Pi (omp), an open-source terminal coding agent, to your Neuronz.ai account with its native extension. Neuronz.ai runs inside ordinary Oh-My-Pi sessions through Oh-My-Pi's own extension system, skills, and MCP. There is no Neuronz.ai launcher or patched omp binary: Oh-My-Pi reads the plugin's package manifest and loads the extension itself in every session.

Prerequisites ​

  • A Neuronz.ai account with a verified email address — see Create your account.
  • Oh-My-Pi 18.0.5 or newer (omp --version).
  • Python 3 on PATH. The plugin's scripts use only the standard library.
  • git on PATH — Oh-My-Pi uses it to download the plugin.

1. Install the plugin ​

Add the Neuronz.ai repository as an Oh-My-Pi marketplace, then install the plugin from it — the same two steps as on Claude Code:

bash
omp plugin marketplace add \
  https://github.com/neuronzai/neuronzai.git
omp plugin install neuronzai@neuronzai

Oh-My-Pi fetches the repository into its own cache, reads the catalogue it shares with Claude Code, and installs a versioned copy of the plugin under its plugin root (~/.omp/plugins). Every later session loads it automatically; there is no flag to pass and no edit to any file you own.

If Oh-My-Pi can't find the plugin
  • Add the marketplace by its git URL, as above. A raw link to the catalogue file cannot serve the plugin, which lives in a subdirectory of the repository.
  • The plugin root follows $HOME and Oh-My-Pi's --profile option. The PI_CODING_AGENT_DIR environment variable does not move it.

Start a new Oh-My-Pi session after installing.

2. Sign in ​

Start Oh-My-Pi and run:

text
/neuronzai:login

The command opens Neuronz.ai in your browser, signs you in there, and stores the login in your system keychain when one is available. The plugin's tools and its automatic steps share that login.

After you sign in, the command asks whether Oh-My-Pi should install plugin updates automatically. See Updating for what that changes.

On a machine without a browser, the command prints a link. Open it on another device, approve the request, then paste the single-use code back into Oh-My-Pi. Run /neuronzai:logout to revoke the machine later.

3. Verify ​

Start a new session. If it opens with ⚠ Neuronz.ai is not signed in, run /neuronzai:login again. A new account starts empty, so a working install shows nothing else at session start until you save something. To check the install itself, list Oh-My-Pi's plugins:

bash
omp plugin list

The row neuronzai@neuronzai (<version>) (user) is the installed package. Inside a session, /mcp lists the Neuronz.ai server as neuronzai:neuronzai ● connected (that is the server's id; the plugin's is neuronzai@neuronzai). It connects on its own — if it shows under "Disabled", a /mcp disable from an earlier session put it on your denylist, and /mcp enable neuronzai:neuronzai clears that.

If a session starts on an Oh-My-Pi build older than 18.0.5, the plugin prints a visible requirements notice.

4. Use the workflows ​

Oh-My-Pi exposes the bundled workflows as namespaced slash commands:

text
/neuronzai:capture
/neuronzai:init-profile
/neuronzai:switch-profile backend
/neuronzai:reload-assets

Skills, commands, and agents you store in Neuronz.ai for the current profile are placed at session start in .omp inside the repository you are working in, which is where Oh-My-Pi looks for project skills and commands. They are not shared with your other repositories or with another agent.

Resuming a session keeps its original directory ​

omp -r <session> restores the directory the session was created in, and --cwd does not override it. Everything that follows from the directory follows the old one: the profile that answers recall, and the skills and commands Oh-My-Pi discovered on disk. Resume a session from another repository and you get the first repository's memory and assets, in the second repository's terminal.

Neuronz.ai cannot change a session's directory after the fact, so it says so instead — at session start you get a notice naming both directories:

⚠ Neuronz.ai: this session is running in /path/it/was/created/in, but you launched it from /path/you/are/in.

Start a new session in the directory you want to work in. Resuming is safe as long as you resume where the session began.

Updating ​

Oh-My-Pi checks its marketplaces for plugin updates every time it starts, and the marketplace.autoUpdate setting decides what it does with a newer release:

ValueAt startup
notify (default)Oh-My-Pi notes the update in its debug log only, so you see nothing and nothing is installed
autoOh-My-Pi installs the update itself
offOh-My-Pi does not check

On the default, the plugin stays on the version you installed until you update it by hand. To stay current without thinking about it, turn automatic upgrades on once:

bash
omp config set marketplace.autoUpdate auto

/neuronzai:login offers to do this for you after you sign in, and changes the setting only if you say yes. The setting is Oh-My-Pi's own, so it covers every marketplace plugin you have installed, not only Neuronz.ai.

Oh-My-Pi refreshes its copy of a marketplace at most once a day, so a new release is picked up on the first startup after that refresh. The upgrade runs while the session starts, so the new extension is loaded from the next session on.

To update right away instead:

bash
omp plugin marketplace update neuronzai
omp plugin upgrade neuronzai@neuronzai

Both lines are needed. upgrade installs the newest release listed in Oh-My-Pi's local copy of the marketplace, and does not refresh that copy on its own — without the marketplace update first, it reports the version you already have. Start a new Oh-My-Pi session to load the updated extension. Your login stays valid across updates.

Uninstalling ​

bash
omp plugin uninstall neuronzai@neuronzai

This removes the lockfile entry and the installed copy. Run /neuronzai:logout first if you also want to remove this machine's login.

Next ​