0 Fork 0

mirror of https://github.com/paperclipai/paperclip.git synced 2026-10-30 21:49:18 +01:00

Files

T

Devin Foley 639e1715d9 feat(adapter-utils): fast single-stream sandbox sync + byte-level progress

Replace the 32 KB serial-printf base64 chunk loop in the command-managed
writeFile with a single `base64 -d` process fed via stdin (temp file +
atomic rename), collapsing thousands of serial round-trips into one. A
bounded large-chunk stdin fallback covers payloads too big for one stdin
string. Stream readFile downloads through the runner's onLog byte counter,
decoding incrementally instead of buffering one big string.

Make writeFile/readFile the byte-level source of truth via an optional
per-call progress hook, and have prepareSandboxManagedRuntime own the
phase labels (workspace + per-asset upload, workspace restore), direction,
and throttled log lines via the shared runtime-progress reporter.

Tests: O(1) upload process for a multi-MB payload with exact (binary-safe)
bytes; streamed download reports monotonic progress to the total; upload
and restore emit throttled, labeled, directional percentage lines.

2026-06-19 11:47:40 -07:00

src

feat(adapter-utils): fast single-stream sandbox sync + byte-level progress

2026-06-19 11:47:40 -07:00

CHANGELOG.md

chore: release v0.3.1

2026-03-12 13:09:22 -05:00

package.json

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

2026-06-18 15:46:06 -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.