You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Let the self-hosted Pro workbench use a locally installed Oh My Pi (OMP) harness as its agent driver, including OMP-managed authentication and model selection (for example, Codex OAuth with gpt-5.6-terra at high reasoning).
Proposed first slice
Add an opt-in OMP RPC driver behind an explicit runtime setting. The default OpenMAIC Pi runtime stays unchanged.
Launch omp --mode rpc --no-session as a child process per OpenMAIC agent session.
Negotiate RPC protocol v2; use OMP's documented set_model and set_thinking_level commands only when the operator configures them.
Adapt OpenMAIC's existing course-building tools into OMP RPC host tools and translate terminal OMP events into the existing durable workbench event stream.
Validate configuration and process lifecycle with a fake JSONL OMP process in tests.
Boundaries
No new raw API-key provider and no bypass of OMP authentication/subscription rules.
No change to the existing Pi driver, default behavior, or public API routes.
No generic multi-harness abstraction in this first PR; the seam remains deliberately OMP-specific until a second harness proves the abstraction.
The feature remains disabled unless explicitly configured.
Would maintainers prefer this opt-in RPC integration, and if so should the first PR target only the Pro agent runtime or also classic one-click classroom generation?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Goal
Let the self-hosted Pro workbench use a locally installed Oh My Pi (OMP) harness as its agent driver, including OMP-managed authentication and model selection (for example, Codex OAuth with
gpt-5.6-terraathighreasoning).Proposed first slice
Add an opt-in OMP RPC driver behind an explicit runtime setting. The default OpenMAIC Pi runtime stays unchanged.
omp --mode rpc --no-sessionas a child process per OpenMAIC agent session.set_modelandset_thinking_levelcommands only when the operator configures them.Boundaries
OMP documents its process-isolated JSONL RPC mode, model selection, reasoning level, host-tool callbacks, and terminal agent events here: https://github.com/unsigned-gg/omp/blob/main/docs/rpc.md
Would maintainers prefer this opt-in RPC integration, and if so should the first PR target only the Pro agent runtime or also classic one-click classroom generation?
All reactions