0 Fork 0

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

Files

T

Priya RamanandPaperclip 0c5da4de07 refactor(adapter-utils): carry the http2 bridge forward response body as bytes

The host held two copies of every forwarded body on the HTTP/2 bridge
path: readBridgeForwardResponseBody decoded the response to a UTF-8
string, then the caller encoded it back to bytes for the sandbox
stream. This change carries the body as one Buffer end to end.

- readBridgeForwardResponseBody now returns Promise<Buffer>.
- forwardBridgeRequest accepts a string or Uint8Array request body and
  returns a Buffer response body. Every error path returns a Buffer.
- The HTTP/2 forward handler passes and returns raw bytes with no
  toString("utf8") call.
- The file bridge call site converts the body to a string, so the file
  bridge response file format stays unchanged.
- postedIssueCommentLogMarker now accepts a Buffer or a string. It
  decodes at most 4,096 bytes, and it logs a comment id only when the
  parsed value is a canonical lowercase UUID.

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

2026-08-26 18:01:32 -07:00

src

refactor(adapter-utils): carry the http2 bridge forward response body as bytes

2026-08-26 18:01:32 -07:00

CHANGELOG.md

fix: bound workspace Git scans (#11572 )

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

package.json

build(deps-dev): bump typescript from 5.9.3 to 7.0.2 (#11880 )

2026-08-25 14:49:05 -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.