Repository navigation
feat(scient-agent): drive Scient Agent 1.x, built on Oh My Pi 19 - #1034
Merged
Merged
Conversation
Scient Agent has been aligned with Oh My Pi 19.0.1. Every shipped Desktop refuses that build: the Scient Agent target required the stock Oh My Pi provider's supported major, 18, for the agent's upstream release. Scient Agent is qualified release by release, so its upstream range is now its own: Oh My Pi 18.2.8 or newer on major 18 or 19. The 19-based agent ships as Scient Agent 1.0.0, a new product major, because Desktops that cannot run it must never install it: their managed-runtime policy stops below 1.0.0 and their target accepts only 0.x. This Desktop accepts 0.x and 1.x and installs below 2.0.0. The stock Oh My Pi provider stays on 18. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A resume cursor records the Oh My Pi release that wrote it, and a cursor from another major was refused: after updating to Scient Agent 1.x, built on Oh My Pi 19, every thread last run on 0.x would start a fresh native session from a recovery summary. Oh My Pi 19 resumes and continues an 18 session (Scient Agent's capability check runs a 0.1.13 session on the new build), so Scient Agent's target lists 18 then 19 as majors that resume forward. A cursor still never resumes on an older major, and stock Oh My Pi keeps the same-major rule. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Installed Scient releases read the model manifest's compatibility policies from main, so its Scient Agent entry keeps the 0.x range for releases up to 0.6.31, which cannot run 1.x, and a new entry from 0.6.32 on supports Scient Agent below 2.0.0. Without it the release that drives 1.0.0 would show it as an unsupported version. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
yaacovcorcos
enabled auto-merge
November 20, 2026 01:14
Contributor
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Other scenariosAll 64 scenario measurements match All 64 scenario measurements
Baseline: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
4 of 5 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What Changed
Scient Desktop drives Scient Agent 1.x, the agent aligned with Oh My Pi 19.0.1 (ScientFactory/scient-agent#77). Three commits:
isSupportedOmpRuntimeVersionis no longer exported, since onlyOmpTargetuses it.OmpTarget.resumableUpstreamMajors), never the reverse. Stock Oh My Pi keeps the same-major rule.<1.0.0; from 0.6.32 it supports>=0.1.0 <2.0.0.updatedAtmoves forward so a cached manifest from 0.6.31 does not shadow the new bundle.Why
Every shipped Desktop refuses a Scient Agent built on Oh My Pi 19: its target required the stock provider's supported major, 18, for the agent's upstream release. Desktop's live suites against the 19.0.1 candidate failed every session open with "This is not a Scient Agent release this version of Scient supports".
The 19-based agent is released as Scient Agent 1.0.0, so Desktops that cannot run it never install it: their managed-runtime ceiling stops below 1.0.0, and their target accepts only 0.x. They keep 0.1.13. This was weighed against bumping the catalog contract revision (a Codex debate): the revision bump would have left a fresh install of this Desktop without an installable agent until the new agent was promoted. The agent's release check now refuses any other version for this build (scient-agent#77).
Without the resume change, every thread last run on 0.1.13 would start a fresh native session from a recovery summary after the update. Oh My Pi 19 reads an 18 session: Scient Agent's capability check resumes and continues a session written by 0.1.13 on the 19.0.1 build.
Without the manifest change, installed releases (which read the manifest from
main) would mark a working 1.0.0 as unsupported, or this release would.Release order: this merges and ships in a Scient release before Scient Agent 1.0.0 is released and promoted in the managed-runtime catalog. If a Scient release other than 0.6.32 is cut from
mainfirst without this change, the manifest's0.6.32bound moves to that release's successor.Known limit, unchanged by any gate: once the catalog promotes 1.0.0, a fresh install of a Scient release from before this change, with no installed or cached Scient Agent, has no agent to install until it updates itself.
Documentation Impact
Documentation impact: Updated —
docs/internals/providers.md(the identity range and resume across majors).Platforms
Verification
apps/server:src/provider/scient,src/provider/omp,src/scient/providerLifecycle: 857 passed.packages/scient-provider-runtime: 403 passed.scripts/lib/managed-runtime-catalog.test.ts: 75 passed.providerCompatibility.test.tsandModelManifest*: 38 passed.pnpm run typecheck,pnpm run knip:check,vp lint,vp fmt --check,git diff --check,scripts/scient-seam-check.mjs,scripts/verify-upstream-provenance.mjs: pass.OMP_QUALIFY_TARGET=scient, 12 files) on this head: the 19.0.1 candidate and v0.1.13 fail the same 13 of 34 cases and no other (this machine's Ollama lacks the custom-model fixture's model, no stockompruns beside it, and the Scient extension fixture's tool does not load for either). Onmainthe candidate failed 25, every session refused.pnpm run build, desktop smoke; CI runs them.Review
Review: Codex high and a live test — 3 findings on the first head: 2 fixed (resume across majors, the manifest's banner), 1 rejected (a fresh install of an old release after promotion: any gate has it, and the app updates itself); recheck found the manifest's
updatedAtleft unchanged, fixed; recheck otherwise clean.Checklist
Model/harness: Claude Opus 5.5 (Claude Code), reviews by Codex gpt-6.2-sol.
🤖 Generated with Claude Code