To use a signed-in browser from Oh My Pi, first confirm that you are running can1357/oh-my-pi and identify its version. Then verify the Skill provider and command setting in that build, install or expose Tabbit’s Skill in a directory it actually scans, and run a harmless page read through the local Tabbit CLI. Oh My Pi is a fast-moving Pi fork with its own discovery behavior; Pi’s /skill:tabbit instructions are a starting point, not proof that the same path or alias works in every OMP release.
In one Oh My Pi Reddit discussion, a practitioner called it their daily driver, while the original poster said the default token use felt too high (discussion). Another thread focused on the fork’s added features but also noted its fast release pace. These comments support a version-and-settings checklist, not a claim that every build behaves the same.
Key takeaways
Use the local client and verify its actual Skill or shell access.
Check the signed-in page with a harmless read before asking for research.
Save an explicitly named draft and keep a human review checkpoint.
The browser path at a glance
| Surface | Where it runs | What to verify |
|---|---|---|
| Which codebase? | Mario Zechner’s pi project | can1357/oh-my-pi repository |
| Skill invocation | Pi docs describe /skill:<name> | OMP docs describe an optional /skill:<name> command, gated by setting |
| What to verify | Pi version and skill paths | OMP release, providers, skill roots, command toggle |
Verify the client before the session
Do not follow a generic “Pi-compatible” install note blindly. Check the current OMP Skill documentation. The OMP repository exposes its own docs and versioned implementation. Check the active skills settings, use omp --version, and inspect /settings or the current OMP docs for skill roots. OMP docs describe /skill:<name> as an optional interactive command when skills.enableSkillCommands is enabled. For a current OMP-native setup, inspect .omp/skills/<name>/SKILL.md in the project and ~/.omp/agent/skills/<name>/SKILL.md for user skills; OMP can also scan Agent Skills locations such as .agents/skills/ and ~/.agents/skills/ when that provider is enabled. The exact provider precedence can change, so record the installed version and verify the Tabbit Skill appears in that session. If command discovery fails, use OMP’s skill URI/read mechanism or invoke the local Tabbit CLI through its shell tool.
A practical Tabbit workflow for this task
For a migration test, give OMP a release-checklist URL and the output from the last Pi run. Compare the title, checklist version, and approved fields, then save a short difference report as pi-browser-skill-migration-draft.md. This is a review artifact, not a commit. If OMP runs in a container, SSH session, or remote runner, its shell may not reach the desktop Tabbit instance. A supported local handoff is required; do not forward browser cookies or invent a remote bridge.
Use this prompt as a bounded template. Replace internal paths with approved inputs; the sample is not a claim that the named content exists.
In the signed-in Tabbit team handbook, open the approved release-checklist URL. Record the page title, the displayed checklist version, and the three approved fields. Compare them with the previous Pi run. Add the OMP version and any discrepancies to `pi-browser-skill-migration-draft.md`. Leave the handbook unchanged and stop for review.A decision table for the handoff
| Stage | Check | Evidence |
|---|---|---|
| Identify | omp --version; confirm repository/package identity | Version string and install source |
| Discover | Check configured skill roots and enableSkillCommands | Visible Tabbit skill name or explicit read result |
| Connect | Run one read-only Tabbit task against a known page | Expected title and URL, no write action |
Related setup guides
For another client, the same order applies: discover the client skill, check local launcher reachability, verify the signed-in host, then save a reviewable draft. See the Tabbit CLI guide. Start with a test page you can inspect manually, and keep the site action read-only.
FAQ
Is Oh My Pi the same project as Pi?
No. Oh My Pi is a separate fork. Verify the repository and installed version before applying Pi instructions.
Does `/skill:tabbit` always work in OMP?
No. OMP documents the command as optional and controlled by a setting. Confirm command discovery in your build.
Where should the Tabbit Skill go?
Use a path recognized by the active OMP providers and version. Check current OMP docs and settings rather than assuming Pi’s defaults.
Can a remote OMP session use my local browser?
Not automatically. The OMP process needs a supported local handoff to reach the Tabbit profile.
How should I migrate a Skill?
Record version, source path, discovery settings, and a harmless read result before using it on real pages.
Should OMP be allowed to submit forms?
Keep the first browser task read-only. Review the output and approve any later write separately.