0 Fork 0

mirror of https://github.com/paperclipai/paperclip.git synced 2026-10-29 12:59:13 +01:00

Files

T

Priya RamanandPaperclip 7edb4843bf fix(adapter-utils): close remaining SSH env-lab fixture orphan windows

The start-failure catch block sent one SIGTERM and removed the root
directory at once, without waiting for sshd to exit. Because the state
file is written only after readiness succeeds, a slow-to-exit sshd on
this path became an orphan with no state file to target it. Reuse the
bounded SIGTERM-to-SIGKILL escalation before the removal, and keep the
root directory when the listener survives it.

The test drain swallowed a failed stop and deleted the root directory
anyway, which erased the state file stopSshEnvLabFixture relies on for
a later kill attempt. The drain now removes the root directory only
after the stop call succeeds, and logs the pid and port when it fails.

The per-test teardown entry was pushed after several setup `await`
calls (mkdir, writeFile, git init), so a throw among them leaked the
temporary directory with no entry to clean it up. A new helper creates
the root directory and registers its teardown entry in the same step.

Add a regression test that forces a fixture to fail readiness (via an
unreachable RFC 5737 host and a short, test-only readiness timeout)
and proves it leaves no live listener and no root directory behind.

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

2026-08-26 19:01:04 +00:00

src

fix(adapter-utils): close remaining SSH env-lab fixture orphan windows

2026-08-26 19:01:04 +00: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.