0 Fork 0

mirror of https://github.com/paperclipai/paperclip.git synced 2026-10-25 17:45:53 +01:00

Files

T

Priya RamanandPaperclip f09d5ba416 fix(sandbox): make a pre-response duplex forward failure non-retryable for a mutating method

The duplex broker forwarded each request and mapped a forward rejection to a
retryable 502 when its controller was not aborted. A fetch can reject after the
request bytes reach the host and the host commits a mutation, but before the
response headers arrive. A retry then sent a new request id outside the broker
deduplication set, so the host applied the mutation twice.

The broker now classifies a non-aborted forward rejection by method safety. A
safe method (GET, HEAD, OPTIONS, TRACE) never changes host state, so its
rejection stays a retryable 502. Any other method may have committed, so the
broker returns a non-retryable 504 and marks the outcome indeterminate. The
in-sandbox gateway maps the indeterminate outcome to a terminal 409, so a caller
never repeats a possibly-committed mutation. Add broker coverage for both paths.

Co-authored-by: Paperclip <noreply@paperclip.ing>

2026-08-20 06:28:17 +00:00

src

fix(sandbox): make a pre-response duplex forward failure non-retryable for a mutating method

2026-08-20 06:28:17 +00:00

CHANGELOG.md

fix: bound workspace Git scans (#11572 )

2026-08-17 22:11:30 -05:00

package.json

build(deps-dev): bump @types/node from 22.19.21 to 22.20.1 (#10304 )

2026-07-28 10:48:45 -07:00

README.md

PAPA-430: workspace finalize gates + no-remote-git enforcement (#6969 )

2026-05-29 08:25:29 -07:00

tsconfig.json

Fix root TypeScript solution config

2026-03-09 14:09:30 -05:00

README.md

@paperclipai/adapter-utils

Shared utilities for Paperclip adapters: process spawning, environment injection, sandbox/SSH transport, workspace sync, and the round-trip helpers that move code between the local execution-workspace cwd and wherever the agent actually runs.

For the adapter-author guide see docs/adapters/creating-an-adapter.md and the in-repo notes at packages/adapters/AUTHORING.md.

No-remote-git contract

The local execution-workspace cwd is the only persistence boundary across runs. No adapter may depend on a git remote for cross-run state.

Adapters that run the agent on a different host should use the SSH round-trip helpers in src/ssh.ts:

prepareWorkspaceForSshExecution({ spec, localDir, remoteDir }) — bundles the local cwd (tracked files, dirty edits, untracked additions, and the git history needed to reconstruct it) to remoteDir before the run starts. Runs with no git remote configured.
restoreWorkspaceFromSshExecution({ spec, localDir, remoteDir, ... }) — syncs the remote cwd back into localDir after the run, including any new commits the agent created. Also runs with no git remote configured.

prepareRemoteManagedRuntime in src/remote-managed-runtime.ts wraps both calls for adapters that want a per-run remote workspace and an automatic restoreWorkspace() finally hook.

The invariant is pinned by the no-remote-git contract case in src/ssh-fixture.test.ts, which asserts that a remote-only commit propagates to the local worktree through the prepare → restore round-trip with no git remote configured at any point. Do not regress that test.