0 Fork 0

mirror of https://github.com/paperclipai/paperclip.git synced 2026-10-26 18:31:34 +01:00

Files

T

Priya RamanandPaperclip 0d728d0f45 feat(sandbox): bound untrusted duplex broker frame concurrency and id retention

The provider controls the duplex transport directly, so each request frame is
untrusted. The broker now enforces two finite, fail-closed limits before it adds
the id to the seen set, allocates the pending record, or calls the forward
handler:

- an in-flight limit that bounds the controllers, the timers, and the concurrent
  authenticated forwards.
- a lifetime limit that bounds the retained request-id memory.

On a limit the broker answers the refused request with one bounded terminal 503
response and forwards nothing. An in-flight refusal is retryable and keeps the id
out of the seen set, so a resend passes after a slot frees. A lifetime refusal is
terminal. The refusal preserves the no-replay and no-double-dispatch rules and
records no telemetry, so the fixed observability surface stays unchanged.

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

2026-08-20 05:21:27 +00:00

src

feat(sandbox): bound untrusted duplex broker frame concurrency and id retention

2026-08-20 05:21:27 +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.