0 Fork 0

mirror of https://github.com/paperclipai/paperclip.git synced 2026-10-29 04:25:52 +01:00

Files

T

nickyleachandPaperclip e3680ed78b fix(adapters): teach the API helper to send a body, an upload, and a status code

Some skills send a request body from a file or from standard input, upload
one file as a multipart part, or need the numeric HTTP status code apart
from the response body. The token-free API helper could not express any of
these three shapes, so a skill still had to fall back to a form that puts
the bearer token on the command line.

Add "-d @-" and "-d @<path>" to read a body from standard input or a file,
as bytes. Add "-F 'field=@<path>;type=<mime>'" for one multipart file part:
the helper builds the boundary from a cryptographic random source, rejects
a carriage return, a line feed, a double quote, or a backslash in the
field name, file name, or content type, and confirms the boundary does not
collide with the assembled body before it sends the request. Add "-o
<path>" to write the response body to a file, and "--status" to write only
the numeric status code, matching the existing curl form these skills use
today.

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

2026-09-16 10:27:36 +00:00

src

fix(adapters): teach the API helper to send a body, an upload, and a status code

2026-09-16 10:27:36 +00:00

CHANGELOG.md

fix: bound workspace Git scans (#11572 )

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

package.json

feat(connections): add self-serve intent runtime (#12345 )

2026-08-29 12:08:34 -05: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.