mirror of
https://github.com/paperclipai/paperclip.git
synced 2026-11-22 11:54:35 +01:00
## Thinking Path > - Paperclip is the open source app people use to manage AI agents for work. > - Paperclip Runner runs Claude and Codex agents from one shared provider pack. The pack pins an exact Claude Agent SDK (which bundles Claude Code) and an exact Codex CLI. > - #22222 added Claude Fable 5.2 (minimum Claude Code 2.1.321) and GPT-6.2 Sol and Astra (minimum Codex 0.169.1). The pack still bundles Claude Code 2.1.286 and Codex 0.160.0. > - Because of this, Paperclip Runner stops these models with a named version error, and native remote Codex accepts only `>=0.149.0 <0.161.0`. > - This pull request moves the provider pack to Agent SDK 0.3.328 (Claude Code 2.1.328) and Codex 0.170.0. It moves every constant that depends on these pins, and the remote Codex window to `<0.171.0`. > - The benefit is that Fable 5.2 and GPT-6.2 run on Paperclip Runner after a sandbox image with this pack is promoted. ## Linked Issues or Issue Description Refs #22222 (adds the models and the version floors; this pull request makes them runnable on Paperclip Runner). Refs #18488 (moves only the Codex pin to 0.166.0 and the window to `<0.167.0`; it is not updated since November 1 and has conflicts with `master`). Refs #18486 (GPT-6.1 Terra needs Codex 0.165.0; Codex 0.170.0 satisfies it). **Overlap with #18488.** #18488 changes the same Codex pin locations. This pull request uses a newer pin (0.170.0) and also moves the Claude runtime. If this pull request merges first, #18488 has no remaining change. I did not change the #18488 branch. ## What Changed - Claude runtime: `@anthropic-ai/claude-agent-sdk` 0.3.286 → 0.3.328 (Claude Code 2.1.286 → 2.1.328). This changes the root `pnpm.overrides`, `pnpm-workspace.yaml`, the ACPX `claude` profile, and the qualified Claude runtime in `installation-integrity.ts`, with new executable digests for Linux x64, Linux ARM64, macOS ARM64, and macOS x64. - Codex runtime: `@openai/codex` 0.160.0 → 0.170.0. This changes the runner dependency, the `codex-acp@1.6.2>@openai/codex` override, the `codex-acp` patch dependency line, the ACPX `codex` profile, and the qualified Linux x64 runtime with its new executable digest. - The ACP bridges do not change: `claude-agent-acp` 0.73.0 and the patched `codex-acp` 1.6.2. Their `commandDigest` values and profile versions do not change. - Generated declarations: `generated-profiles.ts` and `generated_acpx_profiles.rs` are regenerated with `generate:acpx-profiles`. - Remote native Codex window: `REMOTE_CODEX_MAXIMUM_VERSION_EXCLUSIVE` 0.161.0 → 0.171.0. The minimum stays at 0.149.0. Images with Codex 0.149.0 through 0.170.x are accepted. - Codex company observability: the qualified-version check moves to `codex-cli 0.170.0`. The `otel` configuration keys that Paperclip writes (`exporter`, `trace_exporter`, `metrics_exporter`) are present in the 0.170.0 configuration schema. The `OtelExporterKind`, `OtelHttpProtocol`, and `OtelTlsConfig` definitions are identical to 0.160.0. - Daytona runner image probes (`Dockerfile`, `Dockerfile.release`) expect `codex-cli 0.170.0` and `2.1.328 (Claude Code)`. The remote npm install spec in `server/src/adapters/registry.ts` is `@openai/codex@0.170.0`. - Tests: fixtures and assertions that mirror the pins use the new versions. The window tests accept 0.161.0 through 0.170.99 and reject 0.171.0. The ACPX gate tests now show that Fable 5.2 and GPT-6.2 are admitted. A new test mocks an older bundled runtime and keeps the named version-gap errors covered. The fallback test shows that GPT-6.2 stays on 0.170.0 and still falls back on 0.160.0. - Opt-in qualification scripts (`scripts/tests/native-cleanup-paginated-codex.mjs`, `native-provider-startup-codex.mjs`) require Codex 0.170.0. - Documentation: `docker/daytona-runner/README.md`, `doc/architecture/paperclip-runner-compatibility.md`, `doc/agent-observability.md`, `docs/deploy/environment-variables.md`, and the deferred item in `doc/adapter-model-audit-2026-11-18.md`. - `pnpm-lock.yaml` is not part of this pull request. The refresh bot regenerates it on `master`, as for the previous pin refreshes (#14942, #14993). ## Verification Sources, checked on 2026-11-19: - npm registry: `@openai/codex@0.170.0` (published 2026-11-18T03:45Z) and `@anthropic-ai/claude-agent-sdk@0.3.328` (published 2026-11-18T23:13Z, `claudeCodeVersion` 2.1.328). Both are the `latest` tags. - [Codex releases](https://github.com/openai/codex/releases) 0.161.0 through 0.170.0. The notes record no app-server protocol break. 0.169.0 keeps project configuration disabled for `codex exec` in untrusted directories; Paperclip's CLI path already uses `--skip-git-repo-check`, and the native path uses `app-server`. - [Claude Code changelog](https://github.com/anthropics/claude-code/blob/main/CHANGELOG.md) 2.1.287 through 2.1.328. See "Risks" for the headless changes that I reviewed. Digests and package shape: - I downloaded each platform archive with `npm pack`, which verifies registry integrity, and computed the SHA-256 of the executable. As a method check, the same command on the 0.3.286 Linux x64 archive gives the digest that is on `master` (`fe503f65…`). The Codex 0.160.0 archive also gives the `master` digest (`12eb3e81…`). - The extracted executables report `codex-cli 0.170.0` and `2.1.328 (Claude Code)`. - The Codex 0.170.0 Linux x64 archive no longer contains `codex-resources/zsh/bin/zsh`. Paperclip does not reference that path. - The Agent SDK 0.3.328 `optionalDependencies` have the same platform set as 0.3.286. The Codex 0.170.0 `optionalDependencies` use the same `npm:@openai/codex@<version>-<platform>` aliases. - Bridge link check: I installed `@agentclientprotocol/claude-agent-acp@0.73.0` with an override to Agent SDK 0.3.328 and imported its entry module. Node linked all of the named SDK imports, and the import completed. Real Codex qualification (no model turn, no credentials): - `PAPERCLIP_TEST_CODEX_BINARY=<installed 0.170.0 Linux x64 binary> node --import ./server/node_modules/tsx/dist/loader.mjs scripts/tests/native-cleanup-paginated-codex.mjs` passed: `green: true`, with the expected red control and paginated `thread/resume` through the real 0.170.0 `app-server`. The installed binary digest matches the pinned digest. Focused suites (Linux x64, Node 25.9.0, local `pnpm install --no-frozen-lockfile`): - `cd packages/paperclip-runner && pnpm run typecheck:typescript` passed, including `check:acpx-profiles`. - `npx tsc --noEmit` passed in `packages/adapters/codex-local` and `packages/adapters/claude-local`. - `packages/adapters/codex-local`: 625 passed. `packages/adapters/claude-local`: 419 passed, 1 skipped. - `node --test`: `acpx-codex-package-contract` 9 passed, `controlled-evals/controller` 77 passed, `scripts/acpx-patch-packaging` 26 passed, `scripts/__tests__/grok-public-install-sandbox` 27 passed. - `server`: `acpx-qualification`, `codex-runtime-compatibility`, and `codex-model-fallback` 110 passed. `native-session-executor` 1541 passed, 1 failed. The failure (`compares export process compatibility … db.transaction is not a function`) also fails on unchanged `master` on this host. - `packages/paperclip-runner` vitest (`installation-integrity`, `qualified-profiles`, `codex-security-config`, `native-execution`, `native-backend-factory`): 283 passed, 25 failed. All 25 failures are in `installation-integrity.test.ts` with "ACPX provider lifetime guardian failed to start". The same 25 tests fail on unchanged `master` on this host (master fails 30 here). Rust (toolchain 1.97.1 from `rust-toolchain.toml`, Linux x64): - `cargo test -p paperclip-runner-core --lib`: 658 passed, 2 failed, 4 ignored. `warm_run_attachment_reuses_the_provider_ingress_listener` also fails on unchanged `master` on this host. `reaping_stops_a_dead_runners_provider_and_its_escaped_tool_job` is flaky here: on this branch it passed 2 of 3 reruns. - `cargo test -p paperclip-runner-core --test acpx_warm_attachment --test native_provider_backend`: 7 and 45 passed. - The new and changed saved-session tests pass: `a_session_saved_by_the_previous_agent_runtime_is_refused_by_name`, `unrestorable_saved_sessions_keep_strict_bindings_and_name_their_class`, and `a_settled_session_saved_by_the_previous_acpx_release_continues`. `rustfmt --check` passes. - `server`: `native-session-resume.test.ts` and `acpx-qualification.test.ts` 110 passed, 2 skipped. Both new resume cases run and pass. Not run here: - `native-provider-startup-codex.mjs`, because it needs a compiled `paperclip-runnerd`. The trusted CI runner workflow covers startup and session-resume probes. - The Docker image build and any live model turn. A live Fable 5.2 and GPT-6.2 test follows the staging image rollout. ## Saved sessions from the previous release This change keeps the ACPX bridge command digests and profile versions. It changes `agentRuntimeVersion` in the `claude` and `codex` ACPX profiles. That field is part of the saved session identity. The previous release saved sessions with Agent SDK 0.3.286 or Codex 0.160.0. This build refuses those saved sessions. It does not migrate them. - **Next run (the usual case):** the saved provider descriptor names the old runtime. `rebindNativeSessionCheckpoint` does not match it, so the next run starts a fresh provider session in the same workspace with the complete handoff prompt. No run fails. The earlier provider conversation does not carry over. - **A run in flight at the deploy (settled or mid-turn):** the runner restore refuses the saved descriptor with the permanent class `provider_state_incompatible`. The server reports it as `native_provider_state_incompatible` and stops automatic retries. The runner opens no provider and keeps the saved state bytes and the workspace. The next run on the task starts a fresh provider session. - **Native Codex (`codex_app_server`) and OpenCode** sessions do not record this field, so their resume decision does not change. After a new image is promoted, native Codex resumes a saved thread with Codex 0.170.0 instead of 0.160.0. This pull request does not test that cross-version thread resume. New tests: - `acpx_provider_backend.rs`: `a_session_saved_by_the_previous_agent_runtime_is_refused_by_name` covers settled Claude and Codex sessions and a Claude turn interrupted mid-run by the deploy. `unrestorable_saved_sessions_keep_strict_bindings_and_name_their_class` has a new `agent_runtime_release` case. Each case checks the named class, that no provider session opens, and that the saved bytes do not change. - `native-session-resume.test.ts`: "a session saved by the previous Claude or Codex ACPX runtime" checks that a same-release session resumes, and that a session saved with Agent SDK 0.3.286 or Codex 0.160.0 starts fresh in the same workspace. ## Risks - Medium. Every Paperclip Runner Claude and Codex run uses the new executables. The digests, generated profiles, image probes, and window must agree. They agree locally, and CI runs the Rust and runner suites again. - Claude Code 2.1.287 through 2.1.328 change some headless defaults. I checked each one against Paperclip: - 2.1.302: `-p` and Agent SDK sessions with no permission mode start in `default` mode on third-party providers. Paperclip always sets a mode (`bypassPermissions` or `default`), so this does not apply. - 2.1.299: MCP allow rules now match only the whole server name. Paperclip already writes `mcp__<server>__*` and exact `mcp__paperclip__<tool>` rules. - 2.1.302: fork subagents are on by default in `-p` and the Agent SDK, as in the terminal. This pull request keeps the upstream default and does not set `CLAUDE_CODE_FORK_SUBAGENT=0`. Reviewers can ask to keep them off. - 2.1.299 and later: stdio MCP connections negotiate MCP protocol 2026-07-28 first and fall back to the older protocol for servers that do not answer. - Agent SDK 0.3.328 is less than one day old. If a regression appears, revert this pull request to return to 0.3.286 and Codex 0.160.0. - Sandbox images built before this change still carry Codex 0.160.0 and Claude Code 2.1.286. They stay accepted. On those images, Fable 5.2 and GPT-6.2 keep the existing named errors and fallbacks until a new image is promoted. - Until the refresh bot updates `pnpm-lock.yaml` on `master`, a local `--frozen-lockfile` install fails, as with the previous pin refreshes. > For core feature work, check [`ROADMAP.md`](ROADMAP.md) first and discuss it in `#dev` before opening the PR. Feature PRs that overlap with planned core work may need to be redirected — check the roadmap first. See `CONTRIBUTING.md`. ## Model Used - Anthropic Claude, model ID `claude-opus-5-5`, through Claude Code with tool use (shell, file edit, `gh`) and code execution. The context window and reasoning mode are not reported in this session. - The registry archives, digests, release notes, configuration schemas, and changelog were read directly. No model output was used as a source for those facts. ## Checklist - [x] I have included a thinking path that traces from project context to this change - [x] I have specified the model used (with version and capability details) - [x] I have checked ROADMAP.md and confirmed this PR does not duplicate planned core work - [x] I have searched GitHub for duplicate or related PRs and linked them above - [x] I have either (a) linked existing issues with `Fixes: #` / `Closes #` / `Refs #` OR (b) described the issue in-PR following the relevant issue template - [x] I have not referenced internal/instance-local Paperclip issues or links (only public GitHub `#NNN` / `github.com/paperclipai/paperclip` URLs) - [x] My branch name describes the change (e.g. `docs/...`, `fix/...`) and contains no internal Paperclip ticket id or instance-derived details - [ ] I have run tests locally and they pass - [x] I have added or updated tests where applicable - [x] I have updated relevant documentation to reflect my changes - [x] I have considered and documented any risks above - [ ] All Paperclip CI gates are green - [ ] Greptile is 5/5 with no open P2s, recommendations, or follow-ups - [x] I will address all Greptile and reviewer comments before requesting merge 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: devinfoley <139239+devinfoley@users.noreply.github.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
198 lines
11 KiB
Markdown
198 lines
11 KiB
Markdown
# Paperclip Daytona runner image
|
||
|
||
Ordinary provider packs now include pinned Cursor assets for Linux x64; no
|
||
`--candidate-providers=cursor` flag is needed. Cursor admission is enabled after
|
||
the [production readiness gates](../../doc/plans/2026-10-03-cursor-production-readiness.md)
|
||
passed. The public CLI installation command is `paperclipai runtime setup cursor`;
|
||
it runs explicitly on the execution host and is never an npm installation hook.
|
||
|
||
This image is the Paperclip Cloud fleet sandbox image plus a source-built
|
||
`paperclip-runnerd` and immutable provider pack. The pack contains Node 24.11,
|
||
OpenCode 1.18.34, the compiled OpenCode proxy, ACPX 0.22.0 sidecar, qualified ACP
|
||
agents, and the production lockfile. Its manifest digests each executable bridge
|
||
and records the runner source revision as provenance. Its interface declaration
|
||
allows compatible app releases to reuse it without uploading or installing a pack.
|
||
|
||
The fleet pins are intentionally copied from
|
||
[`paperclip-cloud/fleet-sandbox-image/Dockerfile`](https://github.com/paperclipai/paperclip-cloud/blob/master/fleet-sandbox-image/Dockerfile).
|
||
Update both definitions together until the fleet base is published as a stable
|
||
image that this Dockerfile can extend directly.
|
||
|
||
## Harness versions
|
||
|
||
The November 19, 2026 refresh pins Codex 0.170.0 and Claude Agent SDK
|
||
0.3.328 (Claude Code 2.1.328) in the shared provider pack; OpenCode stays at
|
||
1.18.34. Claude Code 2.1.280 is the minimum for
|
||
[Opus 5.5](https://code.claude.com/docs/en/model-config), 2.1.284 for Sonnet 5.5,
|
||
and 2.1.321 for Fable 5.2, so the pinned runtime supports all three and Fable 5.1.
|
||
Codex 0.170.0 ships bundled metadata for
|
||
[GPT-6.2 Sol and Astra](https://learn.chatgpt.com/docs/models) (minimum 0.169.1)
|
||
as well as GPT-6.1 Sol, GPT-6 Sol, and GPT-6 Luna.
|
||
The sandbox layer pins Grok CLI 1.0.89, Gemini CLI 0.68.0, Kimi Code 2.3.3,
|
||
Cursor CLI 2026.11.17-f532c45, and GitHub CLI 2.105.0 (November 2026
|
||
refresh). The native Cursor provider uses its separately verified distribution,
|
||
pinned to 2026.09.26-dd393fe; it does not use the sandbox layer’s global Cursor
|
||
executable. Grok CLI 1.0.89 supports the current
|
||
[Grok 4.7](https://docs.x.ai/developers/grok-4-7) model family. Hermes stays
|
||
at 0.19.0, the newest release on PyPI.
|
||
|
||
Keep the patched ACP bridge versions separate from their CLI runtime pins.
|
||
Their executable digests do not change when only the runtime dependency
|
||
changes. Refresh the runtime executable digests from integrity-verified npm
|
||
release archives for every supported platform, and keep the native runner,
|
||
provider manifest, and remote controller version checks aligned.
|
||
|
||
## Build and verify
|
||
|
||
Run `pnpm --filter @paperclipai/paperclip-runner test:opencode:qualification`
|
||
after installing dependencies to exercise the actual pinned OpenCode executable.
|
||
It checks health/version, session creation and retrieval, SSE messages, an async
|
||
prompt, and session deletion against a loopback mock provider. It uses an
|
||
isolated home, starts no paid model request, and retires its process group.
|
||
Set `PAPERCLIP_TEST_OPENCODE_BINARY` to the materialized Linux executable when
|
||
qualifying an assembled provider pack.
|
||
|
||
|
||
The fleet image is currently amd64-only because the pinned Cursor and GitHub CLI
|
||
checksums cover amd64.
|
||
|
||
```bash
|
||
content_id="$(pnpm --silent test:e2e:runner:image-id)"
|
||
docker buildx build \
|
||
--platform linux/amd64 \
|
||
--build-arg PAPERCLIP_RUNNER_CONTENT_ID="${content_id}" \
|
||
--build-arg PAPERCLIP_RUNNER_SOURCE_REVISION="$(git rev-parse HEAD)" \
|
||
--build-arg PAPERCLIP_RUNNER_LOCK_SHA256="$(shasum -a 256 pnpm-lock.yaml | cut -d ' ' -f 1)" \
|
||
--tag "paperclip-daytona-runner:e2e-content-${content_id}" \
|
||
--load \
|
||
--file docker/daytona-runner/Dockerfile \
|
||
.
|
||
|
||
docker run --rm --platform linux/amd64 \
|
||
--entrypoint paperclip-runnerd \
|
||
"paperclip-daytona-runner:e2e-content-${content_id}" \
|
||
--build-metadata
|
||
```
|
||
|
||
The metadata must advertise `dial_ws_loopback`, `dial_wss`, and `listen_ws`.
|
||
The explicit entrypoint is needed only for this local probe because Daytona's
|
||
base image uses its own long-running sandbox entrypoint.
|
||
|
||
`test:e2e:runner:image-id` hashes the audited Docker build dependency closure,
|
||
target platform, the immutable Dockerfile syntax-frontend digest, and every
|
||
immutable `FROM` reference. It fails before the paid workflow can build when
|
||
the frontend or a base is not pinned to a sha256 digest. When updating the
|
||
syntax version, resolve and review its registry digest and update both values in
|
||
the first Dockerfile line. Git commits that do not change those inputs reuse the
|
||
same content tag.
|
||
|
||
`PAPERCLIP_RUNNER_SOURCE_REVISION` remains the full Git SHA that built the first
|
||
published copy and is retained as provenance rather than cache identity.
|
||
|
||
## Use in Paperclip
|
||
|
||
Publish the image to a registry Daytona can pull, or use the environment
|
||
editor's **Configure image** flow to produce a Daytona snapshot. Set the
|
||
environment image to that immutable tag or snapshot. Paperclip probes the
|
||
sandbox user's `PATH` for `paperclip-runnerd` and `codex` and checks
|
||
`/opt/paperclip-runner/provider-pack` for OpenCode and ACPX. It uses the pack
|
||
when its selected provider interface and platform are compatible. App source
|
||
revisions and unrelated provider pins do not force an update. Startup reads the
|
||
small manifest in the existing runner metadata query. It does not scan the pack,
|
||
run a version command, or transfer files on this path. Otherwise it stages the pack configured by
|
||
`PAPERCLIP_RUNNER_REMOTE_PROVIDER_PACK_PATH`. Remote OpenCode and ACPX never
|
||
fall back to host-local processes.
|
||
|
||
`src/live/provider-pack-contract.json` in the Runner package declares the
|
||
OpenCode and ACPX interface revisions. Change a revision only for an incompatible
|
||
runner/pack boundary change, and qualify the new pack before publishing it.
|
||
Bumping a revision also retires every older image pack.
|
||
The pack build also records a `contractDigest`, computed by
|
||
`scripts/contracts/contract-fingerprints.mjs` from the JSON contracts under
|
||
`protocol/` and `generated/`, from Rust serde shapes, payload keys, match
|
||
literals and env keys, and from the Runner's ACPX patch, rather than from
|
||
source bytes. An image pack is reused
|
||
only when its digest equals the controller's bundled pack; comments and
|
||
refactors leave it unchanged, so a mismatch means a contract changed and the
|
||
controller uploads its bundled pack. Packs without a digest are not reused.
|
||
Define a new runner/pack contract in a schema under `protocol/` and generate the
|
||
TypeScript from it, as the sidecar's `session.open` parameter allowlist is
|
||
generated from `acpx-sidecar.schema.json`; TypeScript-only definitions are not
|
||
part of the digest.
|
||
Dependency versions and Git SHAs remain build provenance. ACPX retains its
|
||
selected agent's qualified profile checks.
|
||
|
||
The image build makes the pack root-owned and non-writable to the execution user. Fast admission
|
||
requires protected ancestors and manifest, with no writable path alias. Task-owned
|
||
packs and older packs without an interface declaration keep full content
|
||
verification. An attached session retains the exact pack and daemon identity
|
||
admitted at launch. Publish one new image with the interface declaration to enable
|
||
reuse across later compatible app releases.
|
||
|
||
Do not promote `paperclip-runner-e2e-20260826-v2` for OpenCode or ACPX. Build a
|
||
new immutable image or snapshot from a clean committed revision and pass that
|
||
full Git SHA as `PAPERCLIP_RUNNER_SOURCE_REVISION`.
|
||
|
||
Do not bake provider credentials, Paperclip bootstrap tickets, or Daytona
|
||
preview tokens into this image. They remain per-run secret material.
|
||
|
||
The provider-pack build pins the official Linux x64 Node 24.21.0 image by
|
||
manifest digest. Its bundled Undici is 7.29.1, which fixes
|
||
[GHSA-3wwx-pv8p-q78v](https://github.com/advisories/GHSA-3wwx-pv8p-q78v).
|
||
Pi separately verifies its private Node executable and nested npm dependency;
|
||
changing the outer interpreter does not replace either provider-owned pin.
|
||
|
||
Provider CLI updates are manifest-only changes: repository CI owns the root
|
||
lockfile. Resolve the complete workspace manifest graph in the build context
|
||
before invoking Docker, matching CI when a source commit precedes the lockfile
|
||
bot. The trusted workflow supplies this resolved lockfile as an immutable artifact.
|
||
The complete resolved lockfile must match `PAPERCLIP_RUNNER_LOCK_SHA256` before
|
||
package installation or lifecycle execution. Review and refresh that digest
|
||
with source dependency changes; registry-time resolution drift fails closed.
|
||
The Product E2E workflow resolves one lockfile before the image build. It
|
||
verifies the downloaded artifact, then passes that artifact's SHA-256 as the
|
||
`PAPERCLIP_RUNNER_LOCK_SHA256` build argument. The Dockerfile checks the resolved
|
||
lock against this value before installation. The Dockerfile has no default
|
||
digest: standalone builds pass the SHA-256 of the lockfile in their build
|
||
context, and a missing or malformed value fails before installation instead of
|
||
surfacing as a checksum mismatch. When a source change needs a fresh lockfile,
|
||
resolve it from the clean tracked lockfile using the exact
|
||
`pnpm install --resolution-only --ignore-scripts --no-frozen-lockfile` command,
|
||
and verify a second resolution preserves the digest. A lockfile left by a
|
||
filtered or incremental install can retain stale importer patch identities.
|
||
Refresh exact runtime versions and qualification digests together; do not
|
||
download dependencies when a task starts.
|
||
|
||
## Candidate ACP qualification assets
|
||
|
||
Provider branches can build their pinned assets with
|
||
`node packages/paperclip-runner/scripts/build-provider-pack.mjs /absolute/pack --candidate-providers=cursor`
|
||
(or `copilot` or `pi`). The source revision must include the named provider's
|
||
builder. Assets are installed at build time under `provider-assets/<provider>/<platform>-<architecture>`.
|
||
The pack manifest binds each complete asset tree. Runtime admission separately
|
||
checks the provider's source-owned closure pins and copies a verified launch snapshot.
|
||
A pack with candidate assets does not qualify or enable that provider.
|
||
|
||
For an isolated Linux x64 Daytona qualification image, pass
|
||
`--build-arg PAPERCLIP_RUNNER_CANDIDATE_PROVIDERS=cursor` with the normal build arguments.
|
||
Compute its content ID with the same selection:
|
||
`pnpm --silent test:e2e:runner:image-id --candidate-providers=cursor`.
|
||
Candidate assets and the default pack have distinct image identities. Never reuse
|
||
the default image's content ID for a candidate build.
|
||
Use each provider branch's recorded version and explicit model. Keep credentials
|
||
out of images. Paid qualification requires bound provider and Daytona credentials,
|
||
inspectable spend, and the shared $100 ceiling recorded in the capability report.
|
||
|
||
The pack builder tests its copied Node interpreter after relocation. Use a
|
||
standalone Node distribution if the host interpreter depends on a package manager's
|
||
private shared libraries. Pi additionally pins its complete portable interpreter
|
||
and npm dependency graph.
|
||
Refresh exact runtime versions and qualification digests together; never download
|
||
dependencies when a task starts. Grok's additive native ACP profile keeps its
|
||
qualified 1.0.13 executable at the verified sandbox prerequisite path. It does not replace the
|
||
legacy adapter's `grok` command on PATH.
|
||
|
||
Native Grok is an image prerequisite at `/opt/paperclip/providers/grok/1.0.13/grok`.
|
||
Its checksum-verified provisioning is separate from the provider pack, which ships
|
||
only the built-in launcher. Public npm installation never downloads this binary.
|