Oh My Pi 18.11.0 includes a fix for coding sessions that accidentally pick up project configuration or plugins from shared temporary directories. The release, published October 14, is available with both Apple silicon and Intel Mac binaries. It is worth checking before your next disposable-workspace session.
Where the search stops
When OMP starts without a repository anchor, its upward search could reach executable plugins and instruction files at a shared temporary root. The revised search stops before the current home, active temporary directory and, on macOS, /tmp and /var/tmp. Canonical path handling gives /tmp and /private/tmp the same boundary.
Which configurations remain eligible
An isolated HOME could also expose another account’s configuration through ancestor discovery. The fix skips directories with inactive .omp/agent layouts only above the nearest Git root below those limits, or throughout an unanchored walk. The process-active agent directory is exempt from that marker check.
A deliberately opened repository below those limits keeps its own configuration eligible at or below its Git root. A plain ancestor .omp can still outrank a closer Git root. The change adds neither ownership checks nor a general trust policy for arbitrary writable directories.
One documented edge remains: a non-Git project’s SDK-specific .omp/agent can still be classified as user configuration when that directory is not process-active.
Update and verify
The official CLI reference documents omp update --stable for selecting the stable channel and installing an update. Run omp --version afterward and confirm 18.11.0 or a newer stable release.
The project also documents Homebrew and Bun installations. If your copy is managed through another installation workflow, use its official guidance and check the resulting version rather than assuming that every distribution channel has already caught up.
For Mac developers, the practical reason to update is predictable startup in throwaway workspaces. Keep checking the configuration that belongs to repositories you intentionally open, especially when evaluating unfamiliar projects.
MacDigest has not independently tested the fix. The linked pull request includes regression-test results, but does not establish how widely the earlier behavior occurred.
