0 Fork 0

mirror of https://github.com/paperclipai/paperclip.git synced 2026-10-27 11:20:42 +01:00

Files

T

Priya RamanandPaperclip a33d2aaae9 fix(sandbox): bound the pre-READY duplex buffer cap check in O(1)

The duplex readiness gate checked the pre-READY buffer cap with
Buffer.byteLength, which is O(n) in the buffer length. A provider that
controls the chunk size could send many small newline-less chunks, so the
per-chunk byte scan made the pre-READY window quadratic in the bytes
received. This was a CPU-exhaustion path on channel open.

Gate on buffer.length, the UTF-16 code-unit count, which is O(1). The UTF-8
byte length is greater than or equal to the UTF-16 code-unit count for every
string, so the check never fires before the byte cap is truly exceeded. It
can fire late by at most a factor of 3, so peak buffer memory stays bounded
near 3 MB. The failure reason and every other gate behavior stay unchanged.

Add a test that feeds many small newline-less chunks past the cap and asserts
the gate finishes with protocol contamination.

Correct one telemetry README sentence. Counters carry no dimension labels;
fallback_reason and loss_class fold into the counter metric name. The full
closed dimension set rides only the spans and the transport event.

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

2026-08-20 17:53:24 +00:00

src

fix(sandbox): bound the pre-READY duplex buffer cap check in O(1)

2026-08-20 17:53:24 +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.