Start here
Oh My Pi, usually shortened to OMP, is an agentic coding command-line application. You give it a task; its agent can work through model responses and tools that inspect or change a project.
A session records the conversation and associated session information. It is not a backup of the workspace. Reopening a conversation that discussed an earlier file does not restore that file. Forking a conversation does not create a separate Git worktree. Clearing the conversation does not erase retained history or previously generated exports.
This workbook follows three fictional stories:
| Story | Fictional reader | Practical outcome |
|---|---|---|
| Return Desk | Maya maintains Lantern Board across several sittings. | Find the intended history, reopen it deliberately, and distinguish resuming from relocating a session. |
| Decision Desk | Eli wants to explore another direction for Lantern Board. | Fork the conversation, then choose correctly between fresh, clear, and new. |
| Review Packet | Noor reviews the invented Harbor Notes project. | Inspect a local packet, including older and nested history, before making any disclosure decision. |
The recorded Decision Desk tests use a separate fictional Cedar Library fixture. Those tests support the operation boundaries; they are not a recording of Maya or Eli using the public Lantern Board recipe.
What you need
You need basic prompting, terminal use, and filesystem paths—not extension or RPC programming.
For the public exercises:
- A downloaded, disposable copy of the complete examples bundle.
- A terminal shell.
jqfor the JSON inspection and receipt commands.- Bun for the supplied Return Desk lab helper.
shasumfor the optional byte-comparison checks.- An already installed
ompexecutable and an interactive terminal for native session exercises.
The receipt-capture commands reproduce the supplied macOS-style mktemp -t recipes. Their exact shell behavior is not presented as a Windows or cross-platform installation recipe.
Run commands described as “from examples/” in the extracted directory containing return-desk/, decision-desk/, and review-packet/.
No installation, login, provider prompt, live sharing, or destructive session exercise is required. If a clean lab profile stops at model or authentication setup, stop there. Do not supply credentials to force the exercise onward.
Three kinds of evidence
Throughout the book:
- Source-backed expectation means the supplied implementation defines that behavior.
- Recorded check means a completed supplied report observed it under its stated test conditions.
- Your observation means something you actually inspected in your own disposable lab.
These are not interchangeable. Printing a command is not executing it. A component test is not a physical terminal test. A local fake provider handle is not a real provider incident.
Some downloadable files retain preparation-time verification labels. The completed reports summarized in Evidence and limitations supersede those older labels for the named checks—not for every possible environment or reader action.
Begin with the continuity ledger, then follow the three desks. Keep the operation decision matrix and recovery and disclosure checklists nearby.
Sessions, resets, and reviewable history · Source chapter: continuity/start-here. Original evidence remains scoped to its recorded snapshot.