@oas-framework/pi

OAS pi runtime bridge — memory session events and pre-workspace bootstrap over the runtime-neutral @oas-framework/oas kernel

Packages

Package details

extension

Install @oas-framework/pi from npm and Pi will load the resources declared by the package manifest.

npm repo home report

$ pi install npm:@oas-framework/pi

Package: @oas-framework/pi
Version: 0.16.2
Published: Jul 21, 2026
Downloads: 2,837/mo · 2,024/wk
Author: pepe-reyero
License: MIT
Types: extension
Size: 7 KB
Dependencies: 0 dependencies · 3 peers

Pi manifest JSON

{
  "extensions": [
    "./extension/index.ts"
  ]
}

Security note

Pi packages can execute code and influence agent behavior. Review the source before installing third-party packages.

README

@oas-framework/pi

Pi runtime bridge for OAS.

The runtime-neutral kernel and universal oas CLI live in @oas-framework/oas. This bridge registers no operational tools. It only:

exposes oas-getting-started before an OAS workspace exists (the acquisition funnel);
contributes the instance-local .agents/skills set inside a spawned instance;
journals compaction summaries and sends resume nudges when the active knowledge capability created STATE.md/log.md — the OKF session protocol enforced at runtime.

Skill resolution itself is owned by the kernel: spawn materializes the exact kernel + soul + active-capability set into each instance's .agents/skills and launches pi with that directory as an explicit skill path. Ambient skills (user-level, packages, work tree) coexist with the OAS-composed set.

npm install -g @oas-framework/oas
pi install npm:@oas-framework/pi

OAS publishes both packages from the same version tag. Reload pi after an adapter install or upgrade.

All lifecycle/config/package operations use the shell-visible CLI: oas status, oas spawn, oas doctor, oas install, oas trust, oas use, and oas retire.