mirror of
https://github.com/paperclipai/paperclip.git
synced 2026-10-21 16:27:18 +02:00
## Thinking Path > - Paperclip must run the selected agent on its selected host. > - Claude needs verified packages for each supported target. > - A Mac controller must select the correct Linux provider pack. > - New defaults must follow package and execution evidence. > - This PR adds Claude platform packaging and target-specific pack selection. > - Existing Codex Linux ARM64 behavior remains intact. ## Linked Issues or Issue Description Refs #15683. This PR depends on #15993 and #15994. Related scope: #15422 and #15224. ## What Changed - Reuse the merged four-target daemon producer/consumer matrix. Add target-owned Linux provider packs and carry their immutable identities through release assembly and vendoring. - Reuse master’s landed pinned Claude SDK ARM64 executable admission and retain package-integrity, architecture and no-follow admission. - Select target-specific remote packs so Mac controllers can use Linux hosts without a development pack override. - Preserve read-only runtime context on SSH startup and resume without accepting unverified old content. - Check ordinary installed Claude readiness without injected package authority. Retain Codex and Linux x64 consumer checks. - Extend Claude automatic target selection for the remaining qualified package targets. Retain unsupported-platform and external-override behavior. - Qualify managed Daytona snapshot names through provider IDs during Claude Connect. Pin native acquisition to the measured ID. Preserve a revocation marker after failed probes or target edits, and block native acquisition until requalification instead of falling back to a mutable name. Preserve immutable-image proof, company and account boundaries, and Legacy acquisition. ## Verification - Reconciled with master `9179d8dcc3e908c217fde4f63c9d08ccf8132eeb` through the prerequisite stack, retaining the merged startup fix and latest Codex Linux ARM64 behavior. - [Four-target exact-source package qualification](https://github.com/paperclipai/paperclip/actions/runs/39267321383) passed on source `04e0202ca81387b17cbe7fd094a8338648356fe9`: all four native builds, public-package assembly, Linux x64 verification and clean installed consumers on Apple Silicon, Intel Mac and Linux ARM64. The later master reconciliation adds shared OpenRouter attribution and changes runtime source. This historical result keeps its original source identity; [later qualification](https://github.com/paperclipai/paperclip/actions/runs/39281100929) passed at `dca62c7aeb4b45f0dd91a8e18d386a16a2658ef8`. It predates the subsequent TypeScript startup fix. - Fresh local product acceptance on integrated source `b2c9fe43f9cd3bc5dd9d22552da0148845ba71a4` completed a useful file and follow-up through native Claude/Opus 5.5, High effort and the API-key connection. Both actual browser downloads were independently checked; the revision preserves the original body and session continuity. Total task estimates: $0.518432800. Ordinary web and API creation saved defaults with the native experiment disabled. - Local focused verification passed 993 startup/session tests, 243 UI tests, 12 workflow security tests, direct server/UI TypeScript checks, and token/palette gates before the last review changes. Initial DB-backed snapshot pin/revocation coverage passed 18 cases; the final serial route suites pass 122 credential/permission and 232 snapshot/environment cases after correcting a test hook timeout. Current-head cloud suites pass. - Preserved the failed pre-provider local fixture and its full pending reservation. The successful fixture has no unpriced or pending usage. Historical failed Cloud journeys, accounting holds, source identities and subscription limitations remain in the dated plan. - All Docker/Rust release production was performed in cloud CI. No local Docker image was built. An inadvertently invoked local Rust prerequisite was stopped. - Current-head cloud CI is green. All three stack PRs have fresh Greptile 5/5 reviews and zero unresolved review threads. Required typecheck, test and build gates ran in cloud CI; Docker work stayed remote. Earlier failed checks remain in their original runs. - The final master merge preserves task-loading, permission, skill-retention and OpenRouter changes. Pi uses a fresh combined profile 27, preserving both historical profile-24 declarations; Copilot remains profile 22. Focused protocol checks passed 155 cases (one skipped), the updated Pi attestation check passed 18 (one skipped), and 91 evaluation/catalog checks passed. - Latest-application manual continuation passed in 37.942 seconds on `695e5c005a85bddc8711d3fcddcaf6b7e1fb64d0`, with High effort, native Opus 5.5, Anthropic API attribution, the same resumed Claude session, an independently checked 635-byte file and persisted Done status. It uses the earlier verified Mac daemon; the preceding-source package qualification passed at `dca62c7aeb4b45f0dd91a8e18d386a16a2658ef8`. That package run predates the small TypeScript startup fix and is not relabeled as qualification for it. - Upgrade limitation: changed compiled sidecar identity rejected old durable launch state and recovery hit session-open bounds before eventually resuming. That attempt was operator-cancelled and retained; the successful manual continuation does not qualify seamless upgrades. - Local latency profile, Opus 5.5/High unchanged: three alternating real-ACP loopback samples per variant reduce median provider-ready time from 5.081s to 4.034s. The matched real API task startup improves from 5.533s to 4.348s, but total reply time changes from 17.933s to 20.221s because agent work varies. This establishes a startup saving of about one second, not a consistent total-reply speedup. A real candidate follow-up passed in 20.146s and resumed the same saved session. The loopback fixture makes no external model requests; failed initial probes remain retained. - The startup change passes 107 focused runtime/effort/lease tests, 53 profile checks (one skipped), TypeScript checking and the TypeScript-only runtime build. Native hire fixture checks pass 70 tests; their first local run retained a socket-hangup failure and stale OpenCode expectation, both accounted for before the passing rerun. Broader required checks run in cloud CI. ## Risks - **Experience needs improvement:** successful connection setup still shows “Connection needs attention” because runtime checks are deferred. Cold provider-pack upload took 122–126 seconds per run while the task mainly showed “Thinking.” The tested Core-only preview excludes private Cloud UI plugins; this is not full Cloud distribution or subscription qualification. Desktop dark theme was tested; mobile and comprehensive accessibility were not. The portable report validates, but gallery interaction could not be inspected because host preview was queued. - The optional supply-chain scan returned neutral/inconclusive because GitHub Actions package coverage and infrastructure parsing are unavailable. It is not counted as a successful supply-chain qualification. Exact package, daemon and image integrity checks passed. - A stale, missing or wrong-architecture pack must fail admission. It must not change runner or target silently. - Provider-pack source changes invalidate affected earlier execution results. Existing unknown-cost and cleanup holds remain intact. - Live subscription execution remains unverified under the API-key qualification direction. Built-in authentication flows are retained. ARM64 cloud-image production is deferred. Merge and production deployment remain separate. ## Model Used OpenAI Codex, GPT-6 family, with reasoning, repository tools, code execution and browser testing. The exact serving model ID and context-window size are not exposed in this session. ## 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 - [ ] Focused local tests and final cloud verification 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 - [x] All Paperclip CI gates are green - [x] Greptile is 5/5 with no open P2s, recommendations, or follow-ups - [x] I will address all Greptile and reviewer comments before requesting merge --------- Co-authored-by: Paperclip <noreply@paperclip.ing>
180 lines
7.8 KiB
Markdown
180 lines
7.8 KiB
Markdown
# Local, SSH, and sandbox environments — agent access
|
|
|
|
Product map: [Local, SSH, and sandbox
|
|
environments](../feature-map/execution-environments.md).
|
|
|
|
Review date: 2026-10-12. Source commit: `f981fa3cc10cb8663a87dec60345fbff46d54d0a`.
|
|
|
|
This is a source-reviewed baseline of representative operations and known gaps.
|
|
Each capability needs operation-level review before its entire scope can be
|
|
qualified. No live agent execution is claimed. Follow the [map contract](../README.md)
|
|
for format, permission checks, evidence and maintenance.
|
|
|
|
Scoped immutable-platform source review: 2026-10-12 at
|
|
`d16eccf109b524778ceb896f79ccb3881bc61a9b`, limited to saved sandbox probing,
|
|
server-owned qualification metadata and read/invalidation behavior. The original
|
|
baseline commit and review depth remain for unrelated operations; no live agent
|
|
or provider qualification is claimed by this update.
|
|
|
|
## `configuration`
|
|
|
|
Review: `baseline`.
|
|
|
|
API: `present` — representative operation IDs:
|
|
|
|
- `GET /api/companies/{companyId}/environments`.
|
|
- `POST /api/companies/{companyId}/environments`.
|
|
|
|
Agent access: `restricted` — Board read/admin management REST / CLI environment.
|
|
|
|
Policy: Environment management is instance administrator/board; permitted assignment
|
|
uses agent/project policy.
|
|
|
|
Evidence: `source-only` — [implementation](../../server/src/routes/environments.ts#L353)
|
|
at the reviewed commit above.
|
|
|
|
Verification: `not-run` — assert the documented agent denial with an owned test fixture;
|
|
verify any listed agent request/result path separately. A delegated operation needs its
|
|
own policy and access review.
|
|
|
|
Gaps: API exists; an agent cannot use instance environment management as an ordinary
|
|
company actor.
|
|
|
|
Scoped source review: [environment routes](../../server/src/routes/environments.ts)
|
|
require board organization access for reads and local-implicit board or instance
|
|
administrator for management. Create/PATCH reject client-supplied platform-proof
|
|
metadata; [service updates](../../server/src/services/environments.ts) discard
|
|
supplied proof, preserve current server proof atomically for metadata-only edits,
|
|
and invalidate it when the target configuration or driver changes. Public row
|
|
responses hide the private record. This is source-only at the scoped commit.
|
|
Verify forged metadata rejection, concurrent probe/update preservation, target
|
|
invalidation and restricted-reader redaction; actual agent-denial proof remains
|
|
not run. Company/team packages do not import or export environment rows, so those
|
|
packages do not transfer platform qualification.
|
|
|
|
## `capabilities`
|
|
|
|
Review: `baseline`.
|
|
|
|
API: `present` — representative operation IDs:
|
|
|
|
- `GET /api/companies/{companyId}/environments/capabilities`.
|
|
|
|
Agent access: `partial` — Board environment capabilities endpoint; native run gets
|
|
server-selected runtime context.
|
|
|
|
Policy: Environment management is instance administrator/board; permitted assignment
|
|
uses agent/project policy.
|
|
|
|
Evidence: `source-only` — [implementation](../../server/src/routes/environments.ts#L353)
|
|
at the reviewed commit above.
|
|
|
|
Verification: `not-run` — exercise a listed permitted operation with actual agent
|
|
credentials/run context; inspect its result and applicable persistence/attribution.
|
|
Assert the relevant denied actor, owner, company or mode from Policy. Review the
|
|
remaining operations before qualifying the whole capability.
|
|
|
|
Gaps: Endpoint discovery and already-bound run capabilities differ; decide whether a
|
|
safe agent-readable capability listing is desired.
|
|
|
|
## `probe`
|
|
|
|
Review: `baseline`.
|
|
|
|
API: `present` — representative operation IDs:
|
|
|
|
- `POST /api/environments/{id}/probe`.
|
|
- `POST /api/companies/{companyId}/environments/probe-config`.
|
|
|
|
Agent access: `restricted` — Board/admin probes / CLI environment.
|
|
|
|
Policy: Environment management is instance administrator/board; permitted assignment
|
|
uses agent/project policy.
|
|
|
|
Both probe endpoints require a board actor that is local-implicit or an instance
|
|
administrator; ordinary agent identity and company membership alone are denied.
|
|
The saved sandbox probe also resolves company/environment and secret access
|
|
before allocating a fresh lease. Its measurement is company-bound to an immutable
|
|
image digest or verified Daytona snapshot ID, effective provider configuration
|
|
and active custom-image identity;
|
|
only confirmed cleanup permits recording it. A draft probe does not record saved
|
|
qualification. Reading stored qualification does not lease/provision a target and
|
|
does not grant an agent permission to probe or manage that target.
|
|
|
|
Evidence: `source-only` — [implementation](../../server/src/routes/environments.ts#L353)
|
|
at the reviewed commit above.
|
|
|
|
Verification: `not-run` — assert the documented agent denial with an owned test fixture;
|
|
verify any listed agent request/result path separately. A delegated operation needs its
|
|
own policy and access review.
|
|
|
|
Gaps: Reachability probes are not granted by an agent's right to execute assigned work.
|
|
|
|
Scoped Evidence: `source-only` — [probe authorization](../../server/src/routes/environments.ts),
|
|
[immutable binding, measurement and read](../../server/src/services/environment-probe.ts),
|
|
[private metadata writes](../../server/src/services/environments.ts) and
|
|
[custom-image binding](../../server/src/services/environment-custom-image-runtime.ts)
|
|
at the scoped commit. A connection-only success or a fixture cannot certify
|
|
native compatibility, account authentication or agent access.
|
|
|
|
Scoped Verification: `not-run` — on one authorized owned target, compare pinned
|
|
image and provider snapshot-ID proof with mutable-image, unverified-snapshot
|
|
and changed-config/account controls; require independent
|
|
cleanup evidence before recording proof. Assert agent/non-admin board denial,
|
|
secret-context denial where the actor lacks access and forged-proof rejection.
|
|
Verify API reads hide the private record and metadata-only updates cannot overwrite it. Then use
|
|
[runtime validation](./runs-adapters.md#validation) for account/model/native startup.
|
|
|
|
There is no new delegated agent probe binding or client proof-write API. Any
|
|
human-action request/result handoff requires its own admitted path and verification;
|
|
an accepted interaction does not turn the caller into a board administrator.
|
|
|
|
## `assignment`
|
|
|
|
Review: `baseline`.
|
|
|
|
API: `present` — representative operation IDs:
|
|
|
|
- `PATCH /api/agents/{id}`.
|
|
- `PATCH /api/projects/{id}`.
|
|
|
|
Agent access: `partial` — Permitted agent/project REST / native fallback, subject to
|
|
protected configuration policy.
|
|
|
|
Policy: Environment management is instance administrator/board; permitted assignment
|
|
uses agent/project policy.
|
|
|
|
Evidence: `source-only` — [implementation](../../server/src/routes/environments.ts#L353)
|
|
at the reviewed commit above.
|
|
|
|
Verification: `not-run` — exercise a listed permitted operation with actual agent
|
|
credentials/run context; inspect its result and applicable persistence/attribution.
|
|
Assert the relevant denied actor, owner, company or mode from Policy. Review the
|
|
remaining operations before qualifying the whole capability.
|
|
|
|
Gaps: Choosing among permitted targets differs from creating/configuring host targets;
|
|
test authorized and denied selection.
|
|
|
|
## `images`
|
|
|
|
Review: `baseline`.
|
|
|
|
API: `present` — representative operation IDs:
|
|
|
|
- `POST /api/environments/{environmentId}/custom-image-setup-sessions`.
|
|
|
|
Agent access: `restricted` — Board/admin image APIs and existing terminal protocol.
|
|
|
|
Policy: Environment management is instance administrator/board; permitted assignment
|
|
uses agent/project policy.
|
|
|
|
Evidence: `source-only` — [implementation](../../server/src/routes/environments.ts#L353)
|
|
at the reviewed commit above.
|
|
|
|
Verification: `not-run` — assert the documented agent denial with an owned test fixture;
|
|
verify any listed agent request/result path separately. A delegated operation needs its
|
|
own policy and access review.
|
|
|
|
Gaps: No default agent custom-image administration/terminal path; this is a policy
|
|
decision before adding a tool.
|