0 Fork 0

mirror of https://github.com/paperclipai/paperclip.git synced 2026-10-27 02:44:50 +01:00

Files

T

Priya RamanandPaperclip 3e8d9d6f6b test(sandbox): add the local real-process duplex end-to-end harness

Spawn the generated gateway with plain node from a temporary file, attach
the real host broker to the child stdin and stdout, and forward each
request to a local fake API server on a real HTTP call. The harness needs
no provider credentials and adds no dependency.

The harness proves the composed duplex path over real kernel pipes:
- The child sends a valid liveness-only READY frame to the broker.
- One HTTP request travels through the child and the broker to the API and
  the response body returns unchanged.
- A large response spans many pipe chunks and returns complete.
- A multi-byte UTF-8 sequence split across chunk borders decodes correctly.
- Concurrent requests through one child each receive the matching response.
- A real stdin EOF makes the gateway answer 409 outcome_indeterminate to
  every outstanding request and 503 bridge_unavailable to every new one.
- A real process kill moves the broker to lost, stops all dispatch, and
  leaves no open pipe or socket handle after teardown.

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

2026-08-20 03:21:45 +00:00

src

test(sandbox): add the local real-process duplex end-to-end harness

2026-08-20 03:21:45 +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.