Skip to content

Support for oh-my-pi (omp) as a harness with rec launch omp - #47

Open
daniel-sali wants to merge 3 commits into
recursive-oss:mainfrom
daniel-sali:main
Open

daniel-sali wants to merge 3 commits into
recursive-oss:mainfrom
daniel-sali:main

Conversation

@daniel-sali

Copy link
Copy Markdown

This PR adds the rec launch omp command, which starts an omp session with Flint pre-configured properly as the model to use, with correct message size and tool calling configurations.

@strin strin left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for adding omp. Isolated config/session handling, environment-based key delivery and a locked fallback install are useful. Seven targeted Go tests passed with the race detector; go vet ./... passed.

Before merge:

  1. The launcher prefers an arbitrary omp on PATH, while README says harnesses are separate from existing installs. Either always use the pinned install or document PATH preference and the supported-version policy accurately.
  2. Stub/string tests do not establish wire compatibility with the pinned package. Please add or record an isolated fake-server qualification of streamed tool calls, auth, context/max-token settings and a second-turn assistant replay using that version. No real model/customer prompts are needed.

I reviewed the lockfile but did not install/run the package; stub tests are not end-to-end harness validation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants