Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Introduction

omp-spt is the native Oh My Pi adapter for Spacetime (spt-core). It gives named Spacetime endpoints a real OMP terminal session rather than translating OMP through another interface.

The adapter supports the two hostable agent roles that belong in an interactive OMP session:

  • ReadyAgent stays reachable for direct messages in its native OMP TUI.
  • LiveAgent uses the same native endpoint and also activates the live-agent Psyche lifecycle.

There is no plugin installation step. Install OMP and spt-core, then install the BigscreenVR/omp-spt adapter release.

Mental model

Three components share the work:

spt-core endpoint lifecycle
        |
        | launch, resume, attach
        v
native OMP process
        |-- owns the broker PTY and attachable TUI
        `-- loads adapter/strings/omp-spt.mjs
                    |
                    `-- bind, delivery, activity state, replies, shutdown
  • spt-core owns endpoint records, messaging, lifecycle coordination, subnet reachability, adapter installation, and updates.
  • Native OMP owns the hosted process, interactive terminal, model turn, tools, and transcript.
  • omp-spt supplies the launch and transcript helpers plus the packaged OMP extension that connects native OMP events to spt-core.

The release artifact is one fat adapter.spt archive. It contains the supported adapter binaries, the manifest, and the shared adapter/strings/omp-spt.mjs extension, so installation and updates move as one unit.

What the extension does

When OMP starts a hosted session, the extension binds the OMP session id to the named Spacetime endpoint and starts message delivery. Incoming messages are queued into OMP turns. OMP’s assistant response is sent back to the original sender, and the endpoint moves between busy and idle as the turn runs. When the TUI shuts down, the extension ends the bound session and releases its listener.

The result is still normal OMP. You attach to OMP’s own TUI, and OMP remains in direct control of the broker PTY.

Start with the Quickstart. For event-by-event behavior, read the Native integration contract.