oh-my-pi Just Shipped Custom Role Management in Model Hub

oh-my-pi shipped 2 commits in this window, both by can1357, targeting two sharp pain points: role flexibility and session retrieval speed.

What Changed

Custom role management in Model Hub. You can now define and save custom roles directly inside the Model Hub. Instead of picking from a fixed set of system personas, you create roles tuned to your workflow — “code reviewer,” “docs writer,” “architecture critic” — and persist them across sessions. No more re-pasting system prompts every time you switch contexts.

Tiered search session selector. The session selector got a performance overhaul. Instead of scanning every session linearly, it now uses a tiered search — recently used sessions first, then recent-by-date, then full fallback. Result: the session picker snaps open instead of stuttering on accounts with hundreds of sessions.

Why It Matters

Custom roles make oh-my-pi viable for teams where different people need different agent behavior for the same codebase. A junior dev’s “learning mode” role vs a senior’s “audit mode” role — both persisted in the hub. The tiered search fix is ergonomic: if you’ve ever waited for a session list to render, that delay is gone for 90%+ of lookups.

The Takeaway

oh-my-pi is investing in UX polish and configurability, not just raw model support. Custom roles and faster sessions lower the friction for daily use. See how it compares in our oh-my-pi deep dive.